> 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/explain-an-ad-decision-or-no-fill-result.md). # Explain an ad decision or no-fill result Find the result of one ad request and understand why an ad was selected or not selected. Use **Recent ad decisions** when you need to answer one question: what happened when Podigee received this request? The page shows the result, the delivery method, the reason, and the content context. It helps you investigate a no-fill result without changing delivery or billing. ## Before you start Select the correct Monetization workspace. You need permission to view delivery decisions. You need the relevant investigation permission to replay a recorded decision or inspect demand evidence. The decision pages are read-only. Opening a decision does not serve another ad, reserve inventory, change a Campaign, or create a billing event. ## Open Recent ad decisions Open **Monetization > Operations > Live ad delivery**. Select **Recent ad decisions**. ![The current One Podigee decision library shows result, delivery method, and privacy filters next to recent audio and video decisions.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-c7eb99b997ef8bfe2bd793323a7c682391d3ef15%2Fdoc-monetization-073-decisions-overview.png?alt=media) *Use the decision library to move from a delivery signal to one recorded request.* The table shows: * **Result**: what the listener or viewer received; * **Ad and Campaign**: the selected creative and the Campaign, when an ad was selected; * **Podcast and episode**: the content request that produced the decision; * **Why**: the customer-readable reason for the result; * **Delivery method**: the audio or video path used for the request; * **Decided**: when the decision was recorded. ## Find the decision Use **Find a decision** to search by a name, episode, or reference. Use the filters when you need a smaller set of results: * **Result**: choose **Ad selected**, **Partially filled**, **No ad selected**, **House ad selected**, or **Original content played**; * **Delivery method**: choose a path such as **Podcast audio**, **Video interstitial**, or **Video ad stitching**; * **Privacy**: choose the privacy state recorded for the request. Select **Apply filters**. The filter stays visible above the results. Select **Clear filters** to return to the complete list. ![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) *Keep the result filter visible while you compare the reasons for no-fill decisions.* ## Read the result Use the result and the reason together. A result is not an error by itself. | Result | Meaning | | --------------------------- | -------------------------------------------------------------------------- | | **Ad selected** | An eligible creative won the decision for the request. | | **Partially filled** | Some ad slots received an ad. At least one slot stayed empty. | | **No ad selected** | No paid ad was selected for the request. Read **Why** and the slot result. | | **House ad selected** | Podigee used an owned fallback instead of a paid ad. | | **Original content played** | The original episode or stream continued without an ad. | Common reasons include: * no eligible ad matched the targeting or schedule; * a frequency or budget rule prevented selection; * pacing withheld the Campaign for this request; * no bid arrived before the response limit; * the creative was not approved, did not have a suitable rendition, or did not have valid rights; * the requested audio or video path did not support the required format; * a privacy or jurisdiction rule prevented selection; * another delivery rule determined the result. Use the exact reason shown on the page. Do not infer a reason from the Campaign name or from one request. ## Open the decision details Select **View decision** for the row you need. The detail page explains the recorded decision in four parts. ![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) *A no-fill detail explains the result without exposing listener identity or provider secrets.* ### What happened Read **Result**, **Delivery method**, **Decided**, and **Ad slots** first. Then read **What happened**. This section repeats the reason and shows the selected Campaign and creative, when they exist. **Qualified value** tells you whether the request has qualified delivery evidence yet. For a no-fill result, **No campaign selected** and **No creative selected** are valid states. They mean that no paid Campaign or creative was used for that request. ### Where it happened Read the Podcast, episode, ad break, and privacy state. This confirms that you are investigating the correct content and break. Use **Open episode** or **Open ad break** when you need to check the source content or the break setup. ### Exact references The page shows short, copyable references for the decision, decision fingerprint, delivery release, and release fingerprint. Use the copy button when you need to share an exact record with another operator or support person. You do not need to read the full identifier on screen. ### Ad slot results The slot table shows one row for each break slot. It lists the slot result, the reason, and the Campaign and creative that were used. A no-fill decision can still contain several slots. Check every slot before you report that a whole break was empty. ## Investigate without changing delivery Use **Replay recorded decision** to reproduce the stored result. Use **Inspect demand evidence** to review the retained, redacted demand information behind the result. These actions do not serve another ad, change delivery, reserve inventory, or affect billing. They are safe first checks when a Campaign operator reports a missing or unexpected ad. If the decision shows a missing creative, targeting mismatch, schedule conflict, or unsupported delivery method, open the linked Campaign, creative, episode, or ad break and correct the source record. If the reason is not clear, copy the shortened decision reference and include the time, Podcast, episode, and delivery method in the support request. ## Example: investigate a no-fill result 1. Open **Recent ad decisions**. 2. Set **Result** to **No ad selected** and select **Apply filters**. 3. Find the affected episode and read **Why**. 4. Select **View decision**. 5. Check **What happened**, **Where it happened**, and every slot. 6. If the evidence points to a Campaign or creative problem, open that record and fix the source. 7. If the reason is still unclear, copy the shortened decision reference for support. ![The current One Podigee decision detail for a filled result shows the selected creative, delivery method, content context, and one filled slot.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-5fdd893cc5587dc1823701c9ed3690c5bd6de434%2Fdoc-monetization-073-decision-detail.png?alt=media) *The same detail view explains a successful audio or video selection and its delivery path.* ## Expected result You can explain why one request received a paid ad, a fallback, or no ad. You can identify the affected content and slot, investigate the recorded evidence safely, and give another operator an exact short reference without exposing private listener or provider data. --- # 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/explain-an-ad-decision-or-no-fill-result.md?ask=&goal= ``` `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.