How to find your podcast listener demographics

Your podcast listener demographics live in at least three different dashboards, and none of them shows you the whole audience. Your hosting platform sees downloads by location and device. Spotify for Creators sees age and gender, but only for the slice of your audience that listens on Spotify. Apple Podcasts Connect sees country and app version, never age or gender. If you want a real picture of who listens to your show, you pull from all three, then fill what's left with your own survey.

This is different from the national benchmark question. Podcast audience demographics at the population level tell you what podcast listeners look like in general. This guide is about your show specifically: the location, device, and (where available) age and gender of the people who actually hit play on your episodes.

Why your podcast listener demographics never match across platforms

Every platform measures a different slice of your audience using a different method. Your host counts RSS download requests, which happen whenever any app pulls an episode file, whether or not a human ever presses play. Spotify counts activity inside Spotify only, tied to logged-in accounts, which is why it can report age and gender when your host cannot. Apple Podcasts Connect counts plays and downloads inside Apple's own ecosystem, tracked through device and account signals Apple doesn't share past country and device type.

None of these are lying to you. They're each reporting on a different subset of listeners, measured a different way. A show that's 40% Spotify listeners will get a demographic breakdown that leans toward whatever Spotify's logged-in user base skews toward for that show, not your full audience. Treat every number as "this is what we know about the people on this platform," not "this is who listens to my show."

What to check before you start

Before pulling numbers, make sure you have:

• Admin access to your hosting dashboard (Buzzsprout, Transistor, Simplecast, Captivate, Podbean, or whichever platform serves your RSS feed)
• Apple Podcasts Connect access, claimed and verified for your show
• A Spotify for Podcasters (Spotify for Creators) account linked to your feed
• At least 90 days of published episodes, so the sample isn't a handful of downloads
• An email list or a way to reach listeners directly, for the survey step

If any of these are missing, note it now. A show with no email list and no Spotify traction is going to hit a real ceiling on what it can know about its audience without building a survey channel from scratch first.

Step 1: Pull location and device data from your hosting dashboard

Start with your host. Every major host reports downloads by country, and most break it down further by city or region, plus device type (iOS, Android, desktop, smart speaker) and the app used to request the episode. This data comes straight from RSS request logs, so it's the most complete single source you have, even though it can't tell you anything about who the person actually is.

If you're not sure where this lives in your dashboard or what your host reports versus what it doesn't, how to track podcast analytics walks through where each metric actually comes from and what counts as a download versus a stream.

Some hosting and analytics tools also read prefix-level data across your whole download history, not just what your host chooses to surface. Podder is one of the tools built to do this, showing geography and device trends alongside download totals rather than as a separate export.

Write down: top 5 countries, top 3 device types, and the split between the two or three biggest listening apps. That's your baseline.

Step 2: Check Apple Podcasts Connect for country and device detail

Apple Podcasts Connect gives you a second, independent read on geography and device, drawn from Apple's own ecosystem instead of RSS logs. It won't give you age or gender under any circumstances. What it adds is a cross-check: if your host says 60% US listeners and Apple Podcasts Connect says something close to that for its slice of your audience, you can trust the number more. If the two disagree sharply, it usually means your Apple-listening audience skews differently from your audience as a whole, which is itself useful information.

Connect also shows plays versus downloads, and a rough sense of how far into an episode Apple listeners get, which your host may not expose at all depending on the platform.

Step 3: Pull age and gender from Spotify for Creators, if you qualify

Spotify for Creators (formerly Spotify for Podcasters) is the only major platform that reports age and gender for your specific show, broken into age bands and a gender split, plus top listener cities. The catch: this only shows up once your show clears a minimum number of Spotify streams. Below that threshold, Spotify shows nothing or shows the data grayed out.

If you're above the threshold, this is your single best source for age and gender, and it's worth checking monthly since the breakdown shifts as your Spotify audience grows. If you're below it, don't guess at age and gender. Leave that field blank in your profile until you have real data, or go straight to a survey.

Step 4: Reconcile the numbers instead of picking one

You'll now have two or three sets of location and device numbers that don't quite match, plus maybe an age and gender breakdown from Spotify alone. Don't average them or discard the outlier. Instead, label each number with its source and date, and present ranges where the platforms disagree.

For audience measurement tools that aggregate across platforms, the reconciliation problem doesn't go away, it's built into how the tool weights each source. Understanding what each platform actually measures makes you a better reader of any aggregated report, whether it comes from your host, a third-party tool, or your own spreadsheet.

A practical format: "68-74% US listeners depending on source (host: 74%, Apple: 68%), most common device iOS, Spotify audience skews 25-34." That's honest and it's still usable by a sponsor.

Step 5: Fill the gaps with a listener survey

Occupation, income, buying habits, and any demographic your platforms don't expose only come from asking. Keep the survey short, five to eight questions, and run it as a Google Form or Typeform linked in your show notes and read as a 15-second ask in two or three episodes. Offer nothing more elaborate than a thank-you and maybe early access to something you're already planning to release.

Ask for: age range, general location (state or region is usually enough), what they do for work in broad categories, how they found your show, and one open question about what keeps them listening. Skip anything that feels like a data grab. A survey that takes under two minutes gets more honest, higher-volume responses than one that takes ten.

Report the response count next to every survey-derived stat. A 35-response survey on a show with 8,000 monthly downloads is still useful, as long as you say so.

Step 6: Build a signup form for ongoing first-party data

A survey gives you a snapshot. A signup form, tied to a newsletter, bonus content, or early episode access, gives you an ongoing pipeline of self-reported data tied to real email addresses. Ask for the same core fields as your survey at signup, and you'll have fresh demographic data accumulating automatically instead of needing a new survey push every few months.

This is also the data set a sponsor tends to trust most, since it's tied to an identifiable, growing list rather than a one-time poll.

Step 7: Turn it into something a sponsor or a content decision can use

Once you have location, device, platform split, and whatever age, gender, and occupation data you've gathered, put it on one page. Lead with what you're most confident in (usually geography and device), then the platform breakdown, then the survey-derived detail with its sample size attached.

This is the document you bring to a sponsorship conversation instead of a link to your download chart. If you haven't put a sponsorship pitch together yet, the sponsorship guide covers what sponsors actually ask for beyond raw audience size, and where demographic detail fits into that pitch.

The same page is also a content tool. If your survey shows a third of your audience works in a specific field, or your Spotify breakdown skews ten years older than you assumed, that changes what topics and guests are worth booking. For a wider view of how these numbers compare to the industry, podcast audience statistics is a useful cross-check once your own profile is built.

How you know it worked

You've got a usable listener demographic profile when you can answer, with a source and a date, at least four of these: top countries, top devices, listening app split, age range, gender split, and one non-platform detail like occupation or how listeners found the show. If you're missing age and gender because your Spotify numbers haven't cleared the reporting threshold, that's fine, note it as a gap and lean on your survey instead of leaving it blank with no explanation.

Update the page every quarter. Platform breakdowns shift as your show grows, and a demographic profile from a year ago is a worse pitch than an honest "here's what we know as of this month."

If you want your download and prefix-level data feeding into this process automatically instead of pulling it by hand from three dashboards, Podder's Analytics plan tracks geography, device, and app splits from your feed alongside the download numbers, so the baseline in Step 1 stays current without a manual export every time you need it.