Cross-Screen Frequency: How Much Is Too Much?

The Problem Is the Distribution, Not the Average

Ask most teams for their frequency and they will quote one number: the campaign average. That number is close to useless on its own. An average of four exposures can mean everyone saw the ad four times, or it can mean most people saw it once while a small group saw it twenty times. Those are opposite outcomes with the same mean, and only one of them is a problem. When you validate a frequency cap, you are validating the shape of the curve, not its center.

The concern is not new. In 1972 Herbert Krugman argued in the Journal of Advertising Research that the first exposure answers "what is it," the second answers "what of it," and the third is a reminder before attention starts to fall away (Why Three Exposures May Be Enough). Whether the right number is three or seven for your category, the principle holds: response to repetition rises, plateaus, then decays. Exposures past the plateau do not persuade. They spend money and, past a point, they irritate.

The good news for connected TV is that the raw oversaturation story is often overstated. An Innovid and ANA analysis of 35 CTV campaigns from 20 major advertisers found an average frequency of 4.6 exposures, with the typical campaign reaching only about 13 percent of the roughly 75 million addressable U.S. CTV households, and it called the industry's frequency panic highly exaggerated. The same analysis put the average cross-publisher duplication rate near 32 percent. That last figure is the real lesson: the waste is not that one publisher runs the ad too often, it is that the same person is counted separately on ten different platforms that never compare notes.

Why Cross-Screen Frequency Is Hard to See

Each buying surface enforces its own cap against its own identifier. A CTV platform caps against a device or household graph. A programmatic desktop buy caps against a cookie or a hashed email. A mobile app buy caps against a mobile advertising ID. None of those keys is the same key, so a person who is one household on the living room screen, one cookie on a laptop, and one advertising ID on a phone is counted three times. Set a cap of three on each surface and your true cross-screen frequency can be nine before anything looks wrong in any single report.

This is why cross-screen frequency is an identity problem before it is a media problem. To read the real distribution you need a person-level or household-level key that survives across screens, and you need it to be stable enough that the same human resolves to the same key on Monday and again on Friday. That is the job of an identity graph: to collapse the device-level fragments into one countable entity so an exposure ledger can add them up. Without that spine, the frequency report is measuring devices, and devices are not the thing you are trying not to annoy.

What Counts as Too Much, by Screen

There is no single right cap, because the cost of an extra exposure is not the same on every screen. A CTV spot is unskippable, long, and loud in a shared room, so repetition fatigues faster and a lower cap usually pays. A desktop display unit is cheap and easy to ignore, so the same person can tolerate more before the marginal impression turns negative. The table below is a starting frame for a validation conversation, not a rule. Set your own thresholds from your creative wearout curve, then measure against them.

How to Validate a Frequency Cap

Validation is a measurement job with a defined output: the true, deduplicated exposure distribution for the campaign, read against the cap you set. Setting a cap in a platform UI is the easy half. Proving it held across every surface, after impressions have been resolved to people, is the half that separates a control from a hope. Run it as a sequence you can repeat and defend.

1. Fix the counting unit first. Decide whether the cap is per person or per household, and require every surface to report against that same unit, not against its native device key.
2. Join impression logs to a stable cross-screen key. Resolve CTV, desktop, and mobile exposures through one identity graph so the same human is one row, not three.
3. Read the distribution, not the mean. Report the share of exposed people at zero, one to cap, and above cap. The above-cap bucket is the number that proves or breaks the control.
4. Attribute overage to a cause. Separate cross-publisher duplication from a genuinely broken cap. The Innovid and ANA finding was that duplication, not a single greedy publisher, drives most overage.
5. Hold out a control group and re-run the read mid-flight, the same discipline you would apply to any cross-channel measurement test, so a cap change can be shown to move the curve.

Notice that steps two and three are impossible without the identity work in step two being trustworthy. If the graph over-merges, distinct people collapse into one and your frequency looks higher than it is. If it under-merges, one person stays three devices and your frequency looks lower than it is. Before trusting any cross-screen frequency report, ask the same coverage and accuracy questions you would ask of a match-rate claim: what universe, what as-of date, and whether the links were observed or modeled. A frequency number inherits every weakness of the graph underneath it.

Building the Cross-Screen Key

The practical bottleneck is a person-level key with enough coverage across all three screens to make the deduplicated count meaningful. GSDSI approaches this with an identity graph of more than 200 million U.S. MAID to hashed-email links, which is the connective tissue that lets a mobile advertising ID, a hashed email on desktop, and a device on a television resolve to the same person for a frequency read. Those links sit against a base of 301 million plus U.S. consumer records, so the resolved person is not just a match, it is a match you can profile and suppress against.

On the television side specifically, the CTV and Smart TV (ACR) feed contributes roughly 13 to 14 million unique CTV IDs each month, which is the raw exposure signal that has to be deduplicated against desktop and mobile before any household-to-person expansion. Automatic content recognition tells you what played on the screen, but it counts the screen, not the viewer. Folding those CTV IDs into the person graph is exactly the step that turns a per-device impression log into a cross-screen frequency you can cap and validate. The vocabulary for how these identifier types relate is well covered by the IAB Tech Lab standards, which are a useful shared language for a diligence conversation with any measurement vendor.

One caution on definitions. Cross-screen deduplicated reach and frequency is a measurement discipline with published standards, not a vendor slogan. The MRC Cross-Media Audience Measurement Standards define reach and frequency on qualifying viewable impressions and set expectations for how a vendor unifies linear, streaming, and digital exposures into one deduplicated figure. When a partner quotes a cross-screen frequency, ask which standard the number follows and what qualifies an impression to be counted at all. A frequency built on unviewable impressions is measuring delivery, not exposure.

What Too Much Actually Costs

Over-frequency has two bills. The obvious one is media waste: every impression served to a person already past their effective frequency is budget spent to move a needle that has stopped moving. The quieter bill is brand cost. Krugman's third-exposure disengagement is polite language for the fatigue and resentment that heavy repetition produces, and that resentment does not show up in an impression log. It shows up later, as a softer response to the next campaign. A validated cap protects both budgets at once, and it does so with a number you can put in front of a finance team: the count of people who saw the ad more than you decided they should, and what you spent reaching them the extra times. If you want that read on a scoped sample of your own campaigns, contact us and we will frame the measurement plan.