> 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/set-pacing-priority-frequency-and-separation.md). # Set pacing, priority, frequency, and separation Control delivery speed, commercial order, listener pressure, Creative rotation, separation, and safe fallback for a Campaign Flight. Use these controls to deliver a Campaign at the intended speed without showing too many ads to one listener. The Podigee Audio Video Ad Server also lets you set the commercial order, Creative rotation, brand classification, break capacity, and safe fallback. These controls have different purposes. Do not use one control as a substitute for another. ## Prerequisites Before you start, make sure that you have these items: * Permission to plan Campaigns in Monetization. * A Campaign with at least one Flight. * A current order or buyer brief with the required delivery commitment. * A published Inventory package. * Prepared episode breaks for the selected Inventory. * A prepared Creative if you want to set a rotation weight. * Brand classification and publisher rules if the order needs separation or review. ## Know what each control does | Control | Purpose | Current delivery effect | | --------------------------- | -------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Frequency cap and window | Limit how often one listener or session can receive the Flight. | Podigee withholds the Flight when the verified counter reaches the cap. Podigee also withholds it if the required counter authority is unavailable. | | Pacing | Record how the Flight should progress through its schedule. | All modes stay within the Flight goal and reservation. Current Podigee-hosted delivery does not promise a different intraday curve for each mode. A connected destination can apply its supported pacing behavior. | | Guarantee class | Set the commercial serving order. | Podigee considers Guaranteed first, then Sponsorship, Makegood, Non-guaranteed, and House demand. | | Numeric Priority | Preserve a plan value for an integration or specialist workflow. | It does not override guarantee class in current Podigee-hosted serving. Keep the current default unless verified integration guidance requires a change. | | Creative rotation weight | Rank eligible Creatives within the same Flight. | Podigee considers a higher weight before a lower weight after the commercial order. A weight is not a percentage and does not guarantee a traffic split. | | Brand separation | Record how strongly a brand should be kept apart from competitors. | It supports classification, readiness, and review. It is not a complete live adjacency guarantee in current Podigee-hosted serving. | | Break capacity and fallback | Limit the ads in one break and choose what happens when demand is missing. | The break follows its slot limit, duration limit, partial-fill rule, and no-fill fallback. | | Demand order | Set the order of direct-sold, programmatic, and house demand. | Position 1 is considered first under the active workspace policy. | ## Use safe starting values Use the authorized contract when it gives an exact value. If it does not, these values are a safe starting point for a normal direct-sold Flight: | Control | Safe starting value | Change it when | | --------------------------------- | ------------------------------- | ------------------------------------------------------------------------------------------------------------- | | Frequency cap | 3 contacts in 7 days | The buyer contract, campaign duration, or listening pattern requires a different pressure limit. | | Pacing | Even | A specialist has confirmed that the destination supports a different pacing behavior and the order needs it. | | Guarantee class | The class that matches the sale | The commercial commitment changes. Do not mark speculative demand as Guaranteed. | | Numeric Priority | Keep the displayed default | A verified provider or integration contract defines how to use it. | | Creative rotation weight | 1 for each Creative | You want Podigee to consider one eligible Creative before another. | | Competitive separation | Standard | The category needs no added separation, or the contract requires strict separation with a verified safeguard. | | Partial fill and no-fill fallback | Play the episode without an ad | An authorized house Creative is available and the publisher policy permits house fill. | Do not use a universal maximum for ads in a break. Use the active publisher policy and the prepared break capacity. Many listening experiences use one or two ads, but the correct value depends on the show, contract, break duration, and publisher policy. ## Set frequency, pacing, and commercial order 1. Open **Monetization**. 2. Select **Campaigns**. 3. Open the required Campaign. 4. Find the required Flight. 5. Select **Adjust flight**. 6. Enter the **Frequency cap**. 7. Enter the **Window in days**. 8. Select the **Pacing** mode. 9. Select the **Guarantee class** that matches the commercial commitment. 10. Keep **Priority** at its current default unless verified guidance requires another value. 11. Confirm the Flight budget and rate. 12. Enter the reason for the change. 13. Select **Save new Flight version**. ![The One Podigee Adjust flight window shows the frequency cap, window, pacing, priority, guarantee class, budget, and rate.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-aba2ed0523dbeee1892d5d96ffb1d0bc1d444a5e%2Fdoc-monetization-036-flight-delivery-controls.jpg?alt=media) *Use guarantee class for the commercial serving order. Do not use numeric Priority to override it.* Saving creates a new Flight version. Refresh the forecast and review any existing reservation against that exact version before publication. ## Understand the pacing choices * **Even** is the safest starting choice. It records that delivery should progress steadily through the schedule. * **As soon as possible** records that early delivery is preferred. * **Ahead of pace** records that the Flight should keep a buffer above an even plan. The Flight goal and reservation remain hard limits. Current Podigee-hosted delivery does not promise three different intraday delivery curves for these values. A connected destination, such as an approved provider integration, can apply the pacing behavior that its contract supports. ## Set Creative rotation 1. Open the required Campaign. 2. Find the required Flight. 3. Select **Assign creative**. 4. Select an eligible Creative. 5. Preview the audio or video asset. 6. Enter the **Rotation weight**. 7. Confirm the assignment. Start with a weight of `1` for each Creative. Use a larger value only when you want Podigee to consider that Creative before a lower-weight Creative. Do not enter `70` and `30` to promise a 70/30 traffic split. Current Podigee-hosted serving ranks by weight, but it does not promise randomized percentage delivery. If no eligible Creative appears, correct its media format, rights, review state, brand, language, markets, or assignment window. Do not weaken a rights or review rule only to make the Creative appear. ## Set brand separation and review 1. Open **Commercial accounts** from the Campaign area. 2. Open the required Commercial account. 3. Find the required brand. 4. Select **Classify brand**. 5. Select the brand categories. 6. Add the competitive categories when they are known. 7. Select **No additional separation**, **Standard separation**, or **Strict separation**. 8. Set whether the brand is sensitive. 9. Set whether publisher review is required. 10. Save the classification. ![The One Podigee brand classification window shows strict competitive separation and required publisher review.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-527cb475ba97a0a69e4592e71922d8fab9a9c5b5%2Fdoc-monetization-015-safety-and-review.png?alt=media) *Brand separation supports review. It does not prove live adjacency enforcement.* For a contractual adjacency rule, require publisher review and verify the exact delivery safeguard before launch. A saved classification is not enough for a strict separation promise. ## Set break capacity and fallback 1. Open **Inventory**. 2. Select **Review episode breaks**. 3. Open the required episode in **Break Canvas**. 4. Select the required break. 5. Set **Ads in this break**. 6. Set the **Maximum break duration**. 7. Set what happens if not every ad slot is filled. 8. Set what happens if no paid ad is available. 9. Save the exact placement. ![The One Podigee Break Canvas shows a two-slot break, a one-minute duration, and clean-content fallback for partial fill and no fill.](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) *Clean content is the safest fallback. Use house fill only when an authorized house Creative is available.* Use **Run the available ads** when the publisher permits fewer ads than the break capacity. Use **Do not run a partial break** when the break must not play a partial ad set. Keep the original content as the safe no-fill result unless the publisher has approved another fallback. ## Check the result before publication 1. Refresh the Flight forecast. 2. Confirm that the requested quantity remains available. 3. Confirm that the frequency limit matches the contract. 4. Confirm that the guarantee class matches the sale. 5. Confirm that each assigned Creative has the intended weight. 6. Confirm that brand classification and review are complete. 7. Confirm that each prepared break has the correct capacity and fallback. 8. Open **Launch checks**. 9. Resolve every blocked item before publication. ## Resolve a problem safely | Problem | Safe action | | -------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | | Delivery is too slow | Check the schedule, goal, reservation, eligible supply, frequency cap, and active policy. Do not increase numeric Priority as a general fix. | | Delivery is too fast | Check the Flight goal, schedule, reservation, and frequency cap. Use Even pacing as the safe plan value. | | One listener receives too many ads | Reduce the frequency cap or increase its window. Confirm that the delivery surface supplies the required counter evidence. | | The frequency counter is unavailable | Keep the Flight withheld. Restore the counter authority before delivery. Do not bypass the cap. | | The wrong demand wins | Check guarantee class first. Then check demand order and Creative weight. These are separate controls. | | Creative delivery does not match the intended percentage | Treat weight as ranking, not a percentage. Use delivery evidence to compare results, and do not promise a fixed split from weight alone. | | A competitor appears next to the brand | Stop the affected delivery, require review, and verify the exact adjacency safeguard. The saved brand classification alone is not a live guarantee. | | A break has empty time | Use clean content, or use an authorized house Creative when the publisher policy permits it. | | A change makes the forecast stale | Refresh the forecast for the new Flight version. Review the reservation against the same version. | | A second reviewer is unavailable | Use the configured solo or optional-review rule only when the organization permits it. Do not bypass a required independent review. | ## Expected result The Flight has a controlled frequency limit, a pacing plan, and the correct guarantee class. Eligible Creatives have intentional weights. The brand classification records the required separation and review treatment. Each prepared break has approved capacity and a safe fallback. The current forecast and launch checks apply to the same exact Flight version. Next, compare forecast scenarios before you reserve capacity or publish the Campaign. --- # 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/set-pacing-priority-frequency-and-separation.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.