Overview
Radio is one of the custom and non-conforming marketing sources Provalytics can ingest when there is no native platform connector. This is a strong fit for:- terrestrial radio campaigns
- satellite radio buys
- local station activity
- agency-managed radio schedules
Recommended data structure
Best practice is to send Radio data in a consistent hierarchy:ChannelStation NameCreative
DateImpressionsor the closest available exposure metricChannelStation NameCreative
DaypartCampaign NameSpendMarketProgram
Why this structure matters
This structure gives Provalytics enough detail to:- separate Radio from the rest of the media mix
- evaluate performance by station
- distinguish creative-level differences when that detail exists
- analyze how Radio contributes alongside search, social, digital video, and other channels
Historical backfill and cadence
If historical data is available, best practice is to backfill it before the feed goes live in production. That allows the model to train on the data before it begins appearing in the live dashboard. After setup, the data should continue arriving on the same cadence as the rest of your reporting inputs so the dashboard and model outputs stay current.How teams usually send it
Radio data can be delivered through any of Provalytics’ custom-data intake methods, including:- recurring email feeds
- Google Sheets
- SharePoint
- S3 bucket delivery
- Snowflake delivery
- manual uploads
- BigQuery delivery