> 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/test-the-exact-campaign-setup-before-publication.md).

# Test the exact Campaign setup before publication

Prepare and test the exact Campaign setup before publication, understand the current result, and resolve blockers without changing live ad delivery.

The Podigee Audio Video Ad Server can test the exact Campaign setup before you publish it. The test checks the Campaign, capacity, Creative coverage, delivery setup, and connected destinations. It does not change live ads.

Run this test after the Campaign setup is complete and before you start the publication workflow. Run it again after any change to the Campaign or its connected records.

## Before you start

Confirm that the Campaign has:

* Approved commercial terms.
* Reserved Inventory.
* Eligible audio or video Creatives for each planned delivery path.
* Complete targeting, pacing, frequency, and separation rules.
* Prepared episode ad breaks when the Campaign needs them.
* Current connections for each selected delivery destination.

You need permission to run Campaign launch checks.

## Open the exact Campaign setup

1. Open **Monetization**.
2. Open **Campaigns**.
3. Select the Campaign that you want to test.
4. Open **Launch readiness**.

The launch checklist shows whether the commercial, Inventory, Creative, and Campaign setup is ready. It also shows whether the latest check still matches the current setup.

![The current One Podigee Launch readiness page shows a Campaign that needs a new check because its setup changed after the earlier result.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-2c681099d77aa53179281b29ceece806f8f3ffe8%2Fdoc-monetization-051-refresh-needed.jpg?alt=media)

*A prior result is not valid after the Campaign setup changes.*

## Prepare and check the Campaign

Select **Prepare and check Campaign** when **Campaign setup** or **Launch checks** shows **Refresh needed**.

Podigee prepares one exact Campaign setup from the current:

* Commercial agreement and delivery goals.
* Inventory package and reservation.
* Flights, targeting, pacing, priority, frequency, and separation.
* Creative assignments, rights, tracking, and prepared media.
* Episode content, ad breaks, and delivery methods.
* Connected destination capabilities and current integration checks.

The check uses this prepared setup to verify the planned audio and video delivery paths. It checks that Podigee can make the required decisions, use the prepared media, produce the required delivery output, apply tracking, and use a safe fallback when a planned ad cannot run.

The check also records the business effects that publication can enable. It does not create billable delivery, change the active Campaign, or replace the live setup.

## Review the current result

Wait until the operation completes, then review **Launch checks** and **Next action**.

The result can be:

| Result         | Meaning                                                          | Action                                                       |
| -------------- | ---------------------------------------------------------------- | ------------------------------------------------------------ |
| Passed         | The exact prepared setup passed the current checks.              | Continue to Launch readiness.                                |
| Blocked        | One or more required checks failed.                              | Follow the displayed next action, then run the checks again. |
| Refresh needed | The Campaign or a connected record changed after the last check. | Prepare and check the Campaign again.                        |
| In progress    | Podigee is still running the checks.                             | Wait for the result.                                         |

![The current One Podigee Launch readiness page shows a current Campaign setup with a blocked result and the next action to renew Apple Podcasts delivery checks.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-166215fb20c76fd5a215a40dbc49b9d237bd8399%2Fdoc-monetization-051-current-result-blocked.jpg?alt=media)

*A blocked result protects live delivery and gives you the next safe action.*

In this example, the Campaign, Inventory, Creative coverage, and prepared setup are ready. The current check blocks publication because the approved Apple Podcasts connection test is no longer current. The operator must open **Integration checks**, renew the connection evidence, and run the Campaign checks again.

## Understand exact and current results

Each result belongs to one exact prepared Campaign setup. A change to a Flight, Creative, reservation, ad break, targeting rule, delivery method, or connected destination can make the result out of date.

Podigee keeps the earlier result for traceability, but it does not use that result to approve a changed setup. The earlier live Campaign also remains unchanged while you correct and test the new setup.

A passed local or nonproduction check confirms the behavior that Podigee can verify in that environment. It does not replace a provider certification or a production connection test when the destination controls final delivery.

## After the test passes

Continue to **Launch readiness**. Review every checklist area and complete the configured publication review. A passed test does not publish the Campaign by itself.

## Expected result

The exact Campaign setup has a current test result. If every required check passes, the setup can continue to publication review. If a check blocks the setup, live delivery remains unchanged and the page shows the next action that the operator must complete.


---

# 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/test-the-exact-campaign-setup-before-publication.md?ask=<question>&goal=<endgoal>
```

`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.