The Frequency Cap You Set at the Campaign Level Is Not the Frequency Any Individual Person Actually Experiences

Frequency capping is one of the oldest controls in digital media buying. Set a cap, protect your audience from overexposure, contain waste. The logic feels airtight. The problem is that the cap operates on identifiers, not on people, and most people carry more than one identifier across the channels and devices in your plan.

Understanding why this matters requires a short detour into how frequency is actually counted.

How a Cap Gets Applied

When a DSP enforces a frequency cap, it tracks how many times a specific identifier, a cookie, a mobile advertising ID, a connected-TV device ID, or a hashed email, has been served within your specified window. When that identifier hits your cap, the DSP stops bidding for impressions associated with it. This works correctly for the identifier. The identifier is capped. The person behind it may not be.

Consider a plausible scenario. A single buyer researching your product category uses a work laptop on a browser with one cookie, a personal laptop on a different browser with a second cookie, a smartphone with its own mobile advertising ID, and a connected TV that contributes a fourth device-level identifier. Your campaign cap of five impressions per week applies separately to each of those four identifiers. That person could theoretically see your ad twenty times in a week before any one cap triggers, because no single identifier accumulates more than five exposures.

This is not a hypothetical edge case. It is the default behavior of nearly every demand-side platform, and it reflects the structural reality that frequency management was designed around a world where one cookie reliably described one person on one device.

Why Cross-Device Resolution Does Not Fully Solve It

Some DSPs offer cross-device frequency management through their own identity graphs or through integrations with third-party graphs. When this is available, it is worth using. But cross-device matching introduces its own constraints that buyers should understand before treating it as a complete fix.

Device graphs are probabilistic for significant portions of the population. A deterministic match, where the platform has confirmed that two devices belong to the same person through a logged-in signal, is the most reliable link. Probabilistic matches, inferred from shared signals like IP address, location pattern, or behavioral similarity, carry a confidence level that varies and is rarely surfaced to the buyer. When the graph is uncertain, the platform may or may not consolidate frequency across those devices.

Cross-device identity resolution also operates differently across channels. Open web display, mobile in-app, connected TV, and digital audio each resolve identity through different mechanisms, and those mechanisms do not always connect cleanly inside a single campaign. A buyer running a cross-channel plan across multiple DSPs, or across a DSP and a walled garden, has essentially no shared frequency view across those environments. Each platform counts its own identifiers independently.

What This Means for Campaign Design

For practical purposes, buyers should treat any campaign-level frequency cap as a per-identifier floor rather than a per-person ceiling. The cap prevents any single identifier from accumulating extreme exposure, which is still valuable. But it does not reliably protect a person with multiple active identifiers from aggregate overexposure.

A few adjustments can make frequency management more realistic given these constraints.

Set caps lower than your intended per-person threshold. If your goal is to limit a person to five impressions over the course of a week, setting the per-identifier cap at five will produce actual person-level exposure that exceeds that target. The appropriate adjustment depends on your audience's likely device footprint and channel mix, which you can estimate but not observe directly. For a B2B audience that regularly uses multiple work and personal devices, the gap between intended and actual frequency is likely wider than for a simpler media environment.

Treat channels separately when you cannot unify identity across them. A cross-channel plan with a single unified frequency cap often means the cap is enforced within each channel against its own identifier set, not across channels. Acknowledge this when setting expectations with stakeholders. A plan that reaches the same person three times on display, twice in streaming audio, and twice on connected TV has delivered seven exposures regardless of what any individual channel's cap says.

Look at delivery curves, not just cap compliance. Many DSPs surface impression delivery distributions that show how often the average identifier was served. Reviewing this distribution mid-flight can reveal whether a campaign is delivering efficiently across many identifiers or concentrating heavily on a smaller pool. Concentration patterns, even when the stated cap is not technically exceeded, often indicate that the practical addressable audience is smaller than planned.

Use suppression and audience exclusion as complementary controls. When you can build an exclusion audience from post-exposure signals, such as a pixel event indicating a desired action was taken, you can remove converters from the eligible audience rather than relying solely on frequency mechanics. This does not fix the multi-identifier problem, but it reduces redundant exposure to people who have already completed the action you were trying to drive.

The Measurement Implication

Frequency and outcome analysis often looks cleaner in platform reporting than it should. When a platform reports that the highest-converting impressions fell within the three-to-five frequency range, that range reflects identifier-level frequency, not person-level frequency. If a portion of your converting audience held two or three identifiers that each accumulated separately, their effective exposure prior to conversion was higher than the report reflects.

This matters when frequency-to-outcome curves are used to justify cap settings in future campaigns. A curve built from identifier counts may be modeling a different variable than you intend. The practical consequence is that optimal frequency guidance derived from past reporting may underestimate the exposure level your actual audience received before converting, which makes those recommendations less reliable as planning inputs.

A Reasonable Posture

Frequency caps are still worth setting carefully. They provide a real constraint on per-identifier accumulation and limit the most extreme overexposure scenarios. The goal is simply to hold accurate expectations about what they do and do not govern.

A campaign with a five-impression weekly cap is not a campaign where no person sees the ad more than five times. It is a campaign where no single identifier is served more than five times. For many audiences and channel configurations, those two statements describe meaningfully different outcomes. Keeping that distinction visible inside the planning process is the starting point for more honest frequency management.