> 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/verify-one-real-audio-or-video-delivery.md). # Verify one real audio or video delivery Verify one real Podigee RSS audio or HLS video request from playback to qualified revenue. Use this task after you publish a Campaign. It checks one real request through the Podigee Audio Video Ad Server. You will confirm the played result, the recorded ad decision, audience activity, qualified delivery, and revenue. Use a Podigee-controlled RSS or HLS delivery for this check. A connected platform can control its own final playback and reporting. For example, Spotify sends its final results back through the Spotify integration. ## Before you start You need: * Access to **Monetization**, the Campaign, and **Evidence & Money**. * A published Campaign with an eligible Flight and a ready Creative. * A published episode with an approved ad break. * The normal public Podigee RSS episode or HLS presentation. * A note of the podcast, episode, expected Campaign, and approximate request time. For a precise comparison, also note the Flight's delivered quantity and qualified revenue before you start playback. ## 1. Make one real playback request Choose one delivery method: ### RSS audio 1. Open the normal Podigee RSS episode in a podcast app or another normal listener client. 2. Start playback or download the episode. 3. Let playback reach the ad break. 4. Let the Creative play for the period required by its measurement rule. 5. Note the request time. Do not use the Creative preview for this check. A preview confirms the media file, but it does not make a listener delivery decision. ### HLS audio or video 1. Open the normal published HLS presentation in a supported player. 2. Start playback and let the selected ad play. 3. For video, keep the player open until the required start, quartile, or completed-view event. 4. Note the request time. The measurement rule can qualify a video start or a completed view. Confirm the unit on the Flight before you compare the result. ## 2. Find the exact ad decision 1. Open **Monetization > Evidence & Money**. 2. Open **Live ad delivery**, then select **Recent ad decisions**. 3. Select **Ad selected** as the result. 4. Select **Podcast audio**, **Video interstitial**, or the applicable delivery method. 5. Search for the Campaign, Creative, episode, or copied decision reference. 6. Use the request time to select the correct row. ![The current One Podigee Recent ad decisions page shows one Podcast audio result after filtering by its short decision reference.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-a1654ab452ed46718e4b5981217703e7eac7ba93%2Fdoc-monetization-064-exact-decision.png?alt=media) *Use the request time and delivery method to separate this request from other listener requests.* Do not assume that the expected Campaign served only because it was active. The decision list is the record of what Podigee selected for the request. ## 3. Confirm the played result Open the decision and confirm these fields: * **Result** is **Ad selected**, or it shows the expected fallback result. * **Delivery method** matches the RSS or HLS request. * **Decided** matches the request time. * **Campaign** and **Creative** are the expected selections. * **Podcast**, **Episode**, and **Ad break** match the played content. * **Privacy** shows the rule used for the request. * **Qualified value** shows the commercial value after the measurement rule passes. ![The current One Podigee Ad decision details page connects the selected Campaign and Creative to the podcast, episode, ad break, privacy mode, qualified value, and exact delivery references.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-a6a46bc4f1c8230e01ac95b529b06c49a9b3d5f9%2Fdoc-monetization-064-decision-evidence.png?alt=media) *Use the short references for normal work. Copy the complete value when another operator or Podigee Support needs it.* The decision can appear before the qualified value. Audience and commercial processing can finish after playback. Refresh the recorded decision after the measurement window if the other fields are correct but the value is not ready. ## 4. Check audience activity Switch to the **Podcast** context. Open the episode and its Analytics page. Confirm that the request appears after the audience analytics pipeline processes it. Audience activity and qualified ad delivery are different records: | Record | What it confirms | | --------------------- | -------------------------------------------------------------- | | Episode analytics | The episode request met the audience measurement rule. | | Ad decision | Podigee selected this result for this request. | | Qualified ad delivery | The ad met the Flight's measurement rule. | | Qualified revenue | The qualified delivery created the displayed commercial value. | One audience download can contain more than one ad. The totals do not need to match one for one. ## 5. Confirm delivery and money 1. Return to **Monetization > Campaigns**. 2. Open the Campaign. 3. Find **Delivery, pace, and revenue**. 4. Find the Flight that supplied the selected Creative. 5. Confirm that the delivered quantity and qualified revenue include the new qualified result. 6. Confirm that the latest delivery evidence time covers the request. ![The current One Podigee Campaign page shows planned Flights, Flights with qualified delivery, qualified revenue, the latest evidence time, and Flight-level performance.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-9e910395ec52b2b4721cd47d6d1049e391776178%2Fdoc-monetization-064-campaign-performance.png?alt=media) *Use Flight performance to compare the exact decision with the Campaign's aggregate result.* The value on the decision is for one request. The value on the Campaign is the total for the Flight. The money is accrued qualified revenue. It is not yet an issued invoice or an approved payout. ## 6. Check safe cache reuse The delivery network can reuse verified media bytes without creating another paid result. This keeps delivery fast and controls transfer costs. Do not start a new playback session only to test the cache. A new session can correctly receive a new ad decision. If you repeat the already assigned presentation in the same playback session, confirm these results: * Playback returns the same episode and ad presentation. * A byte-range retry does not change the selected Creative. * The retry does not create a second qualified delivery or a second revenue amount. * **Operations** does not show a delivery or evidence-receipt problem for the request. Most ad operators do not need cache node details. If the presentation changes inside one playback session, a range cannot load, or delivery counts increase for a retry, copy the decision reference and ask an authorized delivery operator or Podigee Support to inspect the retained evidence. ## If the records do not agree Check these items in order: 1. Confirm that you selected the correct request time and delivery method. 2. Confirm the Campaign, Creative, episode, and ad break on the decision. 3. Confirm the Flight's measurement unit and qualification window. 4. Wait for audience and commercial processing to finish. 5. Confirm that the Campaign performance period includes the request. 6. Confirm the Campaign currency. 7. Check **Monetization > Operations** for a delivery or delayed-evidence problem. 8. Copy the decision reference before you ask another operator or Podigee Support to investigate. Do not create a manual delivery, adjustment, or finance record only to make the totals agree. First find the missing or delayed evidence. ## Expected result The played ad, recorded decision, podcast or HLS content, audience activity, qualified delivery, and revenue describe the same request. A retry of the already assigned presentation does not change the ad or create another commercial result. For more detail, read [Understand dynamic ad delivery in RSS audio](/documentation/grow-and-monetize/monetization/understand-dynamic-ad-delivery-in-rss-audio.md) or [Understand Podigee HLS audio and video delivery](/documentation/grow-and-monetize/monetization/understand-podigee-hls-audio-and-video-delivery.md). --- # 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/verify-one-real-audio-or-video-delivery.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.