> 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/follow-one-ad-from-request-to-money.md). # Follow one ad from request to money Follow one podcast audio ad from the listener request to qualified revenue. This tutorial follows one podcast audio ad through the Podigee Audio Video Ad Server. You will find the request-level ad decision, confirm the Campaign result, understand the audience record, and see how qualified revenue enters month-end preparation. This tutorial uses a direct-sold audio Campaign. The same evidence model also supports other delivery sources, but the available details can differ by platform. ## Before you start You need: * Access to **Monetization**, Campaigns, delivery evidence, and revenue evidence. * One active audio Campaign with a ready creative and an eligible podcast ad break. * One listener request during the Campaign schedule. * The approximate request time, podcast, episode, and Campaign name. Complete [Launch your first direct-sold audio campaign](/documentation/grow-and-monetize/monetization/launch-your-first-direct-sold-audio-campaign.md) before you use this tutorial. ## 1. Start with the listener request Use the normal public episode from the Podigee RSS feed. Play or download the episode in a podcast app or another normal listener client. The RSS feed keeps its usual episode and enclosure structure. Podigee selects and places the eligible audio ad when the client requests the audio. The listener does not need a special ad URL. A stable episode URL lets Podigee apply the current eligible Campaign rules while the delivery system keeps reusable media parts cached. Wait for the request to complete. Delivery evidence and audience analytics can need additional processing time after playback starts. ## 2. Find the ad decision 1. Go to **Monetization > Campaigns**. 2. Open the Campaign that you expect to serve. 3. Select **Explain delivery**. 4. Filter the list by the Campaign, **Ad selected**, and **Podcast audio**. 5. Use the request time, podcast, and episode to find the correct row. 6. Open the decision. ![An audio ad decision with an ad selected, the podcast audio delivery method, the decision time, and one filled ad slot.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-0ab75b36a50e04a55365a6efc1665b6702aa2e4c%2Fdoc-monetization-006-ad-decision.jpg?alt=media) *The decision page shows the recorded result. Opening it does not serve another ad.* Confirm these fields: * **Result** is **Ad selected**. * **Delivery method** is **Podcast audio**. * **Decided** matches the request time. * **Ad slots** shows the expected filled result. If you cannot find the decision, expand the time range. Then remove one filter at a time. Do not assume that the Campaign served only because it was active. ## 3. Check what Podigee selected Use the decision page to check: * The customer-readable reason for the result. * The selected Campaign and creative. * The podcast, episode, and ad break. * The privacy mode for the request. * The qualified value, if the delivery evidence already passed the measurement rule. Use **Replay recorded decision** only to investigate the saved evidence. This action does not send another ad to a listener. It does not reserve inventory or create another billable event. The page shows shortened references for normal work. Use the copy action when Support or another operator needs the complete reference. ## 4. Confirm the audio result The decision records which ad Podigee selected for that request. The delivery system then returns the episode audio with the selected creative at the eligible break. You can listen to the public episode near the ad break as a practical check. A later playback can receive a different decision, so it cannot prove what happened in the earlier request. Use the recorded decision as the source for the earlier request. If the player cannot load the episode, first check the public episode without Campaign filters. If the episode works but the ad is missing, check the decision reason, creative readiness, break eligibility, and Campaign schedule. ## 5. Keep audience analytics and ad evidence separate Open the episode in the normal podcast area, then open its **Analytics** page. Downloads and streams show audience activity after the analytics pipeline processes the request. Audience analytics and commercial ad evidence answer different questions: | Record | Question it answers | | --------------------- | ----------------------------------------------------------- | | Ad decision | Which ad did Podigee select for this request, and why? | | Episode analytics | Did the episode request qualify as audience activity? | | Qualified ad delivery | Did the ad evidence meet the Campaign measurement rule? | | Qualified revenue | What commercial value did the qualified ad delivery create? | Do not expect the totals to match one for one. One audience download can include several ad slots. An ad decision can also fail a later qualification rule. Processing times can differ. ## 6. Confirm qualified delivery and revenue Return to the Campaign. Find **Delivery, pace, and revenue**. ![A live audio Campaign with six delivered impressions, 49,994 remaining impressions, EUR 0.17 in qualified revenue, and the latest delivery evidence.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-a946a9a5380fedce757c9fbfe7ddaffe0d61eb9b%2Fdoc-monetization-005-delivery-and-revenue.jpg?alt=media) *The Campaign view adds qualified deliveries and revenue to the Flight totals.* Confirm that: * The Flight has qualified delivery. * The delivered quantity increased. * The remaining quantity decreased. * Qualified revenue is present. * The latest delivery evidence time is current for the request. The decision page shows the value for one request. The Campaign page shows the aggregate for the Flight. Qualified revenue is accrued revenue. It is not yet an issued buyer invoice or an approved publisher payout. ## 7. Preview the month-end result Go to **Monetization > Evidence & Money** and select **Prepare month-end**. 1. Select the publisher legal entity. 2. Select the settlement month. 3. Select the buyer invoice tax rate. 4. Select **Update preview**. ![The month-end preparation page with 26 verified delivery entries, two buyers, EUR 0.62 in publisher revenue, and 26 earlier deliveries carried forward.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-3e4f3e15e6be2a1ef2d27e40b48fa551bf47242b%2Fdoc-monetization-006-month-end-preview.jpg?alt=media) *The preview groups unsettled qualified deliveries before Podigee creates draft invoices and publisher earnings.* The preview is an aggregate. It shows the delivery entries, buyers, publisher revenue, and carried entries that Podigee can prepare. It does not show one invoice for each listener request. Stop at the preview unless you are completing the month-end workflow. **Prepare draft records** creates finance records that require the configured review steps. ## If the numbers do not agree Check these items in order: 1. Confirm that you opened the exact decision for the request time. 2. Confirm that the decision used the expected Campaign, creative, episode, and ad break. 3. Check whether the ad delivery has a qualified value. 4. Check the Campaign currency and Flight measurement unit. 5. Check that the Campaign performance date covers the request. 6. Check the publisher and settlement month in the month-end preview. 7. Allow time for audience, delivery, and finance processing. Use the copied decision reference when you ask another operator or Support to investigate. Do not create replacement delivery or finance records to force the totals to match. ## Result You followed one listener request through its ad decision, podcast audio delivery, audience analytics, qualified Campaign delivery, accrued revenue, and month-end preview. You can now explain what served, why it served, and how the result enters the commercial workflow. Next, learn how to [Launch your first direct-sold audio campaign](/documentation/grow-and-monetize/monetization/launch-your-first-direct-sold-audio-campaign.md) with a different target or schedule, or continue to the first video Campaign tutorial when it is available. --- # 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/follow-one-ad-from-request-to-money.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.