Tracking and alerts

/library/tracking is where your workspace says which advertisers it cares about. Watching one does three things: it puts that advertiser on a daily re-ingest instead of the weekly one every other advertiser gets, it turns on activity alerts, and it puts the advertiser in the weekly digest.

A watch belongs to the workspace, not to you. Every member sees the same watches and the same alerts, the same way every member sees the same swipe file.

Watching

Watch from the advertiser's page or from the tracking page. Each watch carries two switches of its own:

They are independent. A workspace with alerts off and the digest on is still mailed the week's movement — the digest is composed from the corpus itself, not from the alert feed, so turning alerts off never turns the mail into a false "nothing happened".

Unwatching deletes the watch row. It deletes no ads: the advertiser and everything captured for it stay in the shared corpus.

Tracked advertisers are counted against your plan. The page states your count and the plan's ceiling, or says plainly that the plan sets none rather than printing a number that stands for "no ceiling". At the ceiling a new watch is refused, the refusal names the limit, and the reason arrives beside the answer instead of as a bare error — so an agent that lists before it writes is told first. Allowances are on the billing page.

The four alerts

At the end of every ingest run for a watched advertiser, Tempio diffs the run against what was already stored and writes an alert for each thing that moved:

An alert kind with nothing to say writes nothing. A quiet run produces no feed entry rather than four zeroes.

Two things about format shift are worth knowing, because both are deliberate:

• A first run never fires it. There is no previous mix for a share to have moved from, so an advertiser's first ingest is new ads and nothing else.
• A run that only stopped ads cannot fire it. The comparison is against the advertiser's ads minus the ones this run created, so a run that created nothing has nothing to compare.

The one it reports is the biggest mover, and on a tie the format that rose — "they started making video" is the news, and "they make proportionally less text" is the same fact said backwards.

What an alert carries

Ids and counts, and nothing else. No headline, no advertiser name copied onto the row, no URL: the alert names rows, and the feed reads those rows when it renders, so nothing in it can go stale or outlive what it describes. The count is always exact; the list of ids is a sample, because a backfill can create a thousand ads in one run and a thousand ids is a payload nobody reads. For the whole set, open the advertiser.

An alert is about a third party's ads in a public archive. It is not a report about your accounts, and an archive that covers only some regions cannot tell you about the ones it does not — the coverage rule applies to an alert exactly as it applies to a search result.

Alerts are read on the tracking page, where Mark read clears them. There is no second notification store: this feed is the whole of it.

The weekly digest

One mail per workspace per week, composed Monday at 13:00 UTC over the previous seven whole days.

The counts come from the corpus, scoped through your own watches: new ads by when they were first seen, stopped ads by when they went inactive, new landing pages by when they first appeared. Only format shift is read from the alert feed, so it is absent in a workspace that has alerts switched off.

A quiet week is still mailed, and the mail says so. It reads: No watched advertiser changed anything we can see this week. Nothing is missing; there was nothing to report. Silence would be indistinguishable from a mail that failed to send.

There is one digest row per workspace per week, so a re-run sends nothing twice. Recipients a mail provider refuses are counted on the row, so a partial send is visible rather than silent.

Nothing in the digest is a performance figure. Every number in it is a count of rows Tempio holds, and the only score in it is longevity, travelling with its own sentence.

Turning the mail off

Every member of a workspace that tracks advertisers is subscribed once, by default. A member who joins after the first watch is subscribed at the next one, and an opt-out is never quietly re-enabled.

Two ways out, and both mean the same thing:

• The weekly digest switch on the tracking page. That switch is yours — it is the one control on that page that is per member rather than per workspace, and turning it off stops your mail and nobody else's.
• The unsubscribe link in the mail itself, including the one-click unsubscribe your mail client offers in its own chrome.

Either one turns off this workspace's digest for you. It does not unsubscribe you from Tempio, it does not touch any other workspace's digest, and the mail's footer says the same thing: it stops this workspace's digest only, and account and billing email still reaches you.

To stop the digest for the whole workspace, turn off the digest switch on each watch — or unwatch the advertisers, which stops the daily re-ingest too.

From an agent

Over MCP, list_library_watches returns this workspace's watches, its unread alerts and its plan usage; set_library_watch watches, unwatches and changes both switches, because all three are one row. Both are reachable through tempio_manage as the library_watch entity. Watching an advertiser changes nothing in your own ad accounts, so it creates no change request and there is nothing to approve.