> 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/prepare-episode-ad-breaks.md).

# Prepare episode ad breaks

Prepare before-episode, during-episode, and after-episode ad breaks for exact audio and video media, with clear capacity and fallback rules.

An ad break defines where advertising may run in an episode. The Podigee Audio Video Ad Server can suggest before-episode, during-episode, and after-episode breaks for the exact audio and video versions that you select.

The suggestions are a starting point. They do not become approved placements automatically. Check the position, capacity, media, and fallback behavior before you use them.

## Before you start

You need:

* Access to **Monetization** and permission to edit episode breaks.
* A show and episode with ready source media.
* Current publisher authority for the episode.
* A decision about which media and break types you can sell.
* The review rule that applies to episode placements.

## 1. Open the episode in Break Canvas

1. Go to **Monetization > Inventory**.
2. Select **Review episode breaks**.
3. Select the episode.
4. Check the exact episode, audio, and video revisions shown under **Episode and media**.

If a source is not ready, revoked, or replaced by a later revision, prepare the current source before you continue.

## 2. Choose where ads may run

Under **Suggest useful breaks**, select one or more positions:

* **Before the episode** creates a pre-roll candidate at the start.
* **During the episode** creates a mid-roll candidate inside the program.
* **After the episode** creates a post-roll candidate at the end.

Select **Audio**, **Video**, or both under **Apply to**. Select both only when both source versions are ready and the placement must remain aligned across them.

![The break suggestion settings with before, during, and after the episode selected for audio and video.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-cbcda71d2a2cd0cecd3f3d08244866d692b03774%2Fdoc-monetization-025-break-suggestion-settings.jpg?alt=media)

*Choose the break types and media before Podigee prepares the episode plan.*

## 3. Set the break capacity

Use these controls to define the commercial capacity of each suggested break:

* **Ads in this break** sets the maximum number of ad slots.
* **Maximum break duration** limits the total ad time in the break.

The ad slot count and total duration work together. For example, two slots in a one-minute break can hold up to two ads, but their combined duration must stay within one minute. The decision engine can use fewer slots when eligible ads do not fit.

Do not add capacity only because the form permits it. Choose a pod size that protects the listening or viewing experience and matches the commercial plan.

## 4. Choose what happens when ads do not fill the break

Set two separate rules:

* **If not every ad slot is filled** controls a partly filled break.
* **If no paid ad is available** controls a break with no eligible paid ad.

**Play the episode without an ad** preserves clean content when Podigee cannot fill the slot. A workspace can also use a house promotion where that option is permitted. Choose the rule that matches the publisher policy. Do not use a house promotion without current rights and a ready creative.

## 5. Create the suggestions

1. Check the selected positions, media, capacity, and fallback rules.
2. Select **Suggest breaks**.
3. Wait until **Break suggestions are ready** appears.
4. Check the number of prepared breaks.

Podigee creates separate draft placements for the selected audio and video sources. Each placement stays bound to the exact source revision used to prepare it.

![Three prepared breaks for the start, middle, and end of the episode, with two ad slots in the first break.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-94109b18ceff62a574cb57be27d906a7944cf07b%2Fdoc-monetization-025-prepared-breaks.jpg?alt=media)

*Prepared breaks are drafts. Check each boundary and its capacity before you confirm it.*

## 6. Review each prepared break

For every break, check:

* The position and suggestion label.
* The confidence indicator.
* The number of ad slots.
* The maximum break duration.
* The partly filled and no-fill behavior.
* The audio and video source revisions.

The confidence indicator describes the quality of the suggested boundary. It is not an approval. Pay extra attention to lower-confidence mid-roll positions.

![A suggested mid-roll with its exact position, two-slot capacity, one-minute limit, and clean-content fallback rules.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-d28c7d85200bc68dbb3253b2b1faacf10fb67866%2Fdoc-monetization-025-break-capacity-and-fallback.jpg?alt=media)

*The prepared break keeps editorial position, commercial capacity, media, and fallback behavior in one place.*

## Add an exact custom break

Use **Custom position** when you already know the exact timecode:

1. Enter the position in the episode.
2. Select **Add custom break**.
3. Review the new draft under **Prepared breaks**.
4. Refine its capacity and fallback rules before you use it.

The timecode must be inside the selected source duration. A custom position is still a draft and must follow the same review rule as a suggestion.

## Prepare breaks across a catalog

Break Canvas works on one exact episode and its current media revisions. For a catalog, process episodes in controlled batches:

1. Start with current and high-demand episodes.
2. Apply the publisher's normal break and fallback policy.
3. Review low-confidence and custom positions before routine positions.
4. Finish the exact placement review for each episode.
5. Record episodes that need new media, rights, or editorial work.

Do not copy one episode's timecodes to another episode. Each episode has its own content timeline and source revisions. Use the back-catalog and future-episode supply workflow to manage coverage without treating unreviewed positions as sellable.

## If Podigee cannot prepare the breaks

* **The source is not ready:** Finish source preparation, then reopen Break Canvas.
* **The media changed:** Select the current revision and prepare the suggestions again.
* **The custom position is outside the episode:** Enter a timecode inside the source duration.
* **A selected format is unavailable:** Use the ready format or repair the missing source.
* **Preparation stays in progress:** Check **Operations** for the recorded preparation and retry only after its state is clear.
* **A suggestion is not a suitable editorial boundary:** Move it in Break Canvas or create a custom break. Do not confirm an uncertain position.
* **The fallback is not permitted:** Select a rule allowed by the active publisher policy.

## Result

The episode has draft pre-roll, mid-roll, or post-roll placements for the selected audio and video revisions. Each break has a defined position, slot count, duration limit, and fallback rule.

Next, use Break Canvas to audition and fine-tune the exact boundaries before review.


---

# 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/prepare-episode-ad-breaks.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.