Listener brings analytics from connected podcast, video, social, and newsletter accounts into one place. Numbers may differ from a platform report because the source, date window, or calculation is different. This page explains what Listener collects and when it can change.
How Listener collects analytics data
Listener requests data from each connected source and displays the latest data that source makes available. Selecting Refresh starts a new request; it cannot speed up the source’s own processing. Connections and available metrics vary by account.
Three combined numbers need particular care:
- Network Reach adds available views, plays, downloads, impressions, and unique newsletter opens. It is activity across sources, not unique people.
- Audio Reach adds available app plays and host downloads. These can overlap.
- Estimates, including estimated LinkedIn impressions and “Est. first 30 days,” are modeled values, not source-reported counts.
How much historical data Listener requests
These windows describe what a new pull requests. Older data already stored in Listener may still appear. A content limit, such as recent videos, is not a promise that older data is retained. On a phone, swipe the table sideways to see every column.
| Source | Data available | Window requested on refresh |
|---|---|---|
| Spotify | Plays, listening hours, followers, episode performance. | Show and episode totals can span lifetime history. Demographics use the last 30 days. |
| Apple Podcasts | Plays, listeners, engaged listeners, listening time, followers. | Recent daily trends commonly cover about 60 days. Overview totals may span longer. |
| Simplecast | Downloads and episode listener details. | Show downloads start at the earliest date available to the connection. Detailed episode rows cover the newest two pages. |
| Transistor | Daily show and episode downloads. | Show history starts at the earliest available data; episode daily data covers the last 90 days. |
| ART19 | Episode totals and first-24-hour performance. | Up to 150 recent episodes or the past year, whichever limit comes first. |
| Captivate | Downloads, unique listeners, and available breakdowns. | Last 90 days. |
| Omny Studio | Program and clip downloads, reach, and player consumption. | Program total can be lifetime; clip measures cover the last 31 days. |
| Megaphone | Downloads and streams from an imported export. | History depends on the latest export supplied. |
| YouTube | Video views, watch time, engaged views where available, subscribers. | Daily Analytics data covers the last 30 days. Public video totals can be lifetime. |
| Reel views and engagement; account activity where available. | Recent Reel data generally covers the last 30 days and a limited set of recent Reels. | |
| TikTok | Video views and engagement; follower snapshots. | Up to 15 newest videos returned by a refresh. Counts are lifetime totals at the last pull. |
| Reel plays, post engagement, follower snapshots. | Recent content covers about 30 days, with comparison data reaching about 60 days. | |
| X | Public post views and engagement; follower snapshots. | Up to 50 popular or previously tracked posts. This is not a full-account impression export. |
| Post engagement and follower snapshots. | Recent posts use 7- or 30-day publish-date windows, with up to 150 stored posts. Native impressions are not supplied. | |
| Threads | Likes, replies, follower snapshots. | A limited recent set of about 15 posts. View counts are not supplied. |
| Beehiiv | Opens, clicks, deliveries, subscriber data. | Available history depends on the connected publication; there is no single fixed backfill limit. |
| Substack | Recipients, opens, clicks, subscribers. | Up to 100 recent posts and up to one year of subscriber history. |
Connection limit: Listener does not currently have a verified analytics feed for Acast.
How Listener stores data
Listener keeps data from successful pulls so reports can show previously collected results. The history shown depends on the source, connection date, and the windows above. We do not publish a single retention period that applies to every source.
When Listener refreshes data
Refresh timing describes when Listener requests data, not when the provider finishes processing it. Recent YouTube Analytics data, for example, can take 48 to 72 hours to become available from YouTube.
| Source or path | Data refresh |
|---|---|
| Self-serve connections | Select Refresh to request the latest data. A network dashboard view can also trigger a background check once the last successful pull is at least four hours old. Four hours is an eligibility threshold, not a fixed schedule. |
| Spotify and Apple Podcasts | Self-serve connected accounts can sync with Refresh. For other accounts, Refresh sends a request to the Listener team. There is no universal automatic interval. |
| Megaphone | Listener displays the latest imported export. New data appears after a new export is imported; reloading the page does not create one. |
| Scheduled reports | Listener refreshes shows due for a scheduled report before sending it. This does not refresh every connected show. |
Why Listener and a platform report can differ
- Different measures: Spotify plays are not the same as host downloads. Some Listener charts group a piece’s lifetime total by its publish date, while a platform chart counts activity during the selected dates.
- Different coverage: Connections, retrieval windows, content limits, and provider processing can leave a recent date blank or a total lower than the native report.
- Combined or estimated numbers: Network Reach is not deduplicated, and any number labeled “Est.” is a model.
If a gap remains, compare the same source, metric, date range, and time zone. Then send your Listener team the report URL, metric name, native screenshot or export, and last refresh time.