> 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/choose-a-spotify-direct-sales-delivery-mode.md).

# Choose a Spotify Direct Sales delivery mode

Choose between a fixed impression goal and priority delivery when you prepare a Podigee Campaign for Spotify Direct Sales.

The Podigee Audio Video Ad Server can prepare a booked Campaign for Spotify Direct Sales. You keep the commercial Campaign, flights, Creatives, forecast, and revenue plan in Podigee. Podigee sends the required campaign and media setup to Spotify.

Spotify controls final playback, ad insertion, delivery counts, and destination reporting. A Spotify result is not proof that Podigee delivered the same ad through RSS or Podigee HLS.

## Before you start

Confirm these requirements:

* The Campaign is booked.
* The Campaign has at least one flight.
* Every flight uses inventory from the Spotify-connected podcast.
* Each flight has an eligible audio or video Creative with a ready Spotify-compatible rendition.
* The podcast has an active Spotify connection.
* The connected Spotify account grants Direct Sales access.
* The Campaign starts late enough to meet Spotify's submission lead times.

Spotify requires orders to start at least 15 minutes after submission. An advertisement must start at least 60 minutes after submission. Use more time when Spotify still needs to process a new media asset.

## Open the Spotify Direct Sales setup

Open **Monetization > Campaigns**, then open the booked Campaign. Find the **Spotify Direct Sales** section and select **Prepare for Spotify**.

![The current One Podigee Campaign page shows a booked audio Campaign, its delivery and revenue summary, and the Spotify Direct Sales action in a ready state.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-2567d92df7063b2de47787f0effec0874f1189e0%2Fdoc-monetization-059-spotify-card.png?alt=media)

*Prepare the exact booked Campaign version that you want Spotify to run.*

Podigee opens a guided setup. Select the Spotify show and the advertiser categories that the connected account provides. Confirm the delivery mode and each flight separately. Podigee does not guess a Spotify ad position or convert a non-CPM commercial model into a Spotify CPM.

## Compare the two delivery modes

Podigee uses customer-facing names for the two Spotify campaign types.

| Podigee delivery mode             | Spotify campaign type |          Impression limit | Use it when                                                                          |
| --------------------------------- | --------------------- | ------------------------: | ------------------------------------------------------------------------------------ |
| Fixed impression goal             | Standard              | Required for every flight | The agreement has a defined delivery quantity.                                       |
| Priority delivery without a limit | Priority              |               Not allowed | The ad must receive priority for the active schedule without a fixed impression cap. |

The priority mode does not guarantee an unlimited number of impressions. The schedule, eligible audience, available ad opportunities, Creative state, and Spotify delivery rules still apply.

## Use a fixed impression goal

Select **Fixed impression goal** when each flight has a defined maximum number of Spotify impressions. This is the normal choice for a sold campaign with a fixed delivery commitment.

For every flight, confirm:

1. The ad position.
2. The Spotify CPM.
3. The Spotify impression limit.

![The current One Podigee Spotify setup shows a fixed impression goal with an ad position, Spotify CPM, and impression limit for the selected flight.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-35081efb7aa287a9072d7a53f24df0bcf66e2f0d%2Fdoc-monetization-059-spotify-standard.png?alt=media)

*A fixed impression goal requires a positive impression limit for every flight.*

The Spotify impression limit is the maximum that Spotify may deliver for that flight. It does not replace the Podigee commercial goal or forecast. Podigee keeps the original Campaign terms and records the Spotify-specific limit as destination setup.

## Use priority delivery without a limit

Select **Priority delivery without a limit** when the Campaign must receive priority during its schedule and the agreement does not use a fixed Spotify impression cap.

For every flight, confirm the ad position and Spotify CPM. Podigee removes the impression limit field because Spotify rejects a Priority order that contains one.

![The current One Podigee Spotify setup shows Priority delivery without a limit and omits the impression limit field from the flight.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-cbdd21162fcc37b92a0ccf4eac59dba854d86447%2Fdoc-monetization-059-spotify-priority.png?alt=media)

*Priority delivery requires no impression limit. Stop the Spotify Campaign when it must no longer run.*

Use a fixed impression goal if the advertiser bought a defined quantity. Do not use Priority only to avoid entering the agreed limit.

## Choose the ad position

Each Spotify advertisement uses one position:

* **Before the episode** for preroll.
* **During the episode** for midroll.
* **After the episode** for postroll.

An episode needs a suitable cue point before Spotify can deliver a midroll. The selected Creative must match the flight media type. Podigee accepts Spotify-supported audio and video renditions and blocks a Creative whose file format or readiness state is not valid for the destination.

## Understand what Podigee creates on Spotify

Podigee converts the governed Campaign into Spotify's required commercial hierarchy:

1. An Agency represents the seller or company that manages the buy.
2. An Advertiser represents the paying brand and its Spotify categories.
3. A Campaign groups the Spotify orders.
4. An Order carries the schedule, targeting, CPM, pacing, frequency rules, and delivery mode.
5. An Advertisement connects one Creative asset to one ad position.
6. An Asset contains the audio, video, or approved companion media that Spotify processes.

Podigee creates or reuses these records in dependency order. A ready Podigee Creative can still need Spotify processing before its Asset becomes ready. Podigee does not activate an Advertisement before the required Asset is ready.

## Submit the setup

Select **Prepare on Spotify** after every required value is complete. Podigee freezes the exact Campaign version and the Spotify-specific choices into one submission snapshot.

The setup can move through these operator states:

* **Ready** means that the Campaign can be prepared.
* **Preparing** means that Podigee is creating or updating the Spotify records.
* **Active** means that Spotify accepted the active orders for the exact Campaign version.
* **Needs attention** means that the provider response or saved state requires review.
* **Stopping** means that Podigee is turning off the active Spotify orders.
* **Stopped** means that the recorded Spotify orders are off.

An Active state reports Spotify's accepted provider state. It does not claim that Podigee controls Spotify playback or final delivery counts.

## Retry a setup that needs attention

Open the Campaign and select **Review and try again**. Podigee restores the last submitted show, delivery mode, advertiser categories, positions, CPM values, and impression limits. Review the provider message, correct the required value, and submit again.

Podigee uses stable operation identities when it retries. A retry must continue the same intended provider operation. It must not create an unrelated duplicate campaign, order, advertisement, or asset.

If Spotify returns an outcome that Podigee cannot reconcile safely, the setup remains in **Needs attention**. An operator must not treat an uncertain provider result as active or submit a second independent setup to work around it.

## Stop Spotify delivery

Open an Active Spotify Direct Sales section and select **Stop Spotify delivery**. Review the confirmation, then select **Stop delivery**.

![The current One Podigee confirmation dialog explains that stopping Spotify delivery turns off every Spotify order but leaves the Podigee Campaign and Podigee delivery unchanged.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-63a57754890c72cb534b8068c077095343f36748%2Fdoc-monetization-059-spotify-stop.png?alt=media)

*Stopping this destination does not stop the Podigee Campaign on other delivery surfaces.*

Podigee turns off every Spotify order created from the submitted Campaign snapshot. It keeps the Podigee Campaign, flights, Creatives, and Podigee delivery unchanged. The recorded stop must finish before you prepare another Spotify setup for the same Campaign.

## Understand capability grants

The visible Spotify options depend on the connected account and the current provider contract. Podigee does not expose or call a Spotify capability only because the provider documentation mentions it.

* Direct Sales needs an enabled Spotify account and the documented campaign, order, advertisement, asset, category, and targeting capabilities.
* Audience targeting needs a separate account capability grant.
* Sponsorships and embedded sponsorships need their own account grants and use a separate workflow.
* A missing or unknown capability stays blocked until Spotify enables and confirms it.

Provider credentials and production certification are required before a local or test connection can become a production Spotify connection.

## Expected result

The Campaign page shows the correct Spotify state and delivery mode. Podigee keeps the exact booked Campaign version and destination choices, prepares the required Spotify records in order, waits for Creative assets to become ready, and records every provider outcome. Spotify remains responsible for final insertion, playback, delivery counts, and destination reporting.


---

# 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/choose-a-spotify-direct-sales-delivery-mode.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.