> 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-and-verify-spotify-delivery.md). # Connect and verify Spotify delivery Connect a show to Spotify, prepare supported direct sales and sponsorships, and keep Spotify's delivery authority clear. Spotify is a managed destination. Podigee prepares show and episode data, campaign instructions, cuepoints, media, and evidence. Spotify hosts the submitted media, selects eligible Spotify demand, inserts ads, streams the result, and controls the final platform outcome. This boundary is important. A successful Podigee request does not prove that Spotify accepted or played the ad. ## Before you start * You have a Spotify Distribution API connection for the workspace. * The show is eligible for the Spotify capability you want to use. * The show and episodes have the required audio or video media. * You have current Spotify authorization and any required enablement. * Your campaign, creative, cuepoints, and policy are ready in the Podigee Ad Server. Open **Monetization > Integrations** to see the connection, show transfer state, Spotify capability state, and delivery authority. A connected show can still require production certification. ![The current One Podigee Integrations page shows the Spotify destination entry point and separate integration, distribution, platform-operation, synchronization, and webhook states.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-fa4d793d9ffed92c3db7bd35c8cabfa50cb80de8%2Fdoc-monetization-059-integration-state-current.png?alt=media) *Read each integration state separately. A connected setup does not prove destination delivery.* The selected show panel separates the connection state from the delivery authority. It also shows which checks are waiting for a Spotify connection and which revenue paths are unavailable. Spotify controls playback and ad insertion for this destination. Podigee prepares and monitors the plan. ![The current One Podigee Spotify destination panel shows connection, delivery authority, revenue readiness, episode state, and supported Spotify revenue paths.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-0447ab65b1f704bb2f99d8d48208b2430681f0ea%2Fdoc-monetization-059-spotify-destination-current.png?alt=media) *A Podigee-ready setup is not the same as a Spotify delivery result.* ![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 destination-specific setup can have its own capability and execution state.* ## Connect the show 1. Open **Monetization > Integrations**. 2. Open the Spotify connection for the selected show. 3. Confirm the Spotify show identifier and the RSS source. 4. Submit the show when the Distribution API connection is ready. 5. Wait for the asynchronous show and episode processing to complete. 6. Review the processing result for every submitted episode. 7. Resolve media or metadata errors before you prepare a paid campaign. Do not replace the RSS identity to repair a Spotify processing error. Keep the source identity stable and retry the declared Spotify operation. ## Understand Spotify Audience Network Spotify Audience Network (SPAN) is controlled by Spotify. Podigee can show the current state in the Spotify connection, but it does not select or insert SPAN ads. The useful SPAN states are: * **Unsubmitted:** the show is not opted in. * **Pending:** the show is waiting for Spotify brand safety review. * **Active:** the show passed the review and is opted in. * **Paused:** the show is temporarily not opted in. * **Rejected:** the show did not pass the review. SPAN targeting categories and enablement depend on the Spotify account. Do not promise a targeting option that the connection does not show as available. ## Prepare direct sales Direct sales let you prepare an advertiser, campaign, order, creative, targeting, schedule, and audio or video goal for Spotify execution. 1. Create or select the Commercial account and brand in Podigee. 2. Create the Campaign and Flight in **Monetization > Campaigns**. 3. Select Spotify as the destination. 4. Select audio, video, or both only when the Spotify account permits the format. 5. Set the impression goal, ad position, CPM, start and end dates, and targeting. 6. Confirm the creative asset and its Spotify media requirements. 7. Review the Spotify execution boundary and submit the campaign. 8. Monitor the asynchronous synchronization result. Spotify supports different campaign priorities and targeting options. Some audience and topic options require Spotify enablement. Podigee must show those options as unavailable until the account is enabled. ## Prepare a sponsorship Spotify provides two sponsorship paths. ### Standard sponsorship A standard sponsorship inserts a separate sponsor media file at an approved cuepoint. Use it for a host-read or sponsor segment that Spotify should deliver as separate media. 1. Open the Spotify sponsorship action for the show. 2. Choose **Standard sponsorship**. 3. Select the sponsor and the bookable cuepoint. 4. Set the start and end dates. 5. Upload or select the sponsor video asset when required. 6. Review the maximum sponsorship and overlap rules. 7. Submit the sponsorship and monitor the Spotify result. Spotify allows up to two sponsorships per episode at one time. A cuepoint cannot have overlapping sponsorships. ### Embedded sponsorship An embedded sponsorship marks content already recorded in the episode. Spotify creates the cuepoint and can stitch the segment out when the sponsorship ends. 1. Choose **Embedded sponsorship**. 2. Select the episode and enter the start and end positions in seconds. 3. Set the sponsorship end date. 4. Confirm the stitch-out effect. 5. Submit the sponsorship and monitor the result. Do not use an embedded sponsorship when you only want a separate ad file. Archiving an embedded sponsorship removes the marked segment from the Spotify presentation. Spotify sponsorship records cannot be deleted, so use an end date or archive them when they must stop. ## Check reports and evidence Podigee records the request, synchronization result, and source identity. Spotify controls the final execution and provides its own delivery or sponsorship report when available. 1. Open **Monetization > Evidence & Money**. 2. Filter by Spotify destination. 3. Compare the Podigee synchronization result with the Spotify source report. 4. Keep Spotify-reported values source-labeled until the report contract and reconciliation are complete. Do not add Spotify-controlled delivery to Podigee totals only because a campaign was accepted by the API. ## If Spotify is blocked or unavailable * **Connection required:** complete the Distribution API connection first. * **Processing:** wait for the asynchronous result before retrying. * **Enablement required:** ask Spotify to enable the capability for the account. * **Certification required:** keep the change inactive until Podigee verifies the full contract. * **Cuepoint unavailable:** choose another bookable cuepoint or change the date range. * **Provider failure:** keep the approved RSS or Podigee delivery path active. ## Expected result The show and its media are synchronized to Spotify through the supported connection. Direct sales and sponsorship instructions are recorded with the correct dates, media, cuepoints, and evidence. Operators can see which results Spotify controls and can keep the RSS or Podigee route available when Spotify is not ready. --- # 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-and-verify-spotify-delivery.md?ask=&goal= ``` `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.