> 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/enable-a-show-for-dynamic-ad-delivery.md). # Enable a Podigee show for dynamic ad delivery Prepare a Podigee show in shadow mode, check every safe-switch requirement, activate dynamic ad delivery, and keep a verified route back to the existing Podigee audio. Show activation connects one Podigee podcast to the Podigee Audio Video Ad Server. Podigee first prepares and checks the new delivery path in shadow mode. Listeners stay on the existing delivery path until an authorized operator makes the coordinated switch. ## What stays the same Enabling dynamic ad delivery does not create a second podcast. These items stay stable: * The Podigee RSS feed address. * The podcast and episode records. * The episode GUIDs used by podcast apps. * The published episode history. For eligible RSS audio, the active setup can change the episode enclosure to a verified Podigee Ad Server media route. Shadow checks, a stopped setup, or a rollback keep the existing Podigee delivery route in use. Spotify remains a separate destination because Spotify controls its own hosting, insertion, and playback. ## Before you start Confirm that: * The show is published. * At least one public episode has its clean source media. * The show belongs to the selected Monetization workspace. * The workspace has the delivery package and integrations required for this show. * You have permission to configure podcast delivery. You need the separate activation permission to make the live switch or return an active show to the existing Podigee delivery path. ## Open the podcast delivery setup 1. Open **Monetization**. 2. Open **Integrations**. 3. Select the podcast in the workspace selector. 4. Find **Podcast delivery**. The **Current delivery mode** card shows whether the podcast is not connected, running shadow checks, live, or disabled. ![The current One Podigee Integrations page explains that bulk preparation does not change listener delivery and that live activation remains a separate action.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-25d17dcd4113059544faf1e3eb0d22fe7c87935c%2Fdoc-monetization-055-integration-safety-current.png?alt=media) *Prepare and verify a selected podcast before you change any public media route.* When a podcast is in **Shadow checks**, Podigee can prepare and verify delivery without changing what listeners receive. The card keeps **Stop shadow checks** and **Check delivery again** available so you can stop preparation or refresh the evidence without changing the live route. ![The current One Podigee podcast delivery card shows Shadow checks and confirms that the existing delivery stays live.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-eb5752971b2917492c4841bbb6470ecd61fdbd83%2Fdoc-monetization-055-shadow-mode-current.png?alt=media) *Shadow checks are preparation work. They are not a live delivery switch.* ## Start shadow checks Select **Start shadow checks**. The confirmation states that existing listener delivery will not change. ![The current One Podigee confirmation dialog starts shadow checks for Cedar Vale Stories and states that existing listener delivery will not change.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-0a48f23825438403b5d897f5e3c75841584ef90c%2Fdoc-monetization-055-start-shadow-confirmation.png?alt=media) *Shadow checks do not move listeners to the new delivery path.* Confirm the action. Podigee creates an exact binding between the podcast, Monetization workspace, delivery environment, and verification run. It then prepares the media and delivery evidence in the background. ## Read the safe-switch checks The page checks these areas: | Check | Required result | | --------------------------------- | ----------------------------------------------------------------------------------------- | | Podcast and workspace are bound | The selected show belongs to the exact Monetization workspace and delivery environment. | | Clean episode masters are ready | Every affected public episode has a verified source before intros, outros, or ads. | | Delivery package is verified | One complete delivery package passed its safety checks. | | Episodes are prepared | Every affected episode matches the verified package. | | Listener measurement is protected | Audience analytics and the reporting destination are verified for every affected episode. | | Recovery path is verified | Podigee can return every public episode to its exact existing audio. | | Public media routes are verified | Every listener-facing route matches the prepared episode state. | | The switch is coordinated | The live setup can point to one exact verified publication in one operation. | ![The current One Podigee Integrations page shows Cedar Vale Stories in shadow mode, the existing delivery safety notice, the recheck control, and the safe-switch checklist.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-420a27a5d3c2ed105bfe4b6aad2788ec3863ea1c%2Fdoc-monetization-055-shadow-checks.png?alt=media) *Use shadow mode to prepare and verify delivery while the existing podcast stays live.* The checklist makes an incomplete switch visible. It shows which prerequisite still needs work and keeps the podcast in the safe shadow path until the complete set of checks passes. ![The current One Podigee safe-switch checklist shows the binding, media, package, episode, measurement, recovery, route, and coordinated-switch checks.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-cc43fbfe59ae5ecc5daa234040516dfd1559ee0e%2Fdoc-monetization-055-switch-checks-current.png?alt=media) *An incomplete check protects the existing listener route. It does not mean that the podcast is unavailable.* If a check is incomplete, follow the reason shown below the checklist. Select **Check delivery again** after you correct the problem. The new verification run must match the current podcast, workspace, media, delivery package, routes, analytics binding, and recovery path. ## Switch the show to live delivery The live switch becomes available only when all safe-switch checks pass and you have activation permission. 1. Confirm that every safe-switch item is complete. 2. Confirm that the delivery binding matches the selected podcast and workspace. 3. Select **Switch live delivery to Podigee Ad Server**. 4. Read the confirmation and confirm the switch. Podigee activates the exact verified release. It also keeps the verified existing Podigee audio as the recovery path. The RSS feed and episode GUIDs stay the same. Eligible RSS enclosures start using the verified dynamic delivery route. ## Verify the active result After the switch, confirm: * **Current delivery mode** shows the Podigee Ad Server as live. * **Binding status** matches the podcast and Monetization workspace. * **Last verified delivery** identifies the active publication. * Every safe-switch check remains complete. * The page confirms that the recovery path is ready. If the active route needs another verification, the page keeps the show visible as live but blocks an unsafe return action. Select **Check delivery again** and correct the displayed blocker. ![The current One Podigee Integrations page shows Harbor and Pine Business Review live on the Podigee Ad Server, with recovery verification still required before the return control becomes available.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-ac992861d771198c9c4ac80b118635f5faed9e5c%2Fdoc-monetization-055-active-verification-needed.png?alt=media) *A live show does not offer an unverified return action.* ## Return to existing Podigee delivery Use **Return to existing Podigee delivery** when an active show must leave the dynamic route. The control becomes available only after Podigee verifies the exact existing audio and the transition evidence. Confirm the return action. Podigee moves listener delivery back to the verified existing route, records the transition, and starts a fresh shadow verification run. The RSS feed address, episode GUIDs, and podcast history stay unchanged. ## Stop shadow checks Select **Stop shadow checks** when the podcast is in shadow mode and you do not want Podigee to continue preparing the new route. The confirmation makes clear that existing listener delivery will remain unchanged. Stopping shadow checks does not delete the podcast or its history. You can start a new shadow run later. An active show cannot use this action because a live route must use the coordinated return process. ## Expected result The show moves through an explicit and reversible path: existing delivery, shadow verification, verified activation, and a verified return when needed. Podigee changes only the eligible delivery route. The public podcast identity and its RSS feed remain stable throughout the process. --- # 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/enable-a-show-for-dynamic-ad-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.