> 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/changelog/monetization/podigee-ad-server.md).

# Podigee Ad Server release notes

Read customer-facing changes to the Podigee Audio Video Ad Server, its delivery surfaces, and its Monetization workflows.

This page lists customer-visible changes to the **Podigee Audio Video Ad Server** in date order. Each entry states the release state, the affected users, the customer benefit, any action required, and the complete task or reference article.

## Before you read an entry

Check these labels:

| Label      | Meaning                                                                                  |
| ---------- | ---------------------------------------------------------------------------------------- |
| Preview    | The capability is available for approved evaluation or a limited grant.                  |
| Available  | The capability is available in the stated product and workspace scope.                   |
| Limited    | The capability has a declared media, surface, provider, market, or environment boundary. |
| Fixed      | A customer-visible problem was corrected.                                                |
| Deprecated | A supported path is being replaced. Follow the linked migration article.                 |
| Removed    | The path is no longer available. Follow the linked replacement or recovery article.      |

Dates use the release date shown by the entry. A documentation update does not mean that a provider-controlled destination or certification boundary changed on the same date.

## August 2026

### Monetization context preview

**State:** Preview

**Who is affected:** Podcast production studios, ad operators, advertising networks, and teams that need one One Podigee workspace for podcast work and monetization work.

**What changed:** The Monetization context brings Campaigns, Inventory, Creatives, Marketplace, delivery, Evidence & Money, Operations, and Integrations into the existing One Podigee shell. The Podcast and Monetization context switch keeps the workspace, permissions, search, help, and account context shared.

**What you can do:** Start with the [Monetization Control Room](https://github.com/podigee/documentation/tree/master/site/documentation/monetization/use-control-room.md), then follow [Launch your first audio and video Campaign](https://github.com/podigee/documentation/tree/master/site/documentation/monetization/launch-your-first-audio-and-video-campaign.md).

**Important boundary:** This preview does not change the Podcast context or existing publishing workflows. Use the [delivery surface and platform compatibility matrix](https://github.com/podigee/documentation/tree/master/site/documentation/monetization/delivery-surface-and-platform-compatibility-matrix.md) before you activate a destination.

### Audio and video Creative preparation

**State:** Preview

**Who is affected:** Creative managers and ad operators who prepare audio or video advertising assets.

**What changed:** Creative preparation now keeps the master, security checks, media profile, renditions, rights, coverage, captions, and delivery formats together. Audio and video can share a Creative family while each version keeps its own exact media and rights evidence.

**What you can do:** [Upload an audio or video master](https://github.com/podigee/documentation/tree/master/site/documentation/monetization/upload-an-audio-or-video-master.md), then read [Audio and video media specifications](https://github.com/podigee/documentation/tree/master/site/documentation/monetization/audio-and-video-media-specifications.md).

**Important boundary:** Uploading a master does not approve a Creative, assign it to a Flight, or change live delivery.

### Dynamic audio and video delivery evidence

**State:** Preview

**Who is affected:** Production operators and integration teams that need to inspect dynamic RSS audio, HLS audio or video, Apple, Spotify, and external demand behavior.

**What changed:** Delivery evidence now keeps the selected Campaign, Creative, episode, break, surface, decision reason, fallback, analytics event, and qualified money state connected to the same delivery path.

**What you can do:** Start with [Verify one real audio or video delivery](https://github.com/podigee/documentation/tree/master/site/documentation/monetization/verify-one-real-audio-or-video-delivery.md), then use [Monitor delivery, pacing, fill, and revenue](https://github.com/podigee/documentation/tree/master/site/documentation/monetization/monitor-delivery-pacing-fill-and-revenue.md).

**Important boundary:** Provider-controlled destinations keep their own execution authority. Read [Capability and service status](https://github.com/podigee/documentation/tree/master/site/documentation/monetization/capability-and-service-status.md) before you interpret a local conformance result as production certification.

## How release notes are maintained

1. Product records the customer-visible change and release state.
2. Documentation links the smallest task and reference articles needed for the change.
3. The entry names the affected surface, media kind, provider, and authority boundary.
4. A fixed or deprecated behavior links to its recovery or migration article.
5. The entry is published only after the product release owner confirms the customer-facing state.

Release notes do not duplicate complete procedures. Keep the task, reference, API, and Help Center articles as the source for detailed steps.


---

# 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/changelog/monetization/podigee-ad-server.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.