The Frequency Cap You Set Per User Is Enforced Per Identifier, Not Per Person

Frequency capping is one of the oldest levers in digital media buying. The logic feels simple: decide how many times a person should see your ad within a given window, set that number in your DSP, and trust the platform to enforce it. The problem is that the word "person" in that description is doing work that the technology cannot actually do.

DSPs enforce frequency caps against identifiers, not against human beings. An identifier might be a cookie, a mobile advertising ID, a hashed email, or a connected TV device ID. When someone uses a laptop browser, a mobile phone, and a smart TV to browse content in the same week, they may carry three or four distinct identifiers that your campaign recognizes as separate entities. Each one receives its own fresh frequency counter. A cap set at five impressions per week can deliver fifteen or more impressions to the same person without ever technically violating the rule you set.

Why identity resolution does not fully close this gap

Some buyers assume that identity resolution solves the problem. If your DSP or identity partner links multiple identifiers to a single resolved person, the frequency cap should follow the person, not the device. This is true in principle and partially true in practice, but the resolution is never complete.

Identity graphs vary in their household and cross-device coverage. A deterministic link between a hashed email and a mobile ID exists only when a user has authenticated in both environments in a way the graph captured. Probabilistic links are inferences, not observations, and the confidence level on those links varies by publisher environment, geography, and device type. In inventory that runs outside authenticated environments, a meaningful share of your impressions will be delivered to identifiers with no resolved link to each other, and those impressions will each count separately toward separate caps.

The practical result is that your effective frequency, meaning the impressions actually received by a single person, is almost always higher than the cap you configured. How much higher depends on the authenticated share of your media mix, the maturity of the graph your DSP uses for identity resolution, and how fragmented the identifier landscape is across your target channels.

Where the fragmentation is highest

Connected television is the environment where identifier fragmentation causes the most visible overcounting. A household may have two streaming apps on the same physical television that report different device identifiers to different ad servers. If your CTV buy runs across multiple streaming publishers or is aggregated through a programmatic CTV marketplace, the same household can appear as several distinct entities, each accruing impressions toward its own cap.

Open web display and mobile web environments add browser-level fragmentation on top of device-level fragmentation. A user who clears cookies or uses multiple browsers generates fresh identifiers that your campaign treats as new individuals. Privacy browser settings in Safari and Firefox have accelerated this pattern by reducing cookie persistence, so the practical lifespan of an identifier in those environments is shorter than the frequency window you may have configured.

Cross-channel campaigns compound the issue further. Frequency logic set in a display DSP does not communicate with the frequency logic in a social platform or a programmatic video buy unless your team has built an explicit cross-channel suppression layer, which most media plans do not include.

How to pressure-test your own campaign

A useful starting audit is to compare your campaign's delivered impression distribution against what a realistic person-level frequency would look like given your total reach and impression volume. If your DSP reports reaching one million unique identifiers at an average frequency of four, but your total impressions suggest the true person-level reach is closer to six hundred thousand, you have a rough signal that identifier fragmentation is inflating your apparent reach and deflating your apparent frequency.

Clean room environments can help here if your media partners support them. A clean room query that joins impression logs against a known identity graph, rather than relying on the DSP's own identifier count, can surface a more accurate picture of how many distinct resolved individuals your campaign actually reached and at what true frequency. This will not be a perfect count, since graph coverage is never complete, but it is structurally more accurate than raw identifier-level reporting.

For campaigns where frequency control matters most, typically upper-funnel brand or awareness campaigns where overexposure is a budget efficiency problem, it is worth asking your DSP and your identity partner specifically how cross-device frequency capping is enforced in each channel of your buy. The answer will tell you where you should expect cap leakage and where you can reasonably trust the number you set.

Setting caps that account for identifier fragmentation

One practical adjustment is to treat your frequency cap as a per-identifier ceiling rather than a per-person target, and set it accordingly. If your intended person-level frequency is five impressions per week and you estimate that the average person in your target environment carries roughly two identifiers your campaign will recognize as distinct, a per-identifier cap of three will get you closer to the actual person-level outcome you want. This is a rough calibration, not a precise formula, but it is a more honest way to use the lever you have.

Another adjustment is to weight your frequency controls more tightly in channels where identity resolution is weakest. Open web inventory outside authenticated publishers, mobile web, and fragmented CTV aggregators are the environments where identifier count diverges most sharply from person count. Social platforms with strong authentication tend to enforce caps closer to the person level because they have high rates of logged-in inventory. Acknowledging that your buy is not one uniform environment for frequency purposes allows you to apply different caps by channel rather than one global setting that will underperform in some placements and over-restrict in others.

The measurement implication

Frequency fragmentation is also a measurement problem. If your post-campaign report shows reach and frequency at the identifier level, the reach number is overstated and the frequency number is understated relative to the actual person-level experience. Campaigns evaluated on those numbers may appear to have delivered more broadly and more gently than they actually did, which can lead to conclusions about creative fatigue, budget efficiency, or audience saturation that do not reflect what actually happened.

Finding this gap does not require a technology overhaul. It requires asking, for each channel in your plan, what the cap is enforced against, how cross-device resolution works in that environment, and what the identifier-to-person ratio looks like given your media mix. Those are answerable questions, and the answers change how you read the frequency numbers your platform returns.