Troubleshooting: preserve the observation
Record the show, date range, source and size of the change before modifying anything. Compare the same reporting window with the preceding period. A partial day or a different timezone can create an apparent anomaly. Keep the original report so later explanations can be checked against the actual observation rather than a memory of a chart that has already updated.
Look across episodes
Inspect whether the increase is concentrated in one release or spread across the catalogue. A broad pattern may be consistent with new subscriptions and automatic downloads, but it is not proof of that cause. A single promoted episode raises different questions. Use the available export or episode-level report to narrow the investigation without turning a plausible explanation into a confirmed audience-growth claim.
Check known changes
Note recent releases, publicity, migrations, distribution changes and reporting adjustments. Ask the team about events that coincide with the dates. Avoid making a technical change just to see whether the chart returns to normal; that can obscure the original cause. If the data remains unexplained, provide the host with the specific show and period rather than asking a general question about whether analytics are broken.
Choose a proportionate response
If the increase is valid delivery, check capacity and continue observing. If a measurement explanation is confirmed, annotate the report. If the cause stays unknown, retain that label and avoid using the spike as evidence of sustained growth or sponsor value. One unusual period need not trigger a host migration. A useful investigation ends with a documented explanation or a precise unresolved question, not a confident story assembled from a single screenshot. Note whether the apparent increase disappears when comparing complete calendar days. If it does, the next action may be correcting the reporting window rather than investigating a platform failure.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- Investigating a download spike — Merchant documentation · support.transistor.fm · Merchant-controlled · checked 2026-09-19
- What a host download measures — Merchant documentation · support.transistor.fm · Merchant-controlled · checked 2026-09-19