
Strategy
Part of Podcast advertising frequency capping: a UK guide
Podcast advertising frequency capping: a UK guide
Podcast advertising frequency capping in the UK: the cap types buyers use, where DAX and Acast set them, the steps to review one and the data rules.
Podcast advertising frequency capping decides how many times one listener hears the same spot. In the UK the ceiling is usually set by whoever runs dynamic ad insertion, and it is agreed in the insertion order rather than left to the show.
What to take away
- Frequency capping is a limit on how often one listener hears the same podcast ad, set per day, per week or per campaign.
- In the UK the cap is usually applied by the platform or network running dynamic ad insertion, not by the individual show.
- A tight cap protects the listener experience but spreads the same budget over more people, which usually raises the effective cost per thousand impressions.
- Host-read spots are harder to cap because delivery follows the episode download rather than a server call.
How capping differs from a budget cap
A frequency cap limits what one listener hears. A budget cap limits what the advertiser spends. Buyers confuse the two when briefing a UK network.
Frequency cap vs budget cap
Frequency cap
- What it limits
- One listener's ad exposures
- Set by
- Platform or network
- Main risk
- Listener ad fatigue
Budget cap
- What it limits
- Advertiser spend
- Set by
- Advertiser or agency
- Main risk
- Budget overspend
Podcast capping operates at three levels: the campaign, the publisher and the listener. A campaign cap says the whole buy will not serve more than a set number of impressions to any one listener.
Deduplication is the harder half. A platform needs a device identifier, an IP address, a podcast app sign-in or a cookie to recognise the same person twice. Where none exists, an episode download cannot be capped.
The four caps UK buyers meet
The four that appear in UK insertion orders are the campaign cap, the publisher cap, the listener cap and the daily or weekly cap. The campaign cap covers the whole buy, the publisher cap covers every show one network runs, the listener cap fixes the ceiling for one person or device, and the daily or weekly cap sets how often that ceiling resets. In an insertion order it is one line: the maximum number of impressions any one listener may hear in a stated period.
Four UK podcast cap types
Cap type
- Per episode
- Impressions on one episode
- Per week
- Exposures in seven days
- Per campaign
- Total exposures per listener
- Per publisher
- Exposures within one network
What it counts
- Per episode
- Platform
- Per week
- Platform or network
- Per campaign
- Platform
- Per publisher
- Network
Where set
- Per episode
- Stop one show dominating
- Per week
- Spread without nagging
- Per campaign
- Standard network buys
- Per publisher
- Several networks same buy
When used
- Per episode
- Per week
- Per campaign
- Per publisher
Where UK podcast caps are set
Platforms that run dynamic ad insertion, including Global's DAX and Acast, allow a cap to be set at campaign level, so it can apply across every show on the buy.
Direct host-read deals work differently. The host reads once per episode, so the exposure count follows the download figure. Capping then means buying fewer episodes, not editing a dashboard.
Who controls the cap therefore depends on the deal. A network buy and a direct buy give the advertiser very different levers, as we set out in podcast network advertising versus direct buying.
Setting and reviewing a cap: four steps
- Decide the listening experience you want. Write down the maximum number of times one person should hear the spot in a week.
- Check what the platform counts. Ask whether the cap uses device, IP, account or household level matching, and whether unaided downloads are excluded.
- Price the reach trade off. A tighter cap delivers more unique listeners for the same impressions, so the effective cost per thousand rises.
- Review mid-flight. Look at completion rates and any listener comments before tightening or relaxing the number you agreed.
An illustrative cap calculation
Suppose a campaign buys 300,000 impressions across four shows and the cap is three per listener. The arithmetic ceiling is 100,000 listeners. These figures are illustrative.
Set the cap too tight and the buy struggles to spend. Set it too loose and the same listener hears the same spot week after week, which is where fatigue starts.
Repetition is not automatically bad. A host-read mention repeated across a network can build recall, while a pre-recorded spot in the same slot every day can irritate. The trade-off between warmth and control is set out in host-read versus programmatic podcast ads.
Data, consent and the paperwork
A cap that recognises the same listener across shows is processing personal data. The UK GDPR, retained in UK law, sets out the lawful bases and the rights involved: UK GDPR contents page.
The ICO's guide for organisations explains how to choose a lawful basis and keep records. Ask networks what they store about a capped listener, and for how long: guide to data protection for organisations.
Cookies and device identifiers fall under a further UK regime. The Privacy and Electronic Communications Regulations 2003 (PECR) govern storing information on, or reading it from, a listener's device, and the ICO enforces PECR alongside the Data Protection Act 2018 and publishes guidance on cookies and similar technologies. Where a cap relies on a cookie or a device fingerprint, PECR applies as well as the UK GDPR.
Repeated exposure does not change the rules on the ad itself. The CAP Code is written by the Committee of Advertising Practice and enforced by the Advertising Standards Authority, and it applies to podcast sponsorship as it does to any other medium: advertising codes.
Common questions
Does frequency capping cut podcast reach?
Yes, by design. Every impression you stop serving to a heavy listener is an impression available to someone new, so a capped buy trades repetition for unique reach.
Do UK podcast platforms apply a default cap?
Global's DAX and Acast let a cap be set at campaign level, and any platform-level default sits behind that setting rather than being obvious in the dashboard. Confirm the number and the counting method in the insertion order rather than assuming the platform will handle it.
Can a host-read slot be capped?
Only by buying fewer episodes or rotating shows. A host-read ad sits in the audio file, so anyone who downloads that episode hears it in full.
Where should a small UK advertiser start?
Start with the number of exposures you would be comfortable hearing yourself, then test it. An illustrative £3,000 buy across two shows will not need the same cap as a national network campaign.



