Review Pacing
The oxs-pacing-review skill guides the AI assistant through checking how the line items of an OpenXDirect™ order, or of a whole account, are pacing. It pulls delivery figures for every line item simultaneously and compares each one to where they should currently be. You get one table with a clear flag per line item: on pace, behind, well behind, ahead, or not started. The order’s own pace is shown at the top.
This skill only reads data. It does not modify items and is safe to run anytime. It tells you which line items are off pace but not the reason. To get the reason, see Diagnose a Line Item.
When to Use It
- Find out which line items are underspending, or are behind or ahead of pace.
- Check how a campaign or order is pacing this week.
- Run a daily or weekly delivery check across an order. For example, “Which line items in order Spring Launch are behind this week?”
What You Need
- What to review: an order by name or ID, or all active line items in an account. The assistant does not review everything by default. If you have several accounts, the assistant asks which account.
- Time window (optional): yesterday, this week (default), the last 30 days, or the full flight.
For large sets, beyond a couple of hundred line items, the assistant asks you to narrow the review to an order or an advertiser.
How It Works
- Settle the set. The assistant finds the order or account and lists its line items. Only line items that are active and that should be delivering are scored. Paused, scheduled, finished, and archived line items are listed separately with their status and reason.
- Pull delivery for all of the line items simultaneously. It gets each line item’s spend, impressions, and pacing for the window you chose.
- Check the order’s pace. The order’s own pace goes at the top. If the line items’ goals do not add up to the order’s budget, the assistant points this out. An order can be behind even when every line item is on pace because line items were not given enough budget.
- Flag each line item. Each line item is compared to where it should be at this point in flight.
How Line Items Are Flagged
| Compared with where it should be | Flag |
|---|---|
| 10% or more ahead | Ahead (or goal reached) |
| Within 10% either way | On pace |
| 10% to 25% behind | Behind |
| More than 25% behind | Well behind |
| Flight hasn’t started | Not started |
You can ask for different thresholds. Every scored line item also gets two extra readings:
- Trend: whether delivery is rising, flat or falling compared with the previous window. A line item that is on pace but falling fast is the one to look for.
- Run-out risk: a line item with more than 80% through its flight and well short of its goal will not reach it at its current rate. The assistant says it plainly.
Good to Know
- Figures run through yesterday. Data updates once a day, around 10:00 UTC. Current day activity is never included. A line item that started on the current day has no data yet and is not an issue.
- “As fast as possible” line items are meant to run ahead, so “ahead” is expected for them.
- Pacing always covers the whole flight. The window you choose only changes the spend and the impression totals shown.
- A hint for behind line items: the assistant notes where things stall. The line item might not be bidding, might be losing auctions on price, or might be winning auctions without serving, which can point to the creative. It names the pattern but does not diagnose it.
What You Get
- The window: the dates the figures cover and when they were last updated.
- The order’s pace: its goal, delivered so far, expected by now, and how far ahead or behind it is.
- A table, one row per line item: goal, delivered, expected, the percentage delivered against the percentage of the flight elapsed, how far ahead or behind it is, the trend, and the flag. Money is shown in dollars and cents, and impressions with thousands separators.
- Line items that were not scored, listed with their status and reason.
- A short note for each behind line item naming where it stalls and pointing to
oxs-delivery-troubleshoot, plus a note for any run-out risk.
The assistant reports how far ahead or behind each line item is. It does not guess for a reason or predicts when a budget will run out.
Safeguards
- Read-only: nothing in your account is modified.
- Reviews only the set you name, never your account by default.
- Paused or finished line items are kept out of the pace scoring so they do not hide the real issue.
Example Prompts
“Which line items in the order Spring Launch are behind this week?”
“How are all my active line items pacing?”
“Show me yesterday’s pacing for order 5678.”