Overcast referrer traffic
Overcast is a popular third-party podcast player for iOS. Show-notes links tapped inside Overcast open in a browser without an HTTP referrer, so podcast traffic from Overcast typically lands as direct. This page explains the mechanics and how UTM tags on show-notes links restore podcast attribution.
Why Overcast links lack a referrer
Overcast is a native iOS podcast app. Listeners read episode notes inside the app and tap links there, and the resulting browser navigation does not come from a web page — so there is usually no HTTP Referer header. The destination records the visit as direct.
This is the same pattern across podcast players: the app, not a web page, is the origin, and most app-to-browser handoffs send no referrer. So Overcast-driven clicks are systematically undercounted unless the links carry their own attribution.
- Show-notes links are tapped inside the Overcast app
- App-to-browser handoffs usually send no Referer header
- Overcast traffic therefore appears as direct by default
Measuring Overcast-driven traffic
Put the attribution in the link. Tag show-notes URLs with utm_source=overcast, utm_medium=podcast, and a utm_campaign identifying the show or episode.
The query string travels through the app handoff into the browser, so analytics records the podcast source even with no referrer. If you want app-level breakdowns, vary utm_source per app (apple_podcasts, overcast, and so on) rather than relying on a referrer that will not arrive.
How it appears in analytics and logs
A visit from an Overcast show-notes tap usually has no referrer, because the link is opened from inside a native app rather than a web page. Without tagging, this traffic is indistinguishable from direct.
Diagnostic use case
Understand why podcast clicks from Overcast appear as direct traffic, and tag show-notes links so the show and episode are measurable.
What WebmasterID can help detect
WebmasterID reads UTM parameters that survive the Overcast app handoff, so podcast traffic is attributed to the right show and episode even though no referrer is sent.
Common mistakes
- Expecting an overcast.fm referrer from in-app taps.
- Treating Overcast-driven direct traffic as unattributable.
- Using one untagged link across episodes, losing per-episode insight.
Privacy and accuracy notes
An app-originated visit with no referrer is normal, not a tracking failure. WebmasterID reads whatever referrer arrives and never re-identifies a visitor when it is absent.
Related pages
- Apple Podcasts referrer traffic
Apple Podcasts is a podcast directory and player app. Links in episode show notes are tapped inside the app, and the resulting web visit usually carries no HTTP referrer — so podcast-driven traffic typically appears as direct. This page explains why and how to tag show-notes links so podcast attribution actually works.
- Pocket Casts referrer traffic
Pocket Casts is a cross-platform podcast player. Show-notes links tapped in the app open in a browser without an HTTP referrer, so Pocket Casts podcast traffic typically appears as direct. This page explains the mechanics and how UTM tags on show-notes links make podcast attribution work.
- Castbox referrer traffic
Castbox is a podcast player with a large mobile user base. Links tapped in Castbox show notes open in a browser without an HTTP referrer, so Castbox podcast traffic typically appears as direct. This page explains the mechanics and how UTM tags on show-notes links restore podcast attribution.
- Campaign links
Tag show-notes links so Overcast podcast traffic is attributed despite the missing referrer.
Sources and verification notes
- Overcast — official siteThird-party iOS podcast app; in-app link taps generally send no referrer.
- MDN — Document.referrerReferrer is often empty for app-originated navigations.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.