measuremy.site
measuremy.site / Blog

How to Track Traffic From a Podcast

November 4, 2026 · 4 min read

Close-up of a professional Saramonic headset with dual microphones in a studio setting.
Photo by tirdad eshraq on Pexels

Podcast traffic rarely arrives with a useful referrer. Podcast apps do not always pass a clear referrer, and some open links in an in-app browser. If you want to know which show, episode, or placement sent a visitor, tag the links yourself before they go out.

Start with a clear destination

Send listeners to a page you can measure. It might be a general page such as example.com/podcast or a page per episode. A dedicated page makes it easier to connect a visit to a signup later.

Tag every podcast link you control

Use UTM parameters on any link in your show notes, episode description, podcast website, or guest bio. A tagged link looks like this:

https://example.com/podcast?utm_source=the-show-name&utm_medium=podcast&utm_campaign=episode-42&utm_content=show-notes

The parameters mean:

This works because the visitor's browser carries those query parameters to your site. The podcast app does not need to pass a referrer.

Keep naming consistent

Pick one format and stick to it. Lowercase with hyphens is easier to read in reports. If you call the show the-startup-pod once and startup-pod later, your data splits. The same show should always use the same utm_source, even if you appear on different episodes.

Tag placements separately

The same episode can have several links: show notes, a link inside the player, a newsletter mention, and a social repost. Give each one a different utm_content value. That lets you see whether the show notes link or the spoken mention actually sent people.

If you host the podcast, you control the show notes. Put the tagged link near the top of the episode description rather than at the bottom. Many listeners scan the description while the episode plays, so the link should be visible without expanding text.

Spoken links need a clean path

If you read a link aloud, do not read a long UTM string. Give listeners something like example.com/trial or example.com/podcast. You can have that clean path redirect to the full tagged URL, or you can give the full URL in writing and a short one in audio. The written link can carry the UTM parameters while the spoken link stays memorable.

If you use a redirect, check that the query parameters survive the redirect before the episode goes live. A simple test in a private browser window is enough.

If you are a guest on someone else's show

Send the host or producer the exact tagged link you want used. Ask them to use it in the show notes and description. If they shorten it, ask them to preserve the UTM parameters. Some podcast hosts use their own tracking or link wrappers, so confirm the final link still contains your source and campaign values.

Do not tag internal links

Do not use UTM tags on internal site navigation. Those tags can overwrite the original source and make your reports messy. UTM parameters are for external placements such as podcast show notes, not for links inside your own site.

Measure beyond visits

A visit from a podcast is not the same as a signup. Set up a conversion goal on the page you send listeners to. That could be a trial signup, newsletter join, download, or purchase. If you use measuremy.site, tracked campaign links can credit later traffic and signups back to the podcast campaign.

Then compare each episode by conversion, not just clicks. A show with fewer visits but more signups may be a better fit than a show with lots of clicks and no action.

Review per episode

For each episode or appearance, record:

This gives you a simple report over time. You can also group by utm_source to see which shows are worth appearing on again.

Watch for delayed traffic

Podcast traffic often spikes in the first few days after an episode, but older episodes can keep sending visitors through search or back catalogs. Check weekly for the first month, then monthly after that. Do not judge an episode only by its first 48 hours.

Ask your analytics tool the right questions

If your analytics tool exposes data through MCP, you can ask a coding agent to answer questions like which podcast campaign had the highest signup rate, or what was the best placement for the latest episode. For example, measuremy.site has an MCP server that lets a coding agent read the analytics and build funnels without you exporting spreadsheets.

Then use that answer to choose the next show, change the placement, or rewrite the call to action.

The goal is not just to count podcast clicks, but to learn which shows and placements actually move people to act. Tag consistently, compare signups per episode, and use that evidence when you decide where to spend your next podcast appearance.

See it on your own site

measuremy.site is cookieless analytics your coding agent can read. 30-day free trial, no card. Plans from $9/month.

Start free trial See the live demo

Add measuremy.site analytics to this project: connect the measuremy.site MCP server at https://a.measuremy.site/mcp for all my projects (claude mcp add --scope user; it signs in with OAuth, no key, and one sign-in covers every site), then tell me how to sign in. Details: measuremy.site/llms.txt

Free tools

All free tools

More from the blog