Apple Podcasts embed player analytics has a gap
Open a source-aware analysis with this article as the primary source.
Add us to your Preferred Sources.
Apple Podcasts embed player analytics has one important gap: plays from the web player do not appear in Apple Podcasts Connect. Apple has expanded what the player can present, including video episodes and trailers, but measurement still sits with your hosting provider because the player progressively streams the episode from the host.
A quiet Apple Podcasts Connect chart does not mean nobody pressed play on your website.
What changed in the Apple Podcasts embed player
The updated player gives podcasters two embed types, one for a specific episode and one for the whole show. Each comes in compact and large sizes. The large episode version plays video when the episode has a video version, while a show embed can give visitors a play button for the latest episode or trailer.
Apple's embed player documentation also explains the two ways to get the code. You can generate it through Apple Marketing Tools, or open the show or episode page on podcasts.apple.com, use the share control, choose Copy Embed, and paste the HTML into your site or CMS.
Podnews reported the player update on September 4, 2026. That write-up named both the added video and trailer support and the split in analytics.
The Apple Podcasts embed player analytics gap
Connect is already a platform-specific view. If you use it as the only place to check Apple listening, embedded playback becomes invisible there, even on a page that converts well.
The play still creates a request for the episode. Apple says the embeddable player progressively streams the media from your hosting provider, so the request lands with the host rather than with Apple.
In practical terms, the two dashboards answer different questions:
| Reporting view | What the web embed contributes |
|---|---|
| Apple Podcasts Connect | No plays from the Apple Podcasts web embed |
| Hosting provider analytics | The progressive stream can be reported like other show streams |
| Website analytics | Page visits and your own tracked clicks, depending on your setup |
Do not add the Apple and host totals together as if they were two complete, non-overlapping audience counts. They have different scopes. Use Apple podcast analytics explained to identify what Connect measures, then use your host-side view for delivery across the open podcast system.
What your host can see, and what it cannot prove
A host-side stream tells you that the media file was requested through the embedded player. It does not automatically tell you which page persuaded the visitor, why they pressed play, or whether the embed produced a follower later.
A download or stream is delivery evidence, not a complete account of attention. Our guide to what counts as a podcast download explains why a server request and a human listening session are related but different measurements.
You need a small measurement stack rather than one perfect dashboard:
- Host analytics for playback delivery. Compare traffic around the pages where you added the player. If your host exposes user-agent, referral, or source detail, use it cautiously and document exactly what that field means.
- Website analytics for page context. Track visits to the article, show page, or landing page that holds the embed. This tells you whether the page had a fair chance to generate plays.
- Tagged links for the next action. Put a clearly labeled Apple Podcasts link near the player and add campaign parameters where your analytics setup supports them. That gives you a measurable handoff even though the embedded play itself stays out of Connect.
- Fixed windows for comparison. Compare the same number of days before and after installation. Do not compare a seven-day launch period with a quiet full month.
For a broader view of how these sources fit together, see the podcast analytics guide.
Where the updated player is worth using
The embed is strongest on pages where listening is already the natural next step. Put an episode player in an episode article, a guest page, or a campaign landing page. Use the show player on a durable show page where the latest episode or trailer makes sense without further explanation.
Video support makes the large episode player a better fit for pages built around a visual conversation. It does not mean every article needs a large player. On a narrow page or a section where the episode is supporting evidence, the compact version keeps the next action obvious.
Run a simple test before rolling it across your site. Choose a few pages with steady traffic, install the relevant player, note the date, and record host-side delivery for the following period. Keep the player position consistent so the comparison is not muddied by one embed appearing above the article and another at the bottom.
The useful reading of the update
Apple has made the embed more capable as a listening and viewing surface. It has not turned Apple Podcasts Connect into an end-to-end measurement tool for that surface.
That is not a reason to avoid the player. Let the embed reduce the distance between a web visitor and your episode, let the host report the progressive stream, and use page analytics to explain the context around that play. If you are comparing platform reporting with broader delivery data, Podder versus Apple Podcasts Connect sets out the boundary.
Start Podder Analytics to track your show's delivery beyond a single listening app and read website-driven playback in the right context.
See who's actually listening.
Podder gives you audience demographics, per-episode analytics, and chart tracking. The Chartable alternative that goes deeper.
Start free