No, not for the impressions Ad Manager marks as overdelivery. Since 2 November 2026, its month-end reconciliation also covers Programmatic Guaranteed deals with Display & Video 360. Delivery above the contracted goal on an ended deal is not paid, and you can see it in the "Total overdelivered impressions" metric.
The rule has gaps, and Google's own help pages don't all agree yet. So the useful work this week is a report that shows what the check caught, plus a look at the pacing settings on every DV360 deal that ends in November.
What changed on 2 November
The release note is short. Ad Manager extends its Programmatic Guaranteed reconciliation to deals with DV360. At the end of each month, before revenue is finalized, it finds impressions above the contracted goal and marks them. You aren't paid for them, and the payments page adds that the buyer isn't charged either.
If you search for the rule you will find four Google pages that read differently:
| Page | What it says about extra impressions |
|---|---|
| Ad Manager release note, 2 November 2026 | Marked impressions are not paid. A small amount outside the lookback window may still be paid. |
| Ad Manager, payments and reports for Programmatic Direct | Neither charged nor paid, for deals that have ended. |
| Ad Manager, about proposal line items | The buyer gets a few more impressions and pays for them. The publisher may return the money or do nothing. |
| DV360, Programmatic Guaranteed deals | Only the contracted amount appears on the buyer's invoice. |
I would work from the release note because it is the only dated one. The proposal line item wording looks like it predates the change, but Google doesn't date that page, so treat that as my reading. Finance should know the old wording exists, because it is the one that tells you a refund is your choice.
What the check catches and what it misses
Three limits on the payments page decide how you read the numbers.
The check only looks at deals that have ended. A deal still running on the last day of November is not assessed for overdelivery in that pass, however far past its goal it is.
Overdelivery that happens well ahead of the end date is not identified, and neither is overdelivery after the system run. Google says small amounts of that kind may continue to be billed and paid. The release note calls this the lookback window and gives no length, so you can't calculate which impressions fall inside it.
The timing matters for the first read. Programmatic Guaranteed appears on the Transactions page by the second of the month, and the marking happens before revenue is finalized. My reading is that the November close is the first one where DV360 deals show the effect, so early December is when you look. Google has not stated that sequence in so many words.
The report to pull at month end
Build this in Interactive reports, the replacement for the older Reports tool. The metric page lists "Total overdelivered impressions" under the Historical report type.
- Create a Historical report for the closed month.
- Filter "Programmatic channel" to Programmatic Guaranteed. The payments page also suggests the filter "Order is programmatic" set to yes, but that one includes Preferred Deals.
- Add the dimensions "Deal ID", "Deal buyer", "Line item", "Line item end date" and "Line item contracted quantity".
- Add the metrics "Ad server impressions", "Total overdelivered impressions" and "Ad server CPM and CPC revenue". Google says to use Ad Manager metrics for these deals, not Ad Exchange ones, and this revenue metric is net.
- Export it and sort by overdelivered impressions, largest first.
Then add two columns of your own. The unpaid share is overdelivered impressions divided by ad server impressions. The money is overdelivered impressions divided by 1,000, times what you actually earn per thousand on that deal. Use earned revenue over paid impressions for that last number, because the payments page says the rate on the line item is gross, before your net payment is calculated.
If Ad Manager refuses a combination, drop the attribute dimensions first and join them from a line item export.
Here is how to read a row:
| What the row shows | What it means | What to do |
|---|---|---|
| Delivered above contracted, overdelivered above zero | The check caught it, and those impressions are unpaid | Size it, then check the pacing setting on that line item |
| Delivered above contracted, overdelivered at zero, deal ended | Outside the window, or the run hasn't happened yet | Read it again after the month closes before you call it paid |
| Delivered above contracted, deal still live | Not assessed yet | Treat a zero as unknown and check the line item's pacing today |
| Delivered at or under contracted | Nothing to reconcile | Check under-delivery instead |
The cost has a second half. An unpaid impression still went to the deal instead of to whatever else could have served there. Pull the eCPM for other demand on the same ad units and the same dates to get a rough number. It is an estimate, since you can't replay those auctions.
Why a deal runs past its goal
Google gives two causes for small overruns on any deal: delayed impression counting, and simultaneous requests arriving just as the cap is reached. You can't configure those away. DV360 and Ad Manager also take at least one to two hours to sync delivery data, which is why Google recommends at least a day to traffic a deal.
The causes you can do something about are in the settings, and they are on your side of the deal: DV360's help page says publishers control pacing for Programmatic Guaranteed. Proposal line items have the same "Deliver impressions" option as other line items, and the delivery speed page gives these limits:
| Setting | Documented behaviour |
|---|---|
| Evenly | Can deliver up to 5% above the goal, as a safeguard against under-delivery |
| Frontloaded | Serves up to 40% above its goal early on, tapering to 5% ahead of schedule |
| As fast as possible | Takes every impression it can and may end early |
Those figures come from the general line item page. Google doesn't restate them for Programmatic Guaranteed, so check them against your own deals using the report above. The pacing page adds a warning that fits small deals on large sites: a low impression goal on a lot of available inventory can over-pace, and the fix it suggests is narrower targeting.
What to change before the next close
Run this on every DV360 deal ending this month, in this order:
- Pull the list: deal ID, end date, contracted quantity and the "Deliver impressions" setting. Include deals that end on the last days of the month, since those are the ones this close assesses.
- Open any deal set to Frontloaded or As fast as possible and ask whether the buyer asked for that. If nobody did, move it to Evenly.
- Look for small goals on broad targeting and narrow them where the contract allows.
- Make the changes early. A pacing edit needs as much as two days to reach traffic, so one made at the very end does little.
- If sales wants to give a buyer extra impressions, or the buyer wants more, put them in the contracted quantity through a renegotiation so they are paid.
- Forecast these deals from contracted quantity, not from delivered impressions, so the unpaid part never reaches the revenue line.
The 5% in Evenly exists to protect against under-delivery, and a deal that falls short has its own cost. For a Standard DV360 deal you can create a makegood if the end date is in the future or within the last 30 days, but buyers aren't charged for those impressions beyond programmatic fees, so a shortfall can't be fixed for free either. Our note on why a direct deal under-delivers covers how to read pacing before you change a goal.
Optimon monitors Programmatic Guaranteed and direct-sold campaigns down to the ad unit from your own Ad Manager data, so you can see a deal's delivery next to the rest of the stack instead of waiting for the month-end export.
FAQ
Does this apply to Programmatic Guaranteed deals with other DSPs?
The 2 November release note only names Display & Video 360, and it calls the change an extension of an existing process. The general payments page describes that process without naming a DSP, so I read other buyers as already covered. Google does not publish a list, so confirm with your account manager if a large deal depends on it.
Are Sponsorship deals covered too?
Google does not say separately. The metric definition covers Programmatic Guaranteed above the agreed goal, and the older proposal line item page describes a Sponsorship CPM impression limit that can also be passed by a small amount. A CPD deal is billed per day against a threshold, not per impression, so overdelivery has no obvious unpaid amount there. Ask before you model either type.
Should I give the buyer money back for extra impressions?
Check first. The proposal line item page still says the buyer pays for a few extra impressions and that you may return the money. Under the reconciliation, marked impressions are neither charged nor paid, so a manual refund on those would return money the buyer never paid. Match your refund process to the impressions the metric reports before anyone sends a credit.
Sources
- What's new in Google Ad Manager (Google Ad Manager Help)
- Payments and reports for Programmatic Direct (Google Ad Manager Help)
- Total overdelivered impressions (Google Ad Manager Help)
- About proposal line items (Google Ad Manager Help)
- Add proposal line items (Google Ad Manager Help)
- Programmatic Guaranteed deals (Display & Video 360 Help)
- Set the delivery speed of line items (Google Ad Manager Help)
- How line item delivery is paced (Google Ad Manager Help)
- Interactive report dimensions (Google Ad Manager Help)
- Give buyers Makegoods (Google Ad Manager Help)
- Programmatic Guaranteed and Preferred Deals has moved to net revenue in reporting (Google Ad Manager Help)
