> 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/fix-an-apple-or-spotify-delivery-problem.md).

# Fix an Apple or Spotify delivery problem

Route Apple Podcasts and Spotify delivery problems to the correct Podigee repair, platform operation, or escalation path.

Apple and Spotify are connected destinations with different delivery authority. Use this guide to identify the boundary before you retry an operation. Keep the normal Podigee RSS or HLS route available until the connected destination has confirmed its own processing or playback state.

## Identify the destination and operation

Record the show, episode, Campaign or sponsorship, destination, approximate time, and visible status. Then select the matching route:

| Problem                                    | Start here                                            | Authority                                                        |
| ------------------------------------------ | ----------------------------------------------------- | ---------------------------------------------------------------- |
| Apple HLS playlist, asset, or interstitial | Integrations and Apple validation evidence            | Podigee prepares media; Apple controls association and playback. |
| Apple association or processing            | Apple connector operation and Podcasts Connect result | Apple controls the association result.                           |
| Spotify show or episode transfer           | Spotify connection and processing result              | Spotify controls hosting and processing.                         |
| Spotify direct sales                       | Campaign synchronization and Spotify result           | Podigee prepares the instruction; Spotify executes delivery.     |
| Spotify SPAN                               | Capability state in the Spotify connection            | Spotify controls enablement, auction, and insertion.             |
| Spotify sponsorship                        | Sponsorship record, cuepoint, and Spotify result      | Spotify controls final playback and stitch-out.                  |

Do not report a connected operation as delivered only because Podigee accepted the request.

## Apple: check HLS before association

Open **Monetization > Integrations**, select **Apple Podcasts**, and read the current capability state. Confirm that the Primary Playlist, media playlists, segments, captions, and interstitial assets are reachable and use stable URLs.

![The current One Podigee Apple delivery view shows the video decision, Apple delivery method, interstitial state, and shortened references.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-458300b2d2e224a26cf621b97c6b250f96445b01%2Fdoc-monetization-058-apple-decision.png?alt=media)

*Use the Apple delivery result to connect the HLS presentation to the episode.*

Run the Media Stream Validator and fix every error. Check:

* audio-only, 720p, 1080p, and I-frame variants;
* media and caption playlist references;
* exact MIME types and CORS headers;
* stable segment and interstitial URLs;
* interstitial duration and asset-list response;
* delayed companion-video retrieval.

![The current One Podigee Apple delivery view shows the Apple HLS standards and interstitial checks for the selected presentation.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-34d9daa348dece809f9dccab5999d7ca485d3f70%2Fdoc-monetization-058-apple-standards.png?alt=media)

*A valid local HLS presentation is required before Apple association.*

If the validator fails, correct the exact HLS version and run it again. Do not change the RSS episode identity to repair an HLS problem.

## Apple: fix association or processing

If HLS validation is clean but Apple does not show the video:

1. Confirm the RSS episode GUID and published episode.
2. Confirm the Primary Playlist URL in the Apple operation.
3. Check whether the operation is staged, submitted, processing, associated, or rejected.
4. Read the Apple error or processing result.
5. Retry the same declared operation once when it is retryable.
6. Keep the RSS audio route available while Apple processes the asset.

For an existing episode, use the episode asset operation. For a new episode, keep the staged asset reachable until Apple associates it with the future episode. Apple can fetch video after it has fetched audio, so do not remove a referenced asset after the first successful request.

## Apple: fix a no-ad interstitial

An empty dynamic asset list is a valid no-fill result. It is not an Apple delivery error.

Check the Podigee decision, selected break, Creative coverage, and interstitial asset duration. If the HLS presentation is valid but no ad is eligible, keep the approved clean fallback. If the asset list is malformed or the selected media is incompatible, repair the exact Creative or HLS version and validate again.

## Spotify: check connection and processing

Open **Monetization > Integrations**, select Spotify, and check the show and episode processing state.

![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 Spotify Campaign can be ready in Podigee while Spotify processing is still pending.*

Check:

* Spotify show identifier and source identity;
* submitted episode and media type;
* asynchronous processing state;
* rejected metadata or media details;
* capability enablement for the selected format;
* synchronization receipt and last attempt.

If processing is pending, wait for the result. If it failed, correct the named media or metadata and submit the declared operation again. Do not create a duplicate show or episode to bypass a processing error.

## Spotify: fix direct sales

For a direct-sales Campaign, compare the Podigee Campaign with the synchronized Spotify configuration:

* audio or video format;
* impression goal;
* ad position;
* CPM and currency;
* start and end dates;
* targeting and enabled categories;
* creative media and processing result;
* Spotify priority or standard execution mode.

If Spotify reports that a capability is not enabled, keep that option unavailable in the Campaign. Ask Spotify to enable it or choose a supported destination path.

## Spotify: fix SPAN

SPAN is Spotify-controlled. Podigee can show the capability state and submit supported configuration, but it cannot select the auction result or force an ad into Spotify playback.

| State       | Operator action                                                           |
| ----------- | ------------------------------------------------------------------------- |
| Unsubmitted | Submit opt-in only when the show is eligible and the business wants it.   |
| Pending     | Wait for Spotify review. Do not promise SPAN delivery yet.                |
| Active      | Monitor Spotify-reported results and keep the provider boundary visible.  |
| Paused      | Confirm the business reason, then resume through the supported operation. |
| Rejected    | Read the Spotify reason and correct or escalate it.                       |

Do not add a Spotify-controlled SPAN result to Podigee qualified revenue without the required Spotify report and reconciliation evidence.

## Spotify: fix a sponsorship

First identify whether the sponsorship is **Standard** or **Embedded**.

![The current One Podigee Spotify sponsorship view shows a standard sponsorship with the selected show, cuepoint, dates, and media asset.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-07fa9100b6ed7ff5e4dde0900f4598fb117a79a7%2Fdoc-monetization-060-standard-sponsorship.png?alt=media)

*A standard sponsorship uses a separate sponsor media asset at a bookable cuepoint.*

For a standard sponsorship, check the cuepoint, date range, sponsor media, overlap rule, and Spotify processing state. A cuepoint cannot have overlapping sponsorships.

![The current One Podigee Spotify sponsorship view shows an embedded sponsorship with the episode, start and end positions, and stitch-out behavior.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-8346fc92effe4e9eb3e789d3c230bd323151239a%2Fdoc-monetization-060-embedded-sponsorship.png?alt=media)

*An embedded sponsorship marks content already recorded in the episode.*

For an embedded sponsorship, check the episode positions and end date. Archiving an embedded sponsorship can remove the marked segment from Spotify's presentation. Spotify sponsorship records are not deleted, so use an end date or archive the record as the operation requires.

## Check evidence and keep the fallback

Open **Evidence & Money** and filter by destination. Separate these records:

* Podigee request and synchronization evidence;
* Apple validator and association evidence;
* Spotify processing and provider evidence;
* destination-controlled delivery or sponsorship reports;
* qualified Podigee delivery and revenue.

Keep provider-reported values source-labeled until reconciliation is complete. If a connected destination is unavailable, keep the approved RSS or Podigee HLS path active when the Campaign allows it.

## When to escalate

Escalate to the destination owner when:

* the local presentation passes validation but Apple rejects or fails association;
* Spotify processing remains failed after one correct retry;
* a required Spotify capability is not enabled;
* a sponsorship cuepoint or stitch-out result disagrees with the submitted configuration;
* provider reports and Podigee synchronization evidence disagree.

Include the short show, episode, Campaign, sponsorship, operation, and provider references. Do not include credentials or private listener data.

## Expected result

The operator knows whether the repair belongs in Podigee, Apple, or Spotify. Apple HLS remains replayable and associated with the stable RSS episode, Spotify instructions remain synchronized, provider-controlled execution is not overstated, and a safe Podigee fallback remains available.


---

# 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/fix-an-apple-or-spotify-delivery-problem.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.