> 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/connect-a-vast-demand-source.md).

# Connect a VAST demand source

Connect, test, and activate a Video Ad Serving Template demand source for audio and video delivery.

Podigee Audio Video Ad Server can connect to an approved Video Ad Serving Template (VAST) demand source. After the first mention, this article uses Podigee Ad Server for the product name. A VAST source can provide an audio or video ad, tracking instructions, or a no-fill result. It does not replace your Campaigns, Creatives, Inventory, demand policy, or measurement rules.

The connection becomes available for a Flight only after the required checks pass. A saved endpoint is not an active demand source.

## Before you start

* You have permission to configure and activate external demand integrations in the workspace.
* You have the provider endpoint and the current provider contract.
* You have an approved credential reference. Do not paste a secret into a form or an article.
* You know the markets, media types, request volume, response time, and commercial rules for the connection.
* You have an owner for media, tracking, privacy, billing, and fallback decisions.

The provider must support the delivery surfaces and media types that you plan to use. Confirm this before you configure the connection.

## Open the connector form

1. Open **Monetization > Integrations**.
2. Choose **Certify an integration**.
3. Choose **Configure a connector**.
4. Select the workspace where the provider will run.
5. Choose **Ad demand** for the connection purpose.

![The One Podigee Add flight form shows the delivery destination and the choice between Podigee delivery and a connected demand provider.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-5fc4e4d261a5d8c83f52f4569ec7dfeb55c32a06%2Fdoc-monetization-034-add-flight.jpg?alt=media)

*Choose a connected provider only when its connection has passed the required checks.*

## Enter the connection details

Complete the form with controlled values where they are available. Do not create provider names, protocols, or operations by typing values that are not in the list.

1. Select **IAB VAST 4.3** under **Standards and platform contracts**.
2. Enter the secure HTTPS provider endpoint.
3. Select the data flow that the provider uses.
4. Select **DSP and exchange demand** as the delivery capability.
5. Select **Audio**, **Video**, or both.
6. Select the allowed markets.
7. Enter the managed request limit and response timeout for the provider contract.
8. Select how provider records match Podigee records.
9. Select the stored credential reference.
10. Confirm the operator responsibility and authorization statements.
11. Apply the connector configuration.

The form displays the values that the workspace can use. Some limits are managed by the workspace or by the provider profile. Do not assume that a value from an older connector still applies to a new version.

## What Podigee checks

The supported profile is VAST 4.3 plus the final 2024 CTV Addendum. The conformance check covers the parts of VAST that can affect safe delivery:

* inline responses and wrapper responses;
* audio, video, media, and mezzanine files;
* universal ad identifiers;
* advertiser and content categories;
* tracking events and error events;
* companion assets and verification references;
* pod sequence information; and
* macro and redirect security.

The check also confirms that the endpoint, credential reference, media type, market, capability, commercial rules, privacy rules, and fallback behavior agree with the connector version.

Local conformance uses managed test responses. It does not contact the provider. Provider certification is a separate check that uses the partner endpoint, its contract, and its approved evidence. Keep the connection in testing or quarantine until both checks are current.

## Review demand policy

Connecting a VAST source does not change the demand order. The active policy still decides when the source may compete, what minimum price applies, how long Podigee waits, and what happens after a no-bid or failure.

![Active demand routing rules show the source order, minimum CPM, response limit, and no-fill outcome.](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 order is a policy decision. Connecting a provider does not silently change that order.*

Review **Monetization > Monetization settings > Revenue and data rules** before activation. Check the source order, minimum CPM, response limit, retry behavior, and no-fill outcome.

## Run the test response

1. Open the connector version in **Monetization > Integrations**.
2. Start the local conformance check.
3. Review the XML response and every wrapper in the chain.
4. Confirm that the wrapper chain stays within the managed depth and redirect limits.
5. Confirm that the selected audio or video file has an allowed media type and duration.
6. Confirm that tracking and error events use the approved destinations.
7. Confirm that macros are handled without exposing identity or credentials.
8. Confirm that no-bid, timeout, invalid media, and failed tracking cases use the configured fallback.
9. Review the billing and privacy result.
10. Save the conformance evidence.

The managed execution profile limits response size, response headers, wrapper depth, redirects, concurrency, timeouts, and repeated failures. These limits protect delivery and do not replace provider testing. A source that exceeds a limit is rejected for that request and can be isolated until the provider is repaired.

## Certify and activate the source

1. Add the provider certification evidence to the connector version.
2. Confirm the exact provider version, endpoint, credential reference, and media capabilities.
3. Confirm that the certification has not expired.
4. Select the environment where the source may run.
5. Submit the connector for the required review policy.
6. Activate the connector only when the review and certification state are current.
7. Open **Monetization > Campaigns** and choose **Add flight**.
8. Select **Connected demand provider**.
9. Select the certified provider, the VAST protocol, and the certified operation.
10. Save the Flight and continue through the normal proposal, review, approval, and publication flow.

The provider, protocol, and operation lists use active certified capabilities. If a value does not appear, do not enter it by hand. The connection is not ready for that use, or the workspace does not have the required authority.

## Understand request-time behavior

For an eligible RSS audio request, Podigee checks the episode, break, listener context, Flight, market, policy, and VAST connection. It validates the provider response before it selects the ad. It then returns the selected audio presentation, the next eligible source, or the configured clean or house fallback.

For an eligible HLS video request, Podigee checks the video presentation, break duration, player capability, Flight, policy, and VAST connection. It validates the bid, media, tracking, and commercial result before it places the ad in the HLS presentation.

A provider request is not a delivery. A bid is not a delivery. A delivery becomes billable only when the decision and measurement contract qualify it.

## If the source fails

* **No connection appears:** confirm that the connector is active and has current certification.
* **The provider is not selectable in Add flight:** confirm its media, destination, protocol, and operation capabilities.
* **The response times out:** review the managed timeout and provider latency evidence. The request continues to the next eligible source or fallback.
* **The response is invalid:** review the exact XML, wrapper, media, tracker, or macro reason. Keep the original payload and connector version unchanged.
* **The source is quarantined:** repair the provider version, run conformance again, and submit new evidence. Do not reactivate an older version without checking its certification period.
* **There is no qualified demand:** use the configured next source, house Flight, or clean content. Do not create paid evidence for a failed or unqualified response.

Use **Monetization > Operations** for the interoperability diagnostic. It preserves the original payload and reports the exact failure category so that the provider can correct the right part of the response.

## Expected result

The VAST source is active only for the certified version, markets, media types, and delivery surfaces that passed the checks. An eligible listener or player receives a validated ad or the declared fallback. Campaign, decision, delivery, measurement, and revenue evidence refer to the same request and connector version.


---

# 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/connect-a-vast-demand-source.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.