Read Pulse
Ask for thepulse include on a campaign:
get returns pulse with the campaign’s verdict, its reasons, and one entry
for each media buy Pulse judges (at most 50; mediaBuysOmitted counts the
rest). Those are the campaign’s active media buys, and its media buys that
ended in the last 90 days whose delivery is behind (below). Draft, paused and
archived media buys are not listed, nor is an ended one whose delivery runs to
its flight end.
Each media buy entry has:
To show Pulse in a list, ask
search for it:
pulse with only the campaign verdict,
dataThrough and nextCheckAt.
If Pulse cannot be read, the campaign is still returned, and
unavailableIncludes names pulse with the reason.
What each verdict means
For a media buy:
For the campaign:
Missing figures are never shown as zero. A media buy whose seller has not
reported reads
not_expected_yet until its first day of delivery is due, and
stale after that, never not_delivering, and its metrics are null. Two
media buys read otherwise: one whose products do not report delivery reads
unsupported, and one whose seller’s latest report failed reads
source_error.
When figures are due
Whether a media buy is stale is the same calculationget_delivery reports as
deliveryFreshness, so Pulse, the Campaigns page and get_delivery always
agree. See
How current each seller’s delivery is.
- The schedule. It comes from the products the media buy booked: how often
each product reports (
available_reporting_frequencies) and how long after a period ends its report arrives (expected_delay_minutes). The most frequent schedule any of them reports on applies, with the longest delay. - When a day is due. Reporting periods run from the day after the last day of daily delivery Apostra holds, and a period is due once it has ended and its delay has passed. When the products declare no schedule, a day is due two days after it starts.
- Stale. A media buy is stale when a due day in its flight has no delivery after the last day held. A day the seller reported as zero is held, so zero delivery is not stale. A media buy whose delivery runs to its flight end is never stale.
- Ended media buys. One whose delivery stops before its flight ended stays
on Pulse as stale for 90 days after the flight ends. After that its gap still
shows in
get_delivery.
dataThrough and observedAt are the time the agent
captured it (for a media buy with several packages, the oldest of their capture
times). Once the daily reports run past it, Pulse shows them again. Either way
the figures are provisional. See
How often GAM delivery arrives.
Keep a view current
Buyer agents can also subscribe tocampaign.progress.changed to learn when a published verdict changes.
nextCheckAt is the earliest time a verdict can change with no new report: a
flight starting, a day of delivery falling due, or an ended media buy leaving
Pulse after its 90 days. It is null when only a new report can change a
verdict. To keep a page current,
read Pulse again at nextCheckAt rather than on a timer.
Pulse on the Campaigns page
The Campaigns page shows Pulse without being asked. Each campaign in the list carries its verdict and how far its data runs (“Data through”, or “No data yet” when no seller has reported). Opening a campaign shows its verdict, then each listed media buy’s verdict, its data-through time and its impressions, clicks and spend. The page labels these as provisional Snapshot figures, not official and not billable. A figure a seller has not reported shows as “Unavailable” with the reason (not reported, delayed, incomplete or out of date), never as 0. Only a figure the seller reported as zero shows as 0. In the Apostra web app, the page updates as soon as a campaign’s Pulse changes: when a new report changes a verdict, or figures go stale, the list and the opened campaign show it within about a minute, without a reload. The page only watches for changes; it reads the new Pulse the same way it did the first time, so it never shows a campaign you can’t otherwise see. In Claude, ChatGPT and other hosts, the page reads Pulse again atnextCheckAt instead. It does not
poll on a timer in any host, and in the web app it also keeps that
nextCheckAt check as a fallback.