> 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-targeting-exclusions-and-brand-safety.md).

# Set targeting, exclusions, and brand safety

Set governed market, content, media, exclusion, brand-safety, and data-use rules without reducing eligible supply by accident.

Use targeting to define where a Flight may run in the Podigee Audio Video Ad Server. Use exclusions and brand-safety rules to prevent delivery that the buyer, publisher, or workspace does not permit.

Start with the buyer's exact requirements. Add only the limits that the order or your publishing policy requires. Each added limit can reduce the eligible supply.

## Prerequisites

Before you start, make sure that you have these items:

* Permission to plan Campaigns in Monetization.
* Permission to manage revenue and data rules if you must change workspace policies.
* A Campaign with at least one Flight.
* A published Inventory package with the required shows, episodes, media, markets, and categories.
* An authorized buyer brief or order.
* A current capacity forecast after you finish the changes.

## Know where each control belongs

Podigee does not use every planning field as a live delivery filter. Use the correct control for each requirement.

| Requirement                                   | Where to control it                            | Delivery effect                                                               |
| --------------------------------------------- | ---------------------------------------------- | ----------------------------------------------------------------------------- |
| Country market                                | Campaign proposal and exact Flight targeting   | Direct match against the governed country code.                               |
| Content category                              | Exact Flight targeting                         | Direct match against the governed content category.                           |
| Audio or video                                | Flight media kind                              | Direct match against the requested media type.                                |
| Show or episode                               | Inventory package and approved episode breaks  | Limits the first-party supply that the Flight can use.                        |
| Platform or channel                           | Flight delivery destination                    | Limits where Podigee sends or serves the ad.                                  |
| Language                                      | Creative language and content metadata         | Describes the asset and content. It is not a general Flight filter.           |
| Audience description                          | Campaign buyer brief                           | Records the intended audience. It is not a live audience-segment filter.      |
| Device, precise location, or personal segment | Connected provider capability, when available  | Podigee does not infer these values or expose them as general Flight filters. |
| Consent and permitted data use                | Monetization settings > Revenue and data rules | Limits which verified signals and data uses a decision may use.               |

The current Podigee-controlled Flight match uses three direct dimensions: country market, content category, and media kind. Other requirements come from Inventory, delivery destinations, Creative metadata, or workspace policy.

## Record the Campaign planning context

1. Open **Monetization**.
2. Select **Campaigns**.
3. Select **Plan campaign**, or open an existing Campaign.
4. Select every country in which the Campaign may run under **Markets**.
5. Enter the intended audience under **Audience**.
6. Select the required audio or video plan.
7. Select the governed content categories for the initial delivery plan.

![The One Podigee campaign proposal shows the governed Markets control and the Audience planning field in the Monetization context.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-68e4a0d9f60b7a798b2bc0b822e78f127c58a00d%2Fdoc-monetization-035-campaign-targeting.jpg?alt=media)

*Use Markets as an eligibility control. Use Audience to record the buyer's planning context, not as a promise of personal audience targeting.*

## Set the exact Flight targeting

1. Open the required Campaign.
2. Find the Flight in the **Flights** section.
3. Select **Adjust flight** if the Flight already exists. Select **Add flight** for a separate delivery plan.
4. Confirm the **Media kind**.
5. Select the target markets.
6. Select the target content categories.
7. Review the Inventory package and delivery destination.
8. Save the proposal as a new Flight version.

Podigee combines the direct conditions. A request must match the Flight media, one selected market, and one selected category. It must also pass the Inventory, schedule, budget, reservation, pacing, publisher, rights, and privacy checks that apply to that request.

Do not add a value only because it seems useful. Use a governed value that matches the approved order and the available supply.

## Apply publisher brand-safety rules

Publisher rules protect the listening and viewing experience across eligible supply.

1. Open **Monetization settings**.
2. Select **Revenue and data rules**.
3. Open the publisher protection rules for the required scope.
4. Select **Revise rules**.
5. Set the advertiser categories that must not run.
6. Add buyer domains that must not run.
7. Set whether sensitive categories require review.
8. Set the maximum number of ads in one break.
9. Select the clean-content fallback.
10. Preview the impact before you request or confirm the change.

![The One Podigee publisher policy shows blocked advertiser categories, a blocked buyer domain, the ad limit, and the clean-content fallback.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-7537f1511a3bc1889a701fd5ec87f8a21d0e9266%2Fdoc-monetization-035-publisher-protections.jpg?alt=media)

*Publisher rules can block unsafe demand even when a Flight otherwise matches the request.*

Use a separate review when your workspace requires it. A solo operator can use an optional review policy if the organization does not require a second person.

## Apply open-market exclusions

Use open-market rules when external or Marketplace demand needs additional restrictions.

1. Open **Monetization settings**.
2. Select **Revenue and data rules**.
3. Add or revise an **Open-market eligibility** rule.
4. Select the categories that external demand must not use.
5. Select the countries that external demand must not use.
6. Add buyer domains that external demand must not use.
7. Confirm the allowed media and placements.
8. Confirm the approved demand source, seller, and publisher authority.
9. Set the safe fallback.
10. Preview the impact before you request or confirm the change.

![The One Podigee open-market rule uses controlled category values for market exclusions.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-4120048dd0f36261483aff4b94eba166deaaf75a%2Fdoc-monetization-035-market-exclusions.jpg?alt=media)

*Use controlled values for exclusions. Do not create different spellings for the same category or country.*

## Limit consent and data use

Privacy and data-use rules do not create new targeting capabilities. They limit which verified signals a decision may use.

1. Open **Monetization settings**.
2. Select **Revenue and data rules**.
3. Add or revise a **Privacy and data use** rule.
4. Select only the consent signals that your integrations can verify.
5. Select the permitted identity evidence.
6. Select the permitted targeting uses.
7. Select the permitted measurement uses.
8. Set the no-consent fallback.
9. Preview the impact before you request or confirm the change.

![The One Podigee privacy rule shows recognized consent signals, permitted identity evidence, and allowed-use controls.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-6c206084d221832b04899de0256b7b7131ff452d%2Fdoc-monetization-035-consent-and-use.jpg?alt=media)

*A stronger identity signal does not permit a use that the policy forbids.*

## Check the supply impact

1. Return to the Campaign.
2. Open the exact Flight version.
3. Select **Calculate forecast** or **Refresh forecast**.
4. Compare the requested quantity with the available quantity.
5. Review the expected range and the reasons for unavailable supply.
6. Remove an unnecessary limit if the order does not require it.
7. Calculate the forecast again after every targeting or policy change.

Use the narrowest rule set that still meets the authorized business requirement. Do not remove a publisher, legal, rights, or privacy protection only to increase supply.

## Resolve a problem safely

| Problem                                                          | Safe action                                                                                                                                                |
| ---------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| The forecast drops after a targeting change                      | Review each new market, category, media, Inventory, and destination limit. Remove only a limit that the order does not require. Then refresh the forecast. |
| A required show or episode is unavailable                        | Update the Inventory package or approve the required episode breaks. Do not try to add a free-text show or episode filter.                                 |
| A required platform is unavailable                               | Select a compatible delivery destination or configure the required integration. Do not use a market or category as a substitute.                           |
| A buyer asks for personal audience or precise-location targeting | Confirm whether an approved connected provider supports it. Do not infer identity, device, or location data.                                               |
| A language is incorrect                                          | Correct the Creative language or content metadata. Do not add a category as a substitute for language.                                                     |
| Safe demand is blocked                                           | Compare the Flight with the publisher and open-market rules. Change the rule only if the authorized policy is wrong.                                       |
| Consent evidence is missing                                      | Use the configured no-consent fallback. Do not treat a missing signal as consent.                                                                          |
| A policy change is waiting for review                            | Complete the configured review, or use an optional-review policy if the workspace permits one-person operation.                                            |
| The Campaign already has a reservation                           | Create and forecast a new Flight version. Review the reservation against that exact version.                                                               |

## Expected result

The Flight has an exact, governed market, content-category, and media match. Inventory, delivery, publisher protection, open-market, rights, and privacy rules limit delivery at their correct boundaries. The current forecast shows the supply that remains eligible after all required limits.

Next, set pacing, priority, frequency, and separation for the Flight.


---

# 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-targeting-exclusions-and-brand-safety.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.