What a radio advertising reporting dashboard means for campaign proof

What to take away

Define the metrics before you build anything

Most dashboard projects fail at the naming stage. One team counts anyone within broadcast range as a listener, while another counts only logged-in stream users. When the two numbers meet in a board pack, nobody can reconcile them.

Write a one-page metric dictionary before touching a connector. Record the source system, refresh frequency, filter and named owner for each metric. The radio advertising measurement and reporting guide 2027 sets out the full field list, the definition wording to use and the survey base behind each audience figure.

Agree who signs off changes to a definition. A metric that quietly changes meaning mid-campaign is worse than a missing metric. Two readers should be able to produce the same figure from the same definition.

Assemble the data sources

A workable dashboard pulls from three layers: delivery data from the station or ad server, audience data from industry research, and response data from your own tracking.

RAJAR publishes listening volumes data covering total hours and average weekly listening per head, the standard reference for audience scale in the UK. Treat it as context, not spot-level attribution.

For digital audio bought programmatically, the IAB UK background on the digital advertising industry body explains whose conventions your platform reporting should follow.

Match dayparts before you merge anything. A station's breakfast show and a streaming platform's morning segment are not the same inventory, and averaging them produces a figure that describes neither.

Build the dashboard in five steps

Step two is the one people skip. Reconciliation against actual affidavits usually surfaces missing spots, duplicated lines or a daypart mapping error.

Run the reconciliation again after any change of station, ad server or trafficking process. Movement in those systems is the usual cause of a gap between booked and aired weight.

Worked example, illustrative figures only. A regional buy across two stations for four weeks books 128 spots; the affidavits show 120 aired, so reconciliation closes an eight spot gap.

Audience: published RAJAR totals put weekly reach in the survey area at 180,000 adults, recorded as survey-based context. Response: 640 tracked actions, split between promo code redemptions and calls inside a 24 hour window.

Spend: £9,000, which gives £75 per aired spot and £14.06 per response. The figures are illustrative, so your own depend on the dayparts bought, the offer and the response channel.

Free tools cover this scale. Google Looker Studio connects to Google Sheets, Google Ads and BigQuery at no licence cost, and Microsoft Power BI has a free desktop version.

Tableau Public is free, but published workbooks are public, so keep client spend off it. A Google Sheets workbook with the five column groups above is enough for one region.

Build time depends on the number of sources and how clean the station affidavit export is.

What to put on the dashboard

Choosing between reach and response panels

Reach tells you how many people could have heard the campaign. Response tells you what they did next. Both belong on the dashboard, but they answer different questions.

A campaign can post strong reach and weak response. That is usually a creative or offer problem, not a media buying one.

Setting a refresh schedule that holds

Daily data needs a daily owner. Quarterly survey data needs a calendar reminder, not a person. Automate what you can and name an owner for the rest.

If your reporting keeps drifting, radio advertising measurement mistakes in England lists the faults that recur in English campaigns, from daypart mapping errors to mismatched attribution windows, with a fix for each.

Add economic context before you present

Advertisers cut and restore budgets in line with wider conditions. Bank of England statistics on the UK economy give you a neutral reference when a client questions a cost increase or a quiet quarter.

Label this panel as context, not attribution. It explains the environment, not the campaign result.

A single quarter rarely justifies a conclusion. Show the trend across several periods alongside the campaign dates.

Presenting the dashboard as proof of spend

A client asks two things: did the spots air, and what did they return. Put booked against aired spots, the station affidavits and the media cost on the first page.

Follow it with the response panel and one cost per response figure. State the attribution window and the source and refresh date beside every number.

Show audience data as context, not proof. RAJAR supports scale, while the response panel is the layer that ties spend to an outcome.

Close with the numbers you can defend and how the attribution window was set, so the client sees what is measured and what is estimated.

Common questions

How often should a radio advertising reporting dashboard be updated?

Delivery and response panels should refresh daily. Audience survey data refreshes quarterly, and cost data monthly once invoices are reconciled.

Can I use RAJAR data to prove a single spot was heard?

No. RAJAR measures listening across a sample and publishes totals and averages. It supports audience context, not spot-level proof.

What is the biggest dashboard mistake?

Blending delivery, audience and response into one score. When the number moves, nobody can tell which layer caused it.

Do I need a paid dashboard tool?

Not necessarily. A spreadsheet with clear metric definitions, named owners and a source column will outperform an expensive tool with undefined metrics.