> ## Documentation Index
> Fetch the complete documentation index at: https://docs.apostra.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Is each package on pace?

> What a package's pacing_index means, where it comes from, and when Apostra tells you a package is behind.

A media buy can sit `active` for weeks while a package delivers a few percent of
its budget. A package's `pacing_index` says whether it is on track, and Apostra
now tells you when a live package falls well behind.

## Read it

The seller reports `pacing_index`. It is AdCP's `pacing_index`, and Apostra
returns the seller's value as it came, on the package's `delivery`.

| `pacing_index` | Meaning |
| - | - |
| `1.0` | On track against the package's plan. |
| Under `1.0` | Behind. `0.5` is half the pace the plan calls for. |
| Over `1.0` | Ahead of plan. |

The value is the seller's own measure, so how it is worked out depends on the
seller. A package whose seller sends none has no `pacing_index`. Apostra does not
publish a number of its own in its place.

## When Apostra tells you a package is behind

Apostra checks live packages on each media buy status sweep (hourly). It
notifies the buying account when a package on an `ACTIVE` media buy is neither
paused nor canceled, is inside its flight, and its published delivery-goal
verdict is `underdelivery`. The notice also requires a pacing index from the
seller or the delivery goal. A verdict of `early_exhaustion` does not trigger
this alert. Delivery-goal verdicts generally need agreement across two reporting
days; see [Goal progress](https://docs.apostra.com/v3/goal-progress.md).

The alert is part of the buyer experience feature profile (see
[Your plan decides what you pay, not what your account can do](https://docs.apostra.com/v3/plan-and-billing.md#your-plan-decides-what-you-pay-not-what-your-account-can-do)).
Every buyer account gets that profile when it is created, on every plan
including Free. An account without a buyer experience profile gets no alert.

The notice uses the seller's `pacing_index` when available, or Apostra's
published delivery-goal pacing index otherwise. The index is supporting evidence;
the published delivery-goal verdict determines whether to alert.

A package whose flight has not opened is never behind, whatever its seller
reports. A flighted buy carries one date-bounded package per window, so each
window is judged inside its own flight.

The notice arrives as a `campaign.unhealthy` notification with
`reason: "package_behind_pace"`. Its data carries the media buy, the package,
`pacingIndex`, `pacingIndexBasis` (`seller` or `estimate`), `flightElapsed`, and
the delivered spend and budget when the package has one. `estimate` now means
the delivery-goal pace. `deliveryGoal` adds the published verdict, pacing index,
projection and data-through time. When the seller has said why, the
notice also carries `sellerIndicatorTypes` and `sellerIndicatorsAsOf`, described
under "Why a package is behind" below. Who is emailed or sees it in the inbox
follows the account's existing notification preferences for `campaign.unhealthy`,
and webhook subscriptions to that event receive it.

A package is told about once per week of its flight. A package that stays
behind is told about again each week. A one-week package gets one notice. Every
notice is stored as a notification on your account, so the record of what you
were told and when stays in Apostra.

## Why a package is behind

A seller can say why a package is behind through AdCP indicators on the package.
Two of them give a reason: `inventory_shortfall_forecast` (the seller forecasts
too little inventory to deliver the package) and `pacing_risk` (the seller
sees the package at risk of missing its pace). When the seller has reported one
of them, the notice names it in its own words, for example "is behind pace: the
seller forecasts an inventory shortfall", and `sellerIndicatorTypes` lists the
reasons it named. `sellerIndicatorsAsOf` is when the seller completed that
evaluation. The notice never quotes the seller's own text or scores.

Today Apostra reads these indicators from the managed sales agent when it is
connected to Google Ad Manager. A package sold through any other seller gets the
notice without a reason. Apostra uses a seller's reason only while its evaluation
is less than 24 hours old, so a seller that stops evaluating never leaves a stale
reason on a notice. A seller that evaluated the package and found no reason adds
none. The package's `pacing_index` is not affected: it still comes from the
seller's delivery report, as described above.

## See package indicators

Read the media buy with `get` (`kind: "media_buy"`, `include: ["products"]`).
A package can carry the seller's assertions and Apostra's own pacing evaluation.
Apostra asserts `pacing_risk` when the package's published delivery-goal state
is `underdelivery`. A projection of early exhaustion does not assert it.

| Field | Meaning |
| - | - |
| `indicators` | Current assertions. Each has `type` and a `source` of `seller` or `apostra`. Seller assertions may include `detected_at`, `scope` and seller detail in `ext`. If both sources assert `pacing_risk`, both entries appear. |
| `indicatorTypesEvaluated` | The union of types evaluated by either source. An unlisted type is unknown, not clear. |
| `indicatorsAsOf` | The evaluation time when one source is present, or the older evaluation time when both are present. |
| `indicatorsEvaluatedScope` | Present when the seller evaluated only part of the package. It describes the seller's coverage; Apostra's pacing evaluation covers the whole package. |

An empty `indicators` list means the listed types were evaluated and no current
assertion was found. A package with no evaluation carries none of these fields;
absence means unknown, not that delivery is on track. Apostra's evaluation time
is the time of the stored published goal-progress row, which can be older than
the latest sweep when its published content has not changed. Seller-authored
text is shortened and set apart from Apostra's own output.

If a source cannot be read, the response reports that in `unavailableIncludes`.
The behind-pace notice above uses a seller's reason only while it is less than
24 hours old.

### Be told when it changes

A registered buyer agent can subscribe to the `indicators` event category and
receive `indicators.changed` when a package's seller indicators change and the
change has held. Events for changes to Apostra's own assertion are not yet
available. [Webhook endpoints](https://docs.apostra.com/v3/webhooks.md#indicatorschanged) explains the
seller event.

### Through AdCP

On `get_media_buys`, the seller's snapshot stays in AdCP's core fields:
`indicators`, `indicator_types_evaluated`, `indicators_as_of` and, when
applicable, `indicators_evaluated_scope`. Apostra's evaluation is separate in
`ext.apostra`: `indicators`, `indicator_types_evaluated` and `indicators_as_of`.
This preserves a seller's partial coverage without treating Apostra's
whole-package evaluation as part of it. A failed source read leaves that
source's fields off; absence means unknown.

To see how a buy that has drifted from its booking is reported, read
[Does your buy still match the booking?](https://docs.apostra.com/v3/booking-answer.md). To change a live buy
whose package is behind, read
[Change a live media buy](https://docs.apostra.com/v3/change-a-live-media-buy.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.