> 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/understand-live-delivery-states.md). # Understand live delivery states Understand the delivery states of a published Campaign and choose a safe control action. The Podigee Audio Video Ad Server shows the confirmed delivery state of each published Campaign. Use this state to understand what Podigee does for new listener and viewer requests. Do not use a Campaign status as proof of delivered impressions. Use **Evidence & Money** for delivery results. ## Open the delivery controls Open **Monetization > Campaigns**. Select the Campaign, then select **Launch readiness**. Find **Live delivery controls**. The control shows the confirmed state and the actions that are safe for that state. For example, an **Active** Campaign can be paused, rolled back, or revoked. ![The current One Podigee Launch readiness page shows an Active delivery state with controls to pause new ad decisions, roll back, or revoke the Campaign.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-0f74b77e5b511a108476ac120aa6b75354fe2d85%2Fdoc-monetization-061-live-delivery-active.png?alt=media) *The displayed state is the last state that Podigee confirmed with the delivery system.* ## Understand each state | State | Meaning | Effect on new requests | | ----------------- | -------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- | | Scheduled | Podigee accepted a change for a future time. | The current confirmed setup stays in control until the scheduled time. | | Resuming | Podigee is checking a request to resume paid delivery. | The previous confirmed state stays in control until the check finishes. | | Active | The verified Campaign setup can take part in new ad decisions. | Eligible requests can receive paid ads according to the Campaign rules. | | Paused | Paid ad decisions are temporarily stopped. | New requests receive clean podcast content without a paid ad from this Campaign. | | Replaced | Another verified setup now controls new requests. | The replacement setup can take part in new decisions. Podigee keeps the old setup for history. | | Revoked | The setup was permanently withdrawn. | New paid decisions stop. You cannot resume this publication. | | Activation failed | Podigee could not confirm the requested setup. | The last confirmed state remains in control. The failed setup does not become live. | **Rolled back** is an action, not a permanent state. A rollback restores the last healthy setup. The setup that you rolled back becomes **Replaced**. ## Pause paid delivery Use a pause when you must stop new paid decisions but expect to resume the Campaign later. 1. Select **Pause new ad decisions**. 2. Select the reason for the pause. 3. Keep the current time for an immediate pause, or select a future time. 4. Review the effect on new requests and existing playback. 5. Select **Pause new ad decisions**. ![The current One Podigee pause confirmation explains that new paid decisions stop while playback already in progress remains safe.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-890f96ed19670130b32e51c8d17be820f5a5119d%2Fdoc-monetization-061-pause-confirmation.png?alt=media) *A pause affects new decisions. It does not break a presentation that Podigee already assigned to a listener or viewer.* Pause and resume are operating controls. They do not need a separate human review unless your organization adds a different policy outside this control. Podigee still runs its automated rights, media, and delivery checks. ## Work with a paused Campaign When the state is **Paused**, Podigee serves clean podcast content for new requests. Existing presentations continue until their defined boundary. Select **Resume delivery** only after you resolve the reason for the pause. ![The current One Podigee Launch readiness page shows a Paused delivery state with controls to resume or permanently revoke the Campaign.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-5e8aacb2db51e95c321d566c032b0a879774ef3c%2Fdoc-monetization-061-live-delivery-paused.png?alt=media) *A paused Campaign remains available for a later resume. A revoked Campaign does not.* When you resume, Podigee checks the same verified Campaign setup again. Paid decisions start only after the delivery system confirms the change. ## Choose rollback, replacement, or revocation These actions have different purposes. | Action | Use it when | Result | | --------- | ------------------------------------------------------------------- | ------------------------------------------------------------- | | Roll back | A recent change is unhealthy and the previous setup is safe. | Podigee restores the last healthy setup after verification. | | Replace | A new verified setup must permanently take control. | The new setup becomes active. The old setup becomes Replaced. | | Revoke | The Campaign must never serve paid ads from this publication again. | New paid decisions stop permanently for this publication. | Rollback, replacement, and revocation can require the configured Campaign review. The confirmation shows the exact Campaign, reason, effective time, and effect before you submit the action. ## Understand playback safety Podigee separates new ad decisions from playback that is already in progress. A pause or revocation stops the applicable new paid decisions. It does not replace media bytes inside a presentation that a listener or viewer already received. The exact boundary depends on the delivery surface: * RSS audio uses the stable presentation and range boundaries that were assigned to the request. * Podigee HLS uses the assigned playlist and media boundaries. * Apple Podcasts uses its durable HLS and interstitial bindings. * Spotify controls final insertion and playback for Spotify-managed delivery. ## Resolve a state that does not change Podigee keeps the last confirmed state when the delivery system does not confirm a requested change. This protects listeners from an uncertain partial change. 1. Read the message below **Current delivery state**. 2. If Podigee will retry, wait for the next verification result. 3. Open **Monetization > Operations** if the message asks for operator action. 4. Resolve the reported connection, media, rights, or delivery problem. 5. Return to **Launch readiness** and confirm the state again. Do not submit repeated changes while one change is still being verified. The confirmed state stays authoritative until Podigee records a successful result. ## Expected result The **Live delivery controls** show one confirmed state. The available buttons match that state. New requests follow the confirmed delivery behavior, and existing playback remains safe within its assigned boundary. --- # 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/understand-live-delivery-states.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.