OmnyStudio analytics: a practical guide

OmnyStudio analytics report your downloads, verified plays, and estimated unique listeners across four levels: organization, network, program, and individual clip. The dashboard also breaks each report down by app, operating system, device, and geography, and it uses OmnyStudio's own IAB-aligned listener estimate rather than a single universal download count.

This guide walks through where to find each report, what the numbers actually mean, and how to read them without mixing incompatible metrics together. It also covers where a third-party prefix like Podder fits, since OmnyStudio is one of the hosts that allows one.

How OmnyStudio analytics are organized

OmnyStudio splits reporting into four levels, and each one answers a different question. Per OmnyStudio's documentation, organization analytics cover every episode of every program you manage, network analytics apply the same metrics to the programs assigned to a specific network, program analytics show stats for every clip in one show, and clip-level analytics give you the numbers for a single episode.

Picking the right level matters before you read anything else. A sponsor asking about one show wants program or clip data, not an organization-wide total that blends every podcast you host.

Inside each level, OmnyStudio separates a few distinct measurements that answer different questions:

Treat these as four separate questions, not four versions of the same answer. A download count and a verified play count will never match, because they measure different behavior on different surfaces.

Before you start

You need an OmnyStudio user account with analytics permissions for the organization, network, or program you want to review. If you manage multiple shows under one organization, confirm which level your account can see before you go looking for a report that might sit at the organization level.

You should also decide the question you're answering before opening the dashboard. Are you checking whether a release performed normally, building a sponsor report, or diagnosing a drop in downloads after a feed change? Each of those needs a different level and a different date range.

Step 1: pick the right analytics level

Open the program or clip you want to review, then navigate to its Analytics tab. OmnyStudio labels this consistently: a single episode's report sits under Clip > Analytics, a show's report sits under Program analytics, and an organization-wide view sits at the organization level.

If you're reviewing a single episode's launch, start at the clip level. If you're preparing a monthly summary across a whole show, use program analytics instead. Don't pull an organization total into a single-show conversation. It will include every other podcast you run.

Step 2: set your date range and check the timezone

OmnyStudio reports display in the timezone of the browser you're viewing them in, based on your local settings. If two people on your team pull the same report from different timezones, or across a daylight saving change, the numbers for edge days can shift slightly. Note the timezone and the exact range you used before sharing a number externally.

Set a fixed date range you can repeat: a calendar month, a rolling 30 days, or a fixed age window measured from each episode's release date. Consistency matters more than which window you pick, because it's what lets you compare one release to the next.

Step 3: read the Download Analytics report

The Download Analytics report is the main download view at every level. It shows total downloads for the selected period, a ranked list of top-performing episodes (available at the program and organization level, not at the clip level), and a consumption pattern breakdown covering playback destination, app or directory, operating system, device, device type, and geography.

Use the app and device breakdown to spot where your audience actually listens. If a large share of downloads comes through one directory or one device category, that's useful context for a media kit or a sponsor conversation, separate from the raw download total.

Step 4: check estimated unique listeners for a shorter window

OmnyStudio's estimated unique listeners metric defines a listener as a combination of IP address and user agent, an approach it describes as an IAB metric with an estimation algorithm accuracy of 99 percent. That accuracy figure is OmnyStudio's own claim about its methodology, not an independently audited result, so treat it as a description of the method rather than a guarantee.

This metric is only available for date ranges of 31 days or less. If you try to pull it over a longer window, OmnyStudio won't calculate it, because IP addresses churn too much for the estimate to hold up over time. Keep your unique listener comparisons inside that 31-day ceiling.

Step 5: check verified plays if you use OmnyStudio's players

If you embed OmnyStudio's clip player, playlist player, or use the Omny.fm web player anywhere (on your site, in a newsletter, or on social), you also get a verified plays metric. OmnyStudio defines a verified play as a tracked listening session with at least 60 seconds of playback, and it explicitly does not come from third-party apps such as Apple Podcasts or Spotify.

That distinction matters for anyone reporting embedded plays alongside feed downloads. A verified play tells you about engagement inside OmnyStudio's own player. It says nothing about someone who downloaded the episode through Apple Podcasts and never opened an Omny embed. Keep the two in separate columns, the same way you'd separate consumption rate or completion rate figures that come from different platforms.

Step 6: add a tracking prefix if you want cross-platform reporting

OmnyStudio's own reports only see activity it can observe directly. If you want a consistent view across every app your show reaches, not just what routes through OmnyStudio's players, you need a download URL prefix.

OmnyStudio has a built-in field for this. At the organization level, go to Organization settings > Content and set the Download URL prefix field, with an option to enforce it across every program in the organization. At the program level, go to Program settings > Content and set the Prefix URL field for that show specifically. OmnyStudio's own documentation covers the exact steps and multi-prefix formatting.

OmnyStudio is on Podder's list of supported hosting prefixes, so Podder's prefix analytics work on an OmnyStudio-hosted feed. If you want the install steps specific to this host, see the OmnyStudio prefix install guide.

Step 7: export before you need the history

Each analytics section in OmnyStudio includes an export to CSV option, and you can set the date range to "Lifetime" to pull the full history in one file. OmnyStudio recommends doing this before a migration, since host-side historical data doesn't automatically carry over if you move platforms later.

Build a habit of exporting monthly or quarterly rather than waiting until you need an old number. A CSV sitting in your own storage is the only copy you fully control.

Verify it worked

You'll know your OmnyStudio analytics setup is working when you can answer three things without guessing: which level (organization, network, program, or clip) a number came from, whether it's a raw download, an estimated unique listener count, or a verified play, and what date range and timezone produced it.

Pull the same report twice, a week apart, using the same level and range. If the total moves in a way you can't explain from the report's own breakdown (a new prefix, a big share, a feed change), that's your cue to dig into the consumption pattern data before drawing a conclusion.

Where Podder fits

If your show is hosted on OmnyStudio, Podder's prefix can sit alongside OmnyStudio's own reporting to give you a consistent download view across the apps and directories your audience actually uses, not just the sessions that happen to route through an embedded OmnyStudio player. It doesn't replace OmnyStudio's own dashboard or the platform-specific numbers you get from Apple Podcasts or Spotify. It gives you one more source, clearly labeled, for the cross-platform question those other reports can't answer on their own.

Keep each source tied to the question it actually answers. That's what makes an OmnyStudio report, a verified play count, and a prefix number useful together instead of confusing side by side.

Start with Podder Analytics.