Build a podcast advertising reporting dashboard that buyers trust

What to take away

Step 1: Agree what the dashboard must prove

Start from the decision it supports. A sponsor renewing a host-read slot needs delivery and cost per acquisition. An in-house team pacing a campaign needs impressions against plan.

Confirm who signs off changes to the metric list. A quiet edit by one team can break another team's month.

Write the metric list down and get it signed off. Use IAB Tech Lab's Podcast Measurement Technical Guidelines as a common reference, and record the counting method used by each source. Define downloads as the sum of platform-reported downloads for the selected episodes and reporting period, using the platform's stated definition; downloads are not listeners or ad impressions.

Step 2: Map every data source to a named owner

List each source: hosting-platform downloads from platforms such as Acast, Captivate, Libsyn or Spotify for Podcasters; ad-server impressions from the ad server used for the campaign, such as Acast or Megaphone; promo codes from the advertiser's commerce system; landing-page analytics; and post-purchase surveys. For each, name the person who exports it and how often.

Record the refresh rate in the dashboard header. A figure refreshed weekly should never sit next to one refreshed hourly without a label.

Prefer scheduled exports to manual downloads. Manual pulls get skipped in busy weeks, and gaps in a series are hard to explain later.

Step 3: Build the metric layer

Create one table per source, then a joined view. Keep raw columns untouched and calculate in a separate layer.

Set the grain explicitly: one row per campaign, episode, source and reporting period in the delivery table, with fields such as campaign_id, episode_id, period_start, period_end, source, downloads, ad_impressions, ad_starts, completed_ad_listens and spend. Keep responses in a separate table with campaign_id, reporting_period, promo_code, redeemed_order_id and attributed_conversion; aggregate each source to matching campaign and reporting-period fields before joining, to avoid duplicated totals.

Build a small dashboard in Google Sheets, or use Looker Studio or Microsoft Power BI for a visual report. Connect only exports your workflow can refresh reliably, and show the last-refresh timestamp.

Label derived columns clearly so a reader can tell measured data from figures you calculated. Define CPM as spend ÷ ad-server impressions × 1,000, completion rate as completed ad listens ÷ ad starts × 100, and CPA as spend ÷ attributed conversions; calculate each only when its inputs cover the same campaign and reporting window. Count promo-code redemptions as distinct redeemed order IDs for the agreed campaign code and reporting period, and document the attribution window for conversions.

For example, a team paying £400 a month for hosting and ad serving might track cost per thousand impressions, completion rate and code redemptions. Those are illustrative figures, not benchmarks.

Step 4: Set the reporting cadence

Match cadence to the buying cycle. Weekly pacing for active campaigns, monthly summaries for retained clients, quarterly reviews for renewals.

Publish the same day each period. Late dashboards get ignored, and ignored dashboards get cancelled.

Send a brief note when each report lands, naming the two or three movements that matter. A dashboard link on its own rarely gets opened.

Step 5: Add the compliance layer

Sponsorship claims need evidence. Rule 3.1 of the CAP Code prohibits materially misleading advertising, and the Advertising Standards Authority (ASA) administers the Code and handles complaints. The CAP rules on misleading advertising apply to podcast spots as they do to other media, so keep substantiation for every performance claim.

The Competition and Markets Authority (CMA) guidance, The CMA's approach to direct consumer protection, covers misleading promotions, which matters when a host reads a discount code.

Where consent and suppression fit

If the dashboard includes listener-level data, document your lawful basis and retention period under the UK GDPR and Data Protection Act 2018. PECR also governs electronic marketing and certain tracking technologies, so a UK GDPR lawful basis alone does not authorise emailing a downloaded list; retain suppression records to prevent re-import. The ICO's enforcement action page shows the penalties that follow marketing breaches, which is useful evidence when a client asks why you will not simply email a downloaded list.

What to do when a source fails

Log the outage, mark affected cells as estimated, and correct them the following period. Never silently overwrite a published number.

Step 6: Test the dashboard before launch

Pick one completed campaign and rebuild it end to end. Check that totals reconcile with the platform invoice, then ask someone outside the project to find a specific figure without help.

Use a campaign with a known problem, such as a tracking outage, so you can see how gaps appear in the finished view.

If they cannot, the labelling is wrong, not the person.

Step 7: Hand over with a method note

Give the client a one-page note: sources, refresh rates, formulas, and who to contact. Revisit it whenever a platform changes its definitions.

To make the figures auditable, retain each dated source export and reconciliation, and make the calculation path available to the buyer. Record whether the metrics follow IAB Tech Lab's Podcast Measurement Technical Guidelines; do not describe the dashboard as independently audited or certified unless that has actually happened.

Set a review date for the definitions, for example each January. Platforms change how they count listens, and stale notes mislead.

Our wider measurement and reporting guide covers how this dashboard sits inside a full reporting cycle.

Common questions

How often should a podcast advertising dashboard refresh?

Daily or weekly for active campaigns, monthly for retained reporting. Publish on a fixed date and label each source's refresh rate so nobody compares mixed windows.

Can I use platform downloads as the only delivery metric?

No. Downloads vary by platform and filtering method, so pair them with ad server impressions or promo code activity before making performance claims to a sponsor.

Who owns the dashboard when an agency runs the campaign?

The buying agency builds and maintains it, but the contract should state that raw exports and the method note transfer to the client on request.

What goes in the method note?

Sources, owners, refresh rates, formula definitions, known limitations and the date of the last reconciliation against platform invoices.