> For the complete documentation index, see [llms.txt](https://docs.podigee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podigee.com/documentation/grow-and-monetize/monetization/diagnose-underdelivery-no-fill-or-wrong-delivery.md).

# Diagnose underdelivery, no-fill, or wrong delivery

Diagnose underdelivery, no-fill, or an unexpected ad by moving from the aggregate signal to the exact decision and the smallest safe correction.

Use this guide when a Campaign is behind pace, fill rate is lower than expected, a buyer reports no ad, or the wrong Campaign or Creative appears in a delivery result. Start with evidence. Do not change targeting, price, capacity, or fallback rules before you know the recorded cause.

## Confirm the signal

Open **Monetization > Evidence & Money** or the Campaign's **Delivery, pace, and revenue** section. Set the correct period, time zone, media type, and Campaign before you compare values.

Check:

* planned quantity and remaining goal;
* delivered quantity and qualified delivery;
* fill rate and no-fill decisions;
* pacing state and time left;
* qualified revenue and currency;
* latest delivery evidence time.

![The current One Podigee Campaign page shows delivery, pace, and revenue for separate audio and video flights, with delivered units, remaining goals, and qualified revenue.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-f8d7c46c7e3d1f7529c295099ca5eda249d4c76d%2Fdoc-monetization-072-campaign-performance.png?alt=media)

*Use the Flight rows to separate an audio issue from a video issue.*

One slow day does not prove underdelivery. Act when the Flight stays **Behind**, the remaining goal is large for the time left, or the no-fill pattern points to a repeatable cause.

## Move to the exact decision

1. Select **Explain delivery** from the Campaign, or open **Monetization > Operations > Live ad delivery**.
2. Filter by the affected delivery method and result.
3. Search by Campaign, Creative, episode, or request time.
4. Open one decision that represents the reported problem.

![The current One Podigee decision library keeps the No ad selected result filter visible above the no-fill results.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-00e00bb91a090a49e50bb0d117d9b4cf7acaf885%2Fdoc-monetization-073-no-fill-filter.png?alt=media)

*The decision reason is more useful than an assumption based on the Campaign name.*

![The current One Podigee decision detail shows a no-fill result, the customer-readable reason, the content context, and shortened references.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-d0a7f6b6116b9361a55e93c258e8db62265213ff%2Fdoc-monetization-073-no-fill-detail.png?alt=media)

*Use the decision detail before changing a Campaign rule.*

Read **Result**, **Why**, **Delivery method**, **Podcast**, **Episode**, **Ad break**, and every slot. A no-fill result can be correct. A partially filled break can also be correct when the break rules allow it.

## Classify the cause

Use the first matching row:

| Evidence points to      | What to check                                                                            | Smallest safe correction                                                |
| ----------------------- | ---------------------------------------------------------------------------------------- | ----------------------------------------------------------------------- |
| Inventory or capacity   | Published Inventory, eligible episodes, slot limits, reservation, and remaining quantity | Repair Inventory or capacity, then refresh the Campaign checks.         |
| Targeting or exclusions | Markets, content categories, audience rules, schedule, and exclusions                    | Narrow or correct the rule only when the business plan is wrong.        |
| Pacing or priority      | Flight pace, priority, budget, separation, and competing Campaigns                       | Adjust the commercial rule after confirming the intended delivery goal. |
| Frequency or separation | Listener or household limits and brand separation                                        | Correct the limit only when it does not match the approved plan.        |
| Creative coverage       | Media type, rendition, rights, market, delivery method, and period                       | Prepare or assign a valid Creative, or resolve the exact coverage gap.  |
| Demand or provider      | Source order, minimum CPM, response limit, timeout, and provider result                  | Repair the source or use the configured next eligible source.           |
| Delivery or destination | RSS, HLS, Apple, Spotify, or external destination state                                  | Check the destination connection and its boundary.                      |
| Evidence or processing  | Delayed audience event, qualification window, or report lag                              | Wait for the stated processing boundary, then reconcile evidence.       |

Do not treat a planned value or forecast value as proof that an impression should have served. Those values describe a plan or estimate, not a recorded decision.

## Check Inventory and capacity

Open the affected Flight and confirm:

* the Inventory package is published;
* the podcast and episode supply are in the selected period;
* the break has enough slots and duration;
* the reservation covers the requested quantity;
* the media type matches the Flight;
* partial-fill and no-fill fallback rules are intentional.

If a reservation is stale or insufficient, use the current Forecast and reservation workflow. Do not promise more delivery until the new reservation succeeds.

## Check targeting, pacing, and frequency

Compare the exact decision reason with the Campaign settings. A Campaign can be active and still not match a request because of a market, schedule, content category, exclusion, frequency, or separation rule.

Use this order:

1. Check whether the request should match the Campaign.
2. Check whether the Flight is allowed to serve at that time.
3. Check whether pacing or priority withheld the Campaign.
4. Check whether a frequency or separation rule blocked it.
5. Check competing Campaigns and the configured selection order.

Change the rule only after the operator confirms that the recorded business requirement is wrong.

## Check Creative coverage

Open the selected Flight and Creative. Confirm that the Creative version has:

* a ready audio or video rendition;
* valid rights for the complete period and markets;
* the required destination delivery method;
* no open coverage decision;
* the intended rotation weight.

A Creative can be ready in the library but still fail a specific Flight. Resolve the exact coverage decision or assign a valid replacement. Do not assign an audio-only Creative to a video Flight.

## Check demand and provider results

For external demand, open the decision detail or demand evidence. Check the provider result, source order, response time, and whether Podigee received a playable response.

| Provider result    | Meaning                                           | Action                                                              |
| ------------------ | ------------------------------------------------- | ------------------------------------------------------------------- |
| No bid or no-fill  | The source did not return eligible demand.        | Check the next configured source and the source rules.              |
| Timeout            | The source did not answer within the limit.       | Check provider health and retry behavior.                           |
| Invalid response   | The response did not meet the supported contract. | Keep the result out of delivery and escalate the provider response. |
| Unsupported format | The response cannot play on this delivery path.   | Use a compatible source or Creative.                                |
| Provider accepted  | The source accepted the request.                  | Confirm that the returned media and tracking are playable.          |

Never force an unsafe or invalid provider response into a paid decision to improve fill.

## Check the delivery destination

If the decision is correct but the listener or viewer received the wrong media, check the delivery method and current delivery version. Confirm that the request used the expected RSS, HLS, Apple, or Spotify path.

For Podigee-controlled delivery, compare the short decision reference with the playback check. For a connected platform, separate Podigee's selected setup from the provider's final execution and reporting.

## Check evidence before changing money

Qualified delivery and revenue can appear after the decision. Confirm the measurement rule and qualification window before calling a request lost or unpaid.

Do not create a manual adjustment just to make a chart match an expectation. Use **Reconciliation** when the decision, audience analytics, delivery evidence, and finance evidence do not converge.

## Confirm the correction

After one correction:

1. Run the current Campaign checks when a connected record changed.
2. Make sure the exact version is ready.
3. Test one representative request when the change affects delivery.
4. Recheck the decision reason and fallback.
5. Watch the Flight pace and fill trend for the next valid processing window.

Do not make several unrelated changes before the next check. You need to know which correction changed the result.

## When to escalate

Escalate when the same exact request still receives the wrong result after one correct repair, when the delivery version and decision version disagree, or when evidence could affect a buyer promise, publisher payout, or invoice. Include the short Campaign, Flight, Creative, and decision references, the period, delivery method, visible reason, and correction already attempted.

## Expected result

You can explain whether the problem is real underdelivery, a valid no-fill result, delayed evidence, or wrong delivery. You can correct one cause at a time and verify that the decision, playback, analytics, qualified delivery, and money evidence remain consistent.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.podigee.com/documentation/grow-and-monetize/monetization/diagnose-underdelivery-no-fill-or-wrong-delivery.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.