> 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/concepts-and-reference/targeting-and-policy-value-reference.md).

# Targeting and policy value reference

Use the supported targeting and policy values to reach the right supply while keeping delivery, privacy, brand safety, and fallback rules clear.

Use controlled values for targeting and policy. A controlled value has one meaning in planning, decisioning, reporting, and support. Do not create a new spelling for a value that already exists.

This reference explains the value groups that an operator can select, the value groups that a workspace administrator can configure, and the value groups that require a connected provider.

## Value ownership at a glance

| Value group         | Typical values                                                      | Where you select it                          | Delivery effect                                                                     |
| ------------------- | ------------------------------------------------------------------- | -------------------------------------------- | ----------------------------------------------------------------------------------- |
| Market              | ISO country code such as DE, AT, CH, GB, or US                      | Campaign and Flight                          | Direct eligibility match.                                                           |
| Language            | A governed language code such as de, en, fr, or pl                  | Creative and content metadata                | Describes the asset or content. It filters only when the Flight rule uses language. |
| Content category    | A controlled category from the workspace catalog                    | Flight and policy                            | Direct eligibility or exclusion match.                                              |
| Media kind          | Audio or video                                                      | Creative, Flight, Inventory, and destination | Direct format and supply match.                                                     |
| Platform or surface | RSS audio, Podigee HLS, Apple Podcasts, Spotify, or an owned player | Flight and delivery destination              | Limits the delivery surface and its required checks.                                |
| Device or client    | A provider-supported device or client value                         | Connected provider rule, when available      | Applies only when the provider can verify the value.                                |
| Audience            | A buyer brief or a provider-supported audience segment              | Campaign brief or connected provider         | A brief records intent. A segment filters only when it has verified authority.      |
| Consent signal      | A configured consent state or signal name                           | Privacy and data-use policy                  | Limits which signals and uses a decision can use.                                   |

The current first-party match uses market, content category, and media kind as direct dimensions. Inventory, break approval, schedule, rights, destination, Creative, budget, reservation, pacing, frequency, and policy checks also apply. A field that appears in a form is not automatically a live delivery filter.

## Geography and language

### Markets

Select markets from the governed market list. The list uses one country code per market and keeps the same code in Campaigns, Flights, forecasts, decisions, and reports.

![A Creative upload form with German as the language, three rights markets, and a controlled UniversalAdID registry.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-4e1af4b842aa4842c7e164cfa4cb96500540bd7b%2Fdoc-monetization-012-language-and-market-selectors.jpg?alt=media)

*Language, rights markets, and the identifier registry use controlled choices in the Creative form.*

Use a market when the order or publishing rule names a country. Do not use a market to represent a city, a language, an audience, or a listener identity. If the required market is not in the list, ask a workspace administrator to configure it before you plan delivery.

### Languages

Select the language code that describes the Creative or content. Use the language value for translation, review, and reporting. Use it as a delivery condition only when the Flight or policy explicitly supports language matching.

Do not add a language by typing a new spelling. If a required language is not available, request a governed language value and record the reason.

## Content, media, and platform values

### Content categories

Select one or more categories from the workspace catalog. Categories support Flight matching, publisher exclusions, open-market restrictions, and brand-safety review.

Use the category that describes the content or the rule. Do not use a category to represent a brand, a market, a language, or an audience segment. If a category is missing or too broad, ask the workspace administrator to review the catalog instead of adding a free-text value.

### Media kind

Use **Audio**, **Video**, or both when the Campaign can use both formats. The selected media kind must match the Creative rendition, the Inventory package, the break, and the delivery surface.

An audio Creative cannot satisfy a video-only Flight. A video Creative can have an audio track, but it still needs a video-compatible rendition and destination.

### Platform and surface

Select the destination that the order supports. The surface determines the media contract, insertion authority, measurement path, and fallback behavior.

| Surface value   | Use it for                                      | Important boundary                                                       |
| --------------- | ----------------------------------------------- | ------------------------------------------------------------------------ |
| RSS audio       | Traditional podcast downloads and players       | The serving path must return the correct audio representation.           |
| Podigee HLS     | Podigee-controlled audio and video streaming    | The manifest, media segments, interstitials, and events must agree.      |
| Apple Podcasts  | Apple Podcasts video and interstitial delivery  | Apple requirements and host-side HLS rules apply.                        |
| Spotify         | Spotify distribution and monetization paths     | Spotify controls execution for supported program paths.                  |
| Owned player    | A connected first-party player                  | The player and integration must accept the required response and events. |
| External demand | VAST, OpenRTB, CATS, or another approved source | Provider capability, consent, timeout, and fallback rules apply.         |

## Device and audience values

Device, client, and audience values are not general free-text targeting fields. Use them only when an approved connected provider can verify the value and the workspace policy permits the use.

| Requirement                | Correct value source                            | Safe behavior when it is unavailable                               |
| -------------------------- | ----------------------------------------------- | ------------------------------------------------------------------ |
| Device type                | Verified provider signal                        | Do not infer it from a user-agent string in a general Flight rule. |
| Player or client           | Destination integration                         | Use the surface rule or clean fallback.                            |
| Audience segment           | Approved provider segment with declared purpose | Treat the segment as unavailable, not as a match.                  |
| Buyer audience description | Campaign brief                                  | Keep it as planning context, not as a delivery promise.            |
| Precise location           | Approved provider signal and policy             | Do not create a location field in the Campaign.                    |

The decision system must disclose the identity tier and data-use boundary for any provider-backed value. A missing or expired signal cannot become consent or a positive audience match.

## Brand-safety values

Publisher and open-market policies use controlled values to protect supply.

| Policy value                | Examples                                                  | Result                                                 |
| --------------------------- | --------------------------------------------------------- | ------------------------------------------------------ |
| Blocked advertiser category | Alcohol, gambling, politics, or another governed category | The candidate is not eligible in the policy scope.     |
| Blocked buyer domain        | A domain on the workspace block list                      | The buyer is not eligible in the policy scope.         |
| Sensitive-category review   | Review required or not required                           | Controls whether a sensitive category needs review.    |
| Maximum ads per break       | A whole number, such as 2                                 | Limits the number of ads in one break.                 |
| Clean-content fallback      | A safe house or source segment                            | Keeps the break safe when paid demand is not eligible. |
| Disclosure or marking       | Required disclosure or marking profile                    | Controls the required presentation and evidence.       |

![Active publisher protection rules with category exclusions, a two-ad limit, sensitive-category review, and clean-content fallback.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-e607d20c19714ecee1773482a82013e2d7e28543%2Fdoc-monetization-019-publisher-rules-active.png?alt=media)

*Publisher rules protect the listening and viewing experience before an ad can become eligible.*

## Consent and data-use values

Privacy rules limit data use. They do not create a new targeting capability.

| Value group         | What it records                           | If the value is missing                               |
| ------------------- | ----------------------------------------- | ----------------------------------------------------- |
| Consent signal      | The signal that an integration can verify | Apply the configured no-consent rule.                 |
| Identity evidence   | The permitted evidence tier               | Use only the allowed tier. Do not upgrade the signal. |
| Targeting use       | The permitted decision purpose            | Do not use the signal for a different purpose.        |
| Measurement use     | The permitted reporting purpose           | Keep measurement within the approved purpose.         |
| Retention           | The allowed retention period              | Do not retain beyond the policy boundary.             |
| No-consent fallback | The safe outcome without consent          | Use clean or non-personalized delivery as configured. |

Select only signals that the connected destination or provider can verify. A stronger identity signal does not permit a purpose that the policy forbids.

## Pacing, priority, frequency, and separation

These values control how eligible Campaigns compete and how often a listener or viewer sees an ad.

| Value group | Common choices                                                                | Use it to                                                        |
| ----------- | ----------------------------------------------------------------------------- | ---------------------------------------------------------------- |
| Priority    | Sponsorship, direct-sold, private deal, Marketplace, open programmatic, house | Set the order when more than one candidate is eligible.          |
| Pacing      | Even, front-loaded, or a configured delivery profile                          | Spread delivery across the Flight window.                        |
| Frequency   | Per session, day, episode, or a governed identity tier                        | Limit repeated exposure when the identity signal supports it.    |
| Separation  | Brand, category, advertiser, or configured adjacency rule                     | Keep conflicting ads apart in one pod or presentation.           |
| Rotation    | Weighted or ordered Creative rotation                                         | Share delivery between eligible Creative versions.               |
| Pressure    | A disclosed audience or supply pressure rule                                  | Prevent a rule from consuming more eligible supply than allowed. |

Frequency is best effort at the disclosed identity tier. Do not describe it as exact when the surface or provider cannot verify the listener or viewer identity.

## Demand and fallback values

Demand policy defines what happens when several demand sources or a provider response are present.

| Value group          | What it controls                               | Safe rule                                                         |
| -------------------- | ---------------------------------------------- | ----------------------------------------------------------------- |
| Demand order         | Which source gets the first opportunity        | Keep the order explicit and versioned.                            |
| Minimum CPM or floor | The lowest accepted price                      | Do not lower it to hide underdelivery without an approved change. |
| Response timeout     | How long a provider may respond                | Keep source playback within the fallback boundary.                |
| Provider result      | Filled, no-fill, invalid, timed out, or failed | Record the result and continue with the next allowed source.      |
| Partial fill         | Whether a pod can contain fewer ads            | Follow the Flight and publisher policy.                           |
| No-fill fallback     | House, clean, or source content                | Use the declared safe result and do not create false billing.     |

![Active demand routing rules with direct-sold demand first, an 18 EUR minimum CPM, an 800 millisecond response limit, and house fallback.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-3300aa6f6beb817f111c20442043939d962b3178%2Fdoc-monetization-019-demand-rules-active.png?alt=media)

*Demand rules define the selection order, price boundary, response limit, and no-fill outcome.*

## Workspace-configurable values

A workspace administrator can configure governed catalogs and policy defaults. The administrator can add a market, language, category, device value, provider segment, review mode, fallback, or policy choice only when the value has a clear owner, meaning, and reporting behavior.

Before adding a value, record:

1. The business meaning and permitted spelling.
2. The scopes where the value is valid.
3. The source that can verify it.
4. The privacy class and allowed uses.
5. The effect on forecast, decisioning, reporting, and fallback.
6. The owner and review date.

Do not add a value that cannot be used consistently in all required surfaces. Retire a value by keeping its history and blocking new selection. Do not delete a value that is referenced by a published Campaign or report.

## Safe value selection checklist

Before saving a Campaign, Flight, or policy, check the following:

1. Every market, language, category, media, and surface value comes from a controlled list.
2. The value matches the order, Inventory, Creative, and destination requirements.
3. A provider-backed value has a current capability and evidence source.
4. Privacy and data-use rules permit the intended purpose.
5. Pacing, frequency, separation, and fallback values are explicit.
6. The forecast still meets the business requirement.
7. The decision or policy preview shows the expected reason when a candidate is excluded.

## Expected result

Targeting reaches the intended supply without hidden free-text rules. Policy values keep brand safety, privacy, pacing, frequency, separation, demand order, and fallback behavior consistent. The same governed values can be explained in a forecast, a decision, a report, or a support case.

Next, review the metric, billing, and currency definitions before you compare delivery with money.


---

# 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/concepts-and-reference/targeting-and-policy-value-reference.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.