How to Set Up a Podcast Measurement Plan: UTMs, Events and Dashboards

Why "download counts" are not a measurement plan

A download is recorded the moment an app requests your audio file. It does not confirm a human pressed play, let alone listened past the first minute. For most podcasters, raw download numbers are the only metric they track, and they wonder why their podcast feels invisible inside the wider marketing stack.

A proper podcast measurement plan replaces that single number with a connected chain of signals: who discovered the episode, how they engaged, what they did afterward, and whether any of it moved a business needle. The seven steps below build that chain, layer by layer.

Step 1: Dedicated episode pages, your measurement foundation

If you send listeners straight to Spotify, you lose almost all behavioural data the moment they leave your site. The fix is straightforward: publish a dedicated page for every episode on your own domain, with an embedded player, show notes, and a transcript excerpt. Your web analytics then capture page views, traffic sources, scroll depth, and session duration, data that simply vanishes when the listener lands in an external app.

Springcast's analytics suite connects episode-page behaviour directly to your hosting stats, so you see both the web visit and the listen in one place. Add your Google Analytics 4 property or Tag Manager ID in your Springcast site settings and the instrumentation is live in minutes.

Step 2: Custom event tracking for platform-click buttons

Your episode page typically has "Listen on Spotify", "Listen on Apple Podcasts" and similar buttons. Each click is a micro-conversion worth measuring. Without event tracking you know the page was visited; with it you know which platform your audience prefers, and that shapes everything from your distribution strategy to your CTA copy.

In Google Tag Manager, create a Click trigger for each outbound-link button (match on the element ID or a URL fragment like spotify.com). Fire a GA4 event named platform_click with a parameter for the platform name. If you use a privacy-first tool like Plausible Analytics instead, outbound link tracking is enabled by default or configurable as a custom goal.

Step 3: Use your embedded player for consistent attribution

A host-provided embedded player does more than play audio. When the player sits on your page, listen events, play, pause, seek, percentage-complete, flow back into your hosting analytics. You can see that a visitor arrived via a LinkedIn post, loaded the episode page, and listened to 82% of the episode, all in a single session view.

Generic WordPress audio plugins or third-party widgets usually cannot surface those interaction events; they fire a download request and nothing more. Springcast's embedded player is built with privacy-first architecture, no third-party cookies, no consent-wall required, which also means it works cleanly for European audiences under GDPR.

The embedded player transforms your podcast from a black-box download count into a rich stream of interaction data.

Implementation is one line: copy the <iframe> embed code from your Springcast dashboard and paste it into your episode page template. Every interaction is then logged and surfaced in your analytics without any additional configuration.

Step 4: UTM tagging, close the loop from newsletter to listen

Email is typically a podcast's single most effective distribution channel. But unless you tag your episode links, Google Analytics cannot tell the traffic apart from direct visits. UTM parameters are the fix.

For every podcast announcement email, append parameters to your episode-page URL:

• utm_source=newsletter
• utm_medium=email
• utm_campaign=podcast_ep42 (use your episode number or slug)

With this in place you can answer "how many people did Episode 42's email drive to the episode page, and how long did they stay?", the kind of number that lands well in a monthly marketing report.

Take it one step further by enabling site tracking inside your CRM (HubSpot, ActiveCampaign, and most others support this natively). Once a known contact clicks your email and visits the episode page, their contact timeline records the visit. You move from aggregate click-through rates to named-contact engagement, genuinely useful for B2B podcasters who want to know which prospects are listening.

Step 5: BI dashboard integration, one place for all KPIs

Logging into separate portals for Spotify, Apple, your host, and your newsletter tool to compile a report is a time tax. The better model is to pull everything into one dashboard, Power BI, Tableau, or Looker Studio, using your podcast host's API.

Springcast's Podcast Analytics API (available on Enterprise plans) provides structured JSON endpoints for downloads per episode, listener geography, platform breakdown, and completion rates. A typical integration looks like this:

Once the data lands in your warehouse or BI tool, join it with your web analytics, newsletter metrics, and, if you run paid promotion, ad spend. Suddenly podcast performance lives alongside every other channel KPI, and the conversation in the quarterly review changes from "people seem to like it" to "Episode 38 drove 14% of this quarter's inbound demo requests."

For a deeper look at what to measure once the dashboard is running, see our post on podcast analytics for business.

Step 6: Understanding platform data, IAB downloads and avoiding overcounting

Not all download numbers are equal, and combining mismatched figures is one of the most common mistakes in podcast measurement.

Your hosting provider should be IAB Podcast Measurement Guidelines compliant, that means they filter out partial requests, bot traffic, and repeated hits from the same IP within a short window before reporting a "download." The number is lower than raw file requests, but it is far more meaningful. Springcast applies machine-learning bot detection on top of IAB filtering, which removes non-human interactions that IAB rules alone would let through.

Platform-specific numbers (Spotify streams, Apple Podcasts plays) use different definitions. Spotify counts a "stream" only if the listener passes the 60-second mark; Apple's data often lags by 24–48 hours. When you see a discrepancy between your host's numbers and Spotify's, it is usually explained by these definitional differences, not a data error.

If most of your audience listens via streaming apps, treat those platform dashboards as directional, useful for demographic colour ("20% of our Spotify audience is 25–34"), and rely on your hosting platform for the primary, comparable download series. For more on moving beyond raw counts, read our guide to metrics beyond downloads. Once your measurement infrastructure is in place, the natural next step is to calculate the ROI of your podcast and present it to stakeholders in financial terms.

Your podcast measurement plan: the full checklist

Frequently asked questions