> 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/pause-or-resume-paid-delivery.md).

# Pause or resume paid delivery

Pause new paid ad decisions safely, then resume the same verified Campaign setup.

Pause a Campaign when new paid ad decisions must stop for a limited time. New requests receive clean podcast content while the Campaign is paused. Resume only after you resolve the reason for the pause and confirm that the same Campaign setup is safe.

## Before you start

Confirm these requirements:

* The Campaign has a published delivery setup.
* You have permission to control Campaign delivery.
* You know why paid delivery must stop or resume.
* You understand whether the change must start now or at a future time.

Pause and resume do not change the Campaign terms, booked quantity, Creative, or targeting. Amend the Campaign when one of those commercial or delivery rules must change.

## Pause new paid decisions

1. Open **Monetization > Campaigns**.
2. Select the Campaign.
3. Select **Launch readiness**.
4. Find **Live delivery controls**.
5. Confirm that the current delivery state is **Active**.
6. Select **Pause new ad decisions**.

![The current One Podigee Launch readiness page shows an Active delivery state and the Pause new ad decisions control.](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)

*Pause is available only for a Campaign setup that is currently active.*

In the confirmation:

1. Confirm the Campaign and current delivery state.
2. Select the reason for the pause.
3. Keep the current time for an immediate pause, or select a future time.
4. Read the effect on new requests and existing playback.
5. Select **Pause new ad decisions**.

![The current One Podigee pause confirmation shows the exact Campaign, pause reason, effective time, effect on new requests, and existing playback safety.](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)

*New paid decisions stop at the chosen time. Playback that is already in progress remains safe.*

## Confirm the paused state

Wait until **Current delivery state** shows **Paused**. Podigee shows the message **Paid delivery is paused**. New requests now receive clean podcast content without a paid ad from this Campaign.

![The current One Podigee Launch readiness page shows a Paused delivery state with Resume delivery and Revoke publication controls.](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)

*Use Resume delivery for a temporary pause. Use Revoke publication only for a permanent withdrawal.*

Podigee does not count a pause request as a successful change until the delivery system confirms it. If the confirmation fails, the last confirmed delivery state remains in control.

## Resolve the reason for the pause

Before you resume, confirm that the cause is no longer present. For example:

* the correct Creative is ready;
* the Creative rights and active period are valid;
* the Campaign and inventory dates are still valid;
* the delivery connection is healthy;
* an incident or policy hold is closed.

Do not use Resume delivery to bypass a failed check. Fix the reported problem first.

## Resume paid delivery

1. Return to **Live delivery controls**.
2. Confirm that the current delivery state is **Paused**.
3. Select **Resume delivery**.
4. Confirm the Campaign and the paused state.
5. Confirm **Operator confirmed recovery** as the reason.
6. Keep the current time for an immediate resume, or select a future time.
7. Select **Resume delivery**.

![The current One Podigee resume confirmation shows that only the same verified Campaign setup can resume after delivery confirmation.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-4d354b2d6b35b864b3112709d6852ac7063e8f25%2Fdoc-monetization-062-resume-confirmation.png?alt=media)

*Podigee checks the exact verified setup before new requests can use it again.*

Wait until the current delivery state shows **Active**. Eligible new requests can then receive paid ads from the Campaign again.

## Understand the review behavior

Pause and resume are immediate operating controls. They do not require a separate human review. Podigee still checks the exact Campaign setup, media, rights, and delivery state.

Your organization can require reviews for Campaign amendments, publication, replacement, rollback, or revocation. Those reviews do not turn a temporary pause into a commercial amendment.

## Resolve a change that is still being verified

If the page shows **Delivery change is queued**, Podigee accepted the request and is checking it. Do not submit the same change again.

If the page shows that Podigee will retry:

1. Keep the last confirmed state in control.
2. Open **Monetization > Operations**.
3. Find the delivery issue for the Campaign.
4. Resolve the connection or verification problem.
5. Return to **Launch readiness** and check the state again.

## Expected result

A pause changes the confirmed state from **Active** to **Paused** and stops new paid decisions. A resume changes the confirmed state from **Paused** to **Active** only after Podigee verifies the same Campaign setup. Existing playback remains safe during both changes.


---

# 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/pause-or-resume-paid-delivery.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.