Key takeaways
- Caps are usually set per viewer ID, per campaign, per creative, or per advertiser within a time window such as hour, day, or week.
- Tighter caps improve viewer experience but reduce impressions sold, so revenue and watch-time must be balanced.
- Caps are enforced by the ad server or SSAI layer using viewer identifiers, not by the player itself.
- OTT caps often differ from web caps because households and devices are tracked as well as individual users.
How frequency capping works
Frequency capping is a delivery rule. The ad server keeps a short history of which viewer has seen which creative, then checks every new ad request against that history before returning a response.
The key inputs are:
- Identity. A stable viewer identifier such as a logged-in user ID, a household ID, or a device ID.
- Scope. What is being capped: a single creative, an entire campaign, an advertiser's full flight, or a category.
- Window. The time period the count applies to, typically per hour, per day, per week, or per session.
- Limit. The maximum number of impressions allowed inside that window, for example 3 ads per hour per viewer.
In OTT and CTV, capping happens at the server side so the same viewer is recognized across smart TVs, phones, tablets, and set-top boxes that share an account or household. When the limit is reached, the ad server substitutes a different eligible creative, drops to a house ad, or returns a no-ad response for that slot. Caps work alongside ad targeting rules and with QoE goals, since showing the same ad too often is one of the fast ways to push a viewer off a stream.
Why frequency capping matters for a streaming business
Capping is a direct lever on two competing goals: ad revenue and viewer retention. Show the same ad too many times and viewers tune out, complain on social, or leave. Show too few impressions per viewer and advertisers will not pay premium CPMs, because reach and repetition both factor into brand recall.
For an operator, the practical questions are:
- How many ads per hour is the channel willing to run.
- How aggressive the cap is per campaign versus per advertiser.
- How the cap interacts with live vs on demand inventory, since live windows are short and burn through caps fast.
- Whether caps apply per device, per account, or per household, which changes how many distinct impressions a campaign can deliver.
A well-tuned cap also smooths delivery. Without one, an early-session viewer can see the same spot repeatedly while a late-session viewer sees none, which is bad for the audience and bad for the campaign's measured reach. Capping is also part of any Ad Campaign Management workflow, because operators need data that shows how many viewers hit the cap, when, and which creative they were shown.
Common mistakes with frequency capping
- Capping on the wrong identifier. Capping per session but not per user lets the same person reset the count by reopening the app, which advertisers will notice in post-campaign data.
- Setting a cap and forgetting creative rotation. A cap of 6 per day still feels like 6 of the same ad if there is only one creative in the rotation.
- Applying web caps to CTV. Web caps of 1 or 2 per day usually feel stingy on a connected TV, where viewers expect fewer, higher-quality spots.
- Ignoring shared devices. Roku, Fire TV, and smart TV households often have more than one viewer per device, which inflates raw impression counts.
- Not separating live and on demand windows. A live sports run can exhaust a daily cap in 20 minutes, leaving the rest of the day unfilled for that campaign.
How Flicknexs handles frequency capping
Flicknexs applies frequency caps inside its SSAI pipeline, so the limit is checked at ad insertion time on every request rather than in the player. Caps can be set per advertiser, per campaign, or per creative across SVOD, AVOD, and TVOD inventory, and they use the viewer and household identifiers available in your login and device graph. The self-serve advertiser portal exposes cap fields, delivery data, and the impression history that buyers and operators need to tune limits together. Multi-audio tracks, geo-restriction, and ad targeting rules all sit behind the same server-side decision, so caps hold even when the same viewer switches devices.
Learn how this fits into a channel launch on the Launch a FAST channel page.
Done reading about Frequency Capping?
Flicknexs ships it as part of a white-label streaming platform: web, mobile and TV apps, billing, ads, DRM and playout, on your own domain.