> 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/publish-a-campaign-setup.md). # Publish a Campaign setup Publish the exact Campaign setup that passed Launch readiness, confirm activation, and keep the previous delivery setup safe if publication cannot finish. Publication moves one checked Campaign setup into delivery. The Podigee Audio Video Ad Server does not rebuild the Campaign during this action. It publishes the exact setup that passed the current launch checks and required reviews. ## Before you start Open **Launch readiness** for the Campaign. Continue only when the page shows: * Commercial approval is **Ready**. * Inventory and reservation are **Ready**. * Creative coverage is **Ready**. * Campaign setup is **Ready**. * Launch checks are **Passed**. * Publication review is complete or can be confirmed during publication. If one area is not ready, follow the displayed next action. Do not use the result of an earlier Campaign setup. ## Confirm the setup that will go live Review the **Prepared Campaign setup** before you publish. The setup reference and version fingerprint identify the exact checked version. Use the copy controls when you need to include these references in a support request or an audit record. Also check **Current delivery state**. An earlier approved setup can stay active while you prepare a new one. The new changes do not affect listeners until publication succeeds. ![The current One Podigee Launch readiness page shows every required area ready, the publication confirmation, the active earlier delivery setup, and the exact prepared Campaign setup.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-b084c1e94404e4a34193ece7fb0c51ef0c5e4fbb%2Fdoc-monetization-054-ready-to-publish.png?alt=media) *Confirm the complete checklist and the exact prepared setup before publication.* ## Publish the Campaign 1. Open **Monetization**. 2. Open **Campaigns**. 3. Select the Campaign. 4. Open **Launch readiness**. 5. Check the six readiness areas and the prepared setup reference. 6. Select **Confirm and publish Campaign**. This confirmation applies only to the displayed setup. If your workspace requires an independent reviewer, complete that review before the publication control becomes available. ## Wait for delivery confirmation Publication can take a short time. Podigee keeps the previous active setup in use while the new setup is being checked and activated. Do not select the publication action again while the page shows that publication is in progress. ![The current One Podigee Launch readiness page shows that Campaign publication is in progress while the previous active setup remains available.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-b67fd63f5c184776489b47d79527a3cef0afc38b%2Fdoc-monetization-054-publication-in-progress.png?alt=media) *Publication is complete only after the delivery services confirm the new setup.* Refresh the page after the operation finishes. Confirm that **Current delivery state** is **Active** and that the active delivery version matches the setup that you published. ## If publication cannot finish A failed activation must not replace a healthy live setup. When Podigee cannot activate the new setup: * The new setup stays out of live delivery. * The earlier healthy setup remains active. * The page shows the failed step and the next safe action. * Podigee can retry a temporary failure automatically. Do not treat a queued retry as a successful publication. Check the delivery state and active version after the retry finishes. ![The current One Podigee Launch readiness page shows that publication will retry, the new setup is not live, and the earlier setup remains active.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-2d0d04c73cf2709c71fe333d80410d09f8269113%2Fdoc-monetization-054-safe-publication.png?alt=media) *A failed publication does not replace the earlier healthy delivery setup.* If the problem continues, open **Operations** and review the failed publication or connected integration. Correct the cause, run Launch readiness again when required, and publish the current exact setup. ## Use live delivery controls The page provides controls for an active Campaign: * **Pause new ad decisions** stops the Campaign from entering new request-time decisions. It does not delete the Campaign or its evidence. * **Roll back to last healthy release** restores the most recent healthy delivery setup when the current one has a delivery problem. * **Revoke publication** removes the Campaign from new delivery decisions. Use this action only when the Campaign must no longer serve. Read the confirmation dialog before you use a live control. The control applies to delivery, not to the underlying Campaign plan, Creative files, or historical evidence. ## Expected result The exact checked Campaign setup becomes the current active delivery version. New eligible requests can use it, and Podigee records the publication result. If activation fails, the previous healthy setup continues to protect live delivery until a valid replacement is active. --- # 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/publish-a-campaign-setup.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.