WebmasterID logoWebmasterID
UTM tracking

Podcast campaign tracking with UTM

Podcasts are read aloud, so listeners type a URL rather than click — which makes attribution inherently approximate. This page shows how vanity URLs that redirect to a UTM-tagged destination capture what you can, while being honest about the limits.

Verified against primary sources

Vanity URL plus UTM

Because nobody clicks a spoken link, give each show or episode a short, easy-to-say vanity URL that redirects to a fully UTM-tagged destination:

Be honest about the limits

Podcast attribution is approximate by nature. Some listeners type your main domain instead of the vanity URL, some hear it days later, and there is no referrer from an audio player. The vanity-URL number undercounts true podcast impact, so treat it as a measurable floor and say so in reports.

Do not fabricate a 'true' podcast conversion figure to compensate. Report the captured visits as captured visits, and use distinct vanity URLs per show to compare shows on a like-for-like basis.

How it appears in analytics and logs

A visit arriving via your podcast vanity URL, redirected to a utm_source=podcast destination, is attributed to that show. The catch: only listeners who use the vanity URL are captured, so the number is a floor, not a total.

Diagnostic use case

Give each podcast or episode a memorable vanity URL that redirects to a UTM-tagged page, so the typed-in traffic you do capture is attributed.

What WebmasterID can help detect

WebmasterID reads the utm_source=podcast destination at ingest and attributes the visit to the show, so the typed-in podcast traffic you capture appears as a real source rather than direct.

Common mistakes

Privacy and accuracy notes

Keep podcast UTM values to generic show and episode labels. No personal data. The vanity URL and its UTM destination are both public.

Related pages

Sources and verification notes

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.