> 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/replace-revoke-or-roll-back-a-delivery-version.md). # Replace, revoke, or roll back a Delivery version Replace a live Campaign setup, restore the last healthy setup, or withdraw delivery permanently. Use these controls when a published Campaign setup must stop controlling new ad decisions. Choose the action from its business effect. Each action keeps an exact record of the reason, effective time, selected setup, and review decision. ## Choose the correct action | Need | Action | Result | | -------------------------------------------------- | ------------------------------------- | ------------------------------------------------------------- | | Move new requests to another verified setup | **Switch to replacement** | The selected replacement controls new requests permanently. | | Restore the setup that the current launch replaced | **Roll back to last healthy release** | The direct previous setup controls new requests again. | | Stop this publication with no option to resume it | **Revoke publication** | New paid ad decisions from this publication stop permanently. | | Stop delivery for a limited time | **Pause new ad decisions** | The same verified setup can resume later. | Use [Pause or resume paid delivery](/documentation/grow-and-monetize/monetization/pause-or-resume-paid-delivery.md) when the stop is temporary. Do not revoke a publication that you expect to resume. ## Before you start Confirm these requirements: * The Campaign has a published delivery setup. * You have permission to control Campaign delivery. * You know whether the change must start now or at a future time. * You have the business reason for the change. * The replacement or previous setup is available when the action requires one. Your organization's review rule can make a review optional, require your own confirmation, or require approval from another authorized person. Podigee applies that rule to the exact action and delivery setup. ## Switch to a verified replacement Use a replacement for a planned, permanent handover. The replacement must already be active and verified. If the current setup is active, pause it before the replacement takes control. 1. Open **Monetization > Campaigns**. 2. Select the Campaign. 3. Select **Launch readiness**. 4. Find **Live delivery controls**. 5. Select **Switch to replacement**. 6. Confirm the Campaign and current delivery state. 7. Keep **Verified replacement is ready** as the reason. 8. Select the verified replacement. 9. Keep the current time for an immediate change, or select a future time. 10. Read the permanent effect and select the confirmation checkbox. 11. Complete the required review, or select **Switch to replacement** when the action is available. ![The current One Podigee replacement confirmation shows the Campaign, current state, effective time, verified replacement, review rule, and permanent effect.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-74f3b0a7336cee5ba6ab84d373b5deecce797cd5%2Fdoc-monetization-063-replacement-confirmation.png?alt=media) *New requests move only after Podigee confirms the selected replacement with the delivery system.* Wait until the old setup shows **Replaced**. Confirm that the selected replacement is the active setup before you close the task. ## Roll back to the last healthy setup Use a rollback when the current launch has a problem and the direct previous setup is still safe. Podigee allows only the setup that the current launch directly replaced. This rule prevents an operator from restoring an unrelated or outdated setup. 1. Open the Campaign's **Launch readiness** page. 2. Find **Live delivery controls**. 3. Select **Roll back to last healthy release**. 4. Confirm the Campaign and current delivery state. 5. Confirm **Restore the previous healthy release** as the reason. 6. Confirm the selected previous healthy setup. 7. Keep the current time for an immediate rollback, or select a future time. 8. Read the effect and select the confirmation checkbox. 9. Complete the required review, or select **Roll back to last healthy release** when the action is available. ![The current One Podigee rollback confirmation shows the direct previous setup, business reason, effective time, review rule, and effect on new requests.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-13358b24ce66cf192be3066e67caf63f5ae456c9%2Fdoc-monetization-063-rollback-confirmation.png?alt=media) *A rollback restores only the direct previous healthy setup and keeps the failed launch as evidence.* Wait until the previous setup shows **Active** and the replaced setup shows **Replaced**. Check the Campaign in **Monetization > Operations** if Podigee reports a verification problem. ## Revoke a publication permanently Use revocation when this publication must never resume. Examples include a completed Campaign, a withdrawn commercial agreement, or a permanent rights withdrawal. 1. Open the Campaign's **Launch readiness** page. 2. Find **Live delivery controls**. 3. Select **Revoke publication**. 4. Confirm the Campaign and current delivery state. 5. Select **Publication must be withdrawn** or **Campaign is complete** as the reason. 6. Keep the current time for an immediate revocation, or select a future time. 7. Read the permanent effect and select the confirmation checkbox. 8. Complete the required review, or select **Revoke publication** when the action is available. ![The current One Podigee revocation confirmation shows the Campaign, permanent effect, business reason, effective time, and review rule.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-a641c811de5e16c904bc57919e7ca70aa156d549%2Fdoc-monetization-063-revoke-confirmation.png?alt=media) *A revoked publication cannot resume. Use a new verified publication if the Campaign must deliver again.* Wait until the delivery state shows **Revoked**. New paid ad decisions from the publication stop. Playback that already has an assigned presentation follows its recorded boundary. ## Understand review and verification The review protects the business decision. The delivery verification protects playback. These are separate checks. * An optional review lets you proceed now or ask a teammate for advice. * A solo confirmation records the decision without a second person. * An independent review requires another authorized person to approve the exact action. * Delivery verification confirms the exact selected setup before the displayed state changes. If delivery verification fails, the last confirmed state remains in control. Do not repeat the action while Podigee shows that verification or a retry is in progress. ## Check connected delivery destinations Podigee controls the confirmed state for Podigee RSS and HLS delivery. A connected platform can control its own final execution. After a replacement, rollback, or revocation, open **Monetization > Integrations** and confirm the destination state when the Campaign also uses a connected platform. ## Expected result The selected action changes only new ad decisions after the delivery system confirms it. A replacement moves new requests to another verified setup. A rollback restores the direct previous healthy setup. A revocation stops the publication permanently. Podigee keeps the reason, review, effective time, and delivery result as evidence. --- # 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/replace-revoke-or-roll-back-a-delivery-version.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.