Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Programmatic Advertising › Troubleshooting

Programmatic Frequency Cap Not Working

Why people see the ad far more often than the cap allows: caps per identifier, caps only on line items, other platforms outside the cap and lost identifiers.
Troubleshootingintermediate19 min readUpdated

First, read the frequency distribution and list every system serving the same people

The cross-platform reach and frequency guide states the rule everything else follows from: a cap limits how many times one identifier is served an ad in a window, caps exist at several levels, each counts against a different identifier, and each is blind to everything outside its own system. The frequency a person experiences is the sum of what every system served to every identifier they carry. A complaint about relentless exposure is therefore not evidence that the cap failed; it is evidence that exposures reached the person through something the cap does not count. The diagnosis is to find out what.

Start with the distribution, not the average. The reach versus impressions comparison defines frequency as impressions divided by reach for the same period and level, an average over a skewed distribution, so the same figure can mean the ad shown once to most people and many times to a few. The DSP's reach report returns, for a chosen level and date range, modelled reach, average frequency and a frequency distribution showing how many people were reached once, a few times or many times, and the reach guide names the figure to read from it: the share of impressions served above the intended frequency, which is the key performance indicator that tells whether the cap is working. A long tail far above the setting, in a report where the average sits comfortably beneath it, says the cap is counting something other than the people the report is modelling. Read the distribution over the cap's own window, because a lifetime figure hides the recent climb, a point the frequency and creative fatigue guide makes for the social side of the same problem.

Then write down what the plan promised and every system that serves the same people. The media planning framework treats reach and frequency as plan figures set before the money moves, with the distribution rather than the average as the check, and the reach and frequency calculator turns the audience size and the impressions the budget buys at the planned price into the average frequency the plan should expect; a plan whose arithmetic already implies a frequency far above the cap has found its answer before any setting is opened. Beside that figure, list the systems: the DSP's campaign, insertion orders and line items, each with its own cap or none; the advertiser's ad server, whose ad-level frequency settings count its own identifier across every buy using its tags; every walled-garden campaign on social or video bought outside the DSP; any direct or publisher buy; and the verification vendor, which caps nothing but reports the distribution it measured. The reach guide's table sets out what each one counts against and what each cannot see, and the diagnosis is a matter of placing the extra exposures in that table. The frequency glossary entry carries the short definition for anyone new to the figure.

Diagnosis table

Diagnosis

SymptomCheckLikely causeFix
Average frequency sits near the cap, the distribution has a long tail far above it, and complainants use several devicesThe reach report's distribution against the cap's window, and which identifier the cap counts in each environment the plan buysThe cap counts identifiers, not people, so one person on several browsers and devices is several capsSet the cap as a ceiling per identifier with the coverage the plan expects, and report the share of impressions above the intended frequency rather than the average
Every line item reports frequency under its own cap while the campaign's distribution does notWhere caps are set at campaign, insertion order and line item levelCaps set only on line items, so each tactic serves up to its own cap and the person sees all of themSet the campaign cap as the outer limit and keep line item caps for tactic-specific control
The DSP's figures look healthy and the complaints name video or social placementsEvery buy outside the DSP that targets the same audience, and its own frequency settingsExposures bought outside the DSP, on social, video or direct, that no DSP cap countsCap inside each platform where a control exists, allocate one plan-level ceiling across systems and deduplicate with a written overlap assumption
Several insertion orders or line items carry the same list, with duplicates and paused clones among themThe audience assigned to every object under the campaign and whether a campaign-level cap existsSeveral insertion orders or line items built around the same audience with no campaign-level ceilingConsolidate the objects around one audience, add the campaign ceiling and retire the duplicates
Reports understate frequency, lists are far smaller than site traffic, and exposure concentrates in environments without identifiersList sizes by environment, the consented and cookie-capable share of traffic, and where the impressions servedIdentifiers missing because of consent and browser limits, so the cap cannot recognise repeat exposureExpect real frequency above the setting, weight delivery towards environments where the identifier holds and read the modelled figures with their limits
The cap is reached early, pacing slows, then spend recovers while reach stays flat and frequency climbsThe audience size against the impressions the budget buys, read in the calculator, and the line item's bid request and bid figuresA small audience against a large budget, so the DSP buys above the cap through identifiers it cannot matchSize the budget to the audience, widen the audience or accept under-delivery, and decide which in advance

Fix, verify and prevent each cause

The cap counts identifiers, not people

The reach guide describes the identity a DSP has to work with: third-party cookies are per browser rather than per person, so one person on a laptop and a phone is at least two cookies even where cookies work; mobile apps use a device advertising identifier that is per device and reset at the person's choice; logged-in identity is the strongest kind and the most bounded; and modelling fills the gaps. A cap is applied to each of those identifiers separately, which is why the guide's practical reading is that a cap is a ceiling per identifier rather than per person, and why a person who meets the brand on three devices can be served three caps' worth. The Display & Video 360 Help Centre documents the levels a cap can be set at, and the bidding and pacing guide notes that it also describes how DV360 manages frequency in environments without cookies or device identifiers, including modelled approaches, which change often enough that the help page is the source rather than a summary here.

Fix: stop treating the cap as a promise to the person. Read the distribution for the people the report models, note the share served above the intended frequency, and set the cap with the identifier coverage of the plan's environments in mind, lower where the plan buys mostly in environments where one person is many identifiers, rather than copying a figure from a plan that bought elsewhere. Then shape the rest of the exposure with the controls that do not depend on recognising the person: audience exclusions for recent converters, sequencing by recency and creative rotation, as the fatigue guide sets out.

Verify: over the cap's window the distribution's tail shortens and the share above the intended frequency falls, while reach holds; if reach collapsed, the cap is now binding on identifiers the plan needed.

Prevent: write the cap into the plan as a ceiling per identifier with the coverage assumption beside it, and report the share above the intended frequency every month so the gap between the setting and the experience is a known figure rather than a surprise.

Caps set only on line items

The bidding guide is the owner of where caps live: DV360 lets them be set at campaign, insertion order and line item level, each as a number of impressions per period or as no limit, and every level's cap is enforced for the impressions under it, so caps stack. The campaign's cap bounds the whole plan, the insertion order's cap bounds its channel or budget line, and the line item's cap bounds the tactic. The usual pattern the guide describes is a loose cap at campaign level to protect the person from the plan as a whole, with tighter caps on remarketing line items. The failure it lists among its common mistakes is caps only on the line item: each line item serves up to its own cap and the person sees all of them. A plan with several tactics against overlapping audiences and no cap above them has, in effect, multiplied its cap by the number of line items.

Fix: set the campaign cap as the outer limit for the plan and keep line item caps for the tactics that need a lower one, such as a long video execution that tires faster than a static banner, as the DV360 brand awareness setup recommends; where channels sit in separate insertion orders, use the insertion order cap to bound each channel beneath the campaign ceiling.

Verify: the campaign-level reach report's distribution now shows the tail bounded at the ceiling for the identifiers the campaign can see, and the line items that shared an audience each report lower frequency without the total reach falling.

Prevent: make the campaign cap a line in the pre-flight check beside pacing and bid strategy, so that a line item added mid-flight inherits the ceiling rather than running to its own, and keep the ceiling decision in the plan where the next trader will find it.

Exposures bought outside the DSP

A DSP cap counts the identifiers the DSP can see and nothing else. The reach guide's table says what each level cannot see: a DSP campaign cap is blind to other DSPs, direct buys and walled gardens bought elsewhere; a walled-garden campaign on social or video caps against the platform's own logged-in user and sees nothing bought outside it; the advertiser's ad server, CM360, counts its identifier across every buy that passes through its tags and nothing that does not. Across systems, caps do not combine at all, so a tight cap in one does nothing about exposures from another, and the reach guide's answer to the question of whether a DSP cap applies across platforms is that exposures bought outside it are never counted by it. YouTube bought through DV360 can be included in the DSP's cross-property reach estimate; a social campaign bought separately never can.

Fix: list the buys outside the DSP that reach the same people and cap each inside its own platform where a control exists; on the social side the fatigue guide notes that a frequency control is documented for reach-optimised ad sets and for reach and frequency buying, while conversion objectives manage frequency indirectly through audience size, exclusions and rotation. Then allocate one plan-level ceiling across systems rather than setting the same number in each as though they combined, and record the overlap assumption used to deduplicate reach, because the reach guide is clear that walled gardens cannot be deduplicated from outside and the sum of platform reach is an upper bound. The Campaign Manager 360 Help Centre documents the ad server's frequency settings, which the reach guide places at ad level across every buy using its tags; where the plan's buys all run through those tags, that is the widest single cap available, with the identifier caveat the guide attaches.

Verify: the combined frequency for people reached on both sides, read with the overlap assumption, sits inside the plan's ceiling, and the complaints that named social or video placements stop.

Prevent: give every plan a table of systems with the cap each one holds and the identifier it counts, and treat a new buy on a new platform as a change to that table before it launches.

Several objects around the same audience with no campaign-level ceiling

The DV360 account structure guide places a frequency cap at the campaign, insertion order and line item levels of the tree and explains what each level is for: the campaign holds the objective and a campaign-level cap, the insertion order holds a budget line, and the line item holds a tactic. Its rule for line items is one per combination that needs its own budget, bid or report line, and it names over-splitting as the commoner error: dozens of thin line items, several of them paused duplicates that somebody eventually unpauses. The awareness setup draws the consequence for frequency: without a ceiling applied above them, each line item serves its own audience up to its own limit, and the same person collects exposures from every tactic. Three line items built on the same remarketing list, each with a sensible cap, are one person served three times the sensible figure.

Fix: read the audience assigned to every object under the campaign, consolidate the objects that carry the same list into one line item per combination the structure guide's rule allows, retire the paused duplicates with a reason and date, and add the campaign ceiling so that whatever remains split is bounded from above. Where two tactics must stay separate because they need different bids, keep them separate and let the campaign cap do the bounding.

Verify: the reach report at campaign level shows the tail bounded and reach unchanged, and the Structured Data File export of the campaign lists no object that targets a list already targeted by a sibling without a reason in its name.

Prevent: record each insertion order and line item with the reason it is separate from its neighbours in the build sheet before anything is created, name the audience in the line item name as the structure guide's convention does, and read the duplicates out of the tree in the quarterly structure review.

The DV360 audiences guide explains why a list is smaller than the traffic suggests: it counts only people whose activity could be matched to an identifier the DSP can bid on, which excludes browsers that block third-party cookies, users who declined consent and app traffic without an advertising identifier. The same limits apply to a cap, because a cap counts identifiers. The reach guide gives the direction of the error: a missing identifier makes a person look new every time, so the systems that cannot recognise people overstate reach and understate frequency, and the people least recognisable to the system, those who decline consent or use restrictive browsers, are precisely the ones whose frequency nobody is managing. A cap set where the identifier is weakest is a cap in name only.

Fix: read the audience sizes by environment and the consented, cookie-capable share of the plan's traffic, as the audiences guide asks, and accept that real frequency in the remaining environments will run above the setting; weight delivery towards the environments and inventory where an identifier holds for the campaign's purpose, use exclusions where the person can be matched and expect them to fail where they cannot, and read the modelled reach and frequency figures with the conditions the reach guide attaches rather than as counts. The audiences guide notes that Google documents routes that reduce the dependence on cookies and the modelled methods reports use where identifiers are missing; the guide's working rule is to read every audience size as a lower bound on the people the advertiser cares about and an upper bound on the people the DSP can reach.

Verify: frequency read by environment shows the gap between the setting and the experience concentrated where identifiers are missing, and shifting weight away from those environments shortens the tail without the plan's reach falling below the figure the calculator predicted.

Prevent: treat identifier coverage as one of the six inputs the reach guide lists for planning a cap, state the assumption in the plan, and re-read it whenever consent rates or browser behaviour change.

A small audience against a large budget

The reach guide's planning section lists the audience size against the budget among the inputs that decide a cap, and says what happens when they are mismatched: a small audience with a large budget will hit any cap quickly, after which the money either goes unspent or buys exposures above the cap through identifiers the cap cannot see. The awareness setup owns the consequence in the console: a plan that caps per line item, bids on cheap served impressions and paces as soon as possible repeats the budget onto the audience available in the first days and leaves later weeks to repeat it again, and the bidding guide's under-delivery table lists a frequency cap reached for most matched users among the reasons a line item shows bid requests but few bids. The fatigue guide describes the same arithmetic on the social side, where a remarketing audience of a few thousand people meets a budget that reaches all of them in a day and then repeats.

Fix: divide the budget by the planned price per thousand to get the impressions the flight buys, enter them with the audience size into the reach and frequency calculator and read the average the plan implies; if it sits far above the intended frequency, the choices are to size the budget to the audience, to widen the audience or add fresh lists so the DSP has people left to reach, or to accept under-delivery as the cap's verdict, and the reach guide asks for that choice to be made in advance, because the DSP will move spend to new identifiers and pacing will slow if there are none left. Pace evenly across the flight, as the awareness setup recommends, so reach accumulates rather than repeating.

Verify: the line item's bid request and bid figures stop collapsing at the cap, which is also one of the causes the line item not spending diagnosis separates, the reach report shows reach growing week by week, and the share of impressions above the intended frequency falls to the level the plan accepted.

Prevent: run the calculator before every flight with the audience size and the impressions the budget buys, and record the implied frequency beside the budget, so a budget increase against an unchanged audience is read as a frequency decision rather than a reach one, and move money to a channel that still has people to reach once the audience is saturated.

Prevention: a campaign-level ceiling, one cap per plan and a monthly read of the share served above it

Each cause above was a gap between what a cap can count and what a person experiences, and the routine that closes the gap has three parts. The first is a campaign-level ceiling set before any line item exists. The awareness setup puts it first among the frequency decisions, the bidding guide confirms that caps at every level apply and stack, and the pre-flight check confirms the ceiling beside pacing and bid strategy so a mid-flight addition cannot run uncapped. Tighter caps lower down are added only where a tactic needs them, and the reason is written into the plan.

The second is one cap per plan rather than one per system. The plan records the intended frequency per person per window, the systems that serve the same people, the cap each holds and the identifier each counts, and the overlap assumption used to read reach across them. Where a control exists on a social or video platform it is set there; where it does not, the fatigue guide's indirect controls, audience size, exclusions, rotation and budget, do the work; and the ad server's ad-level settings bound whatever passes through its tags. The reach guide's five routes to a better combined view, buying the walled garden through the DSP where possible, clean rooms, panel-based partners, a modelled overlap and an incrementality test, are each an estimate with stated assumptions, and the honest plan names which one it uses. The level of the ceiling itself is not a figure to inherit from last year; the frequency cap test runs a capped cell against an uncapped one on lift per unit of spend, with reach, cost and the uncapped cell's exposure above the cap as guardrails, and the media planning framework records the result as the plan's assumption.

The third is a monthly read of the share of impressions served above the intended frequency, by campaign and by environment, from the DSP's reach report and from each platform's own figures. That share is the measure of whether the cap is working; the average is not. Beside it sit the audience sizes by environment and the implied frequency from the calculator, so that a budget change, a shrinking list or a new buy on a new platform shows up as a predicted rise in the tail before the complaints arrive. When several of these habits are missing at once, the programmatic measurement section orders the delivery questions, viewability first and reach and frequency second, and the low viewability diagnosis handles the question that usually precedes this one, since a campaign that has just fixed its viewable rate often hears next that the same people are seeing the now-viewable ad far too often. The programmatic troubleshooting hub lists the other symptom pages for this root.

A garden furniture maker finds where the extra exposures came from (illustrative)

Illustrative example — not a real result

Vorsinghale Garden Furniture

Vorsinghale Garden Furniture, an invented maker with 4 showrooms and an online store, runs a 10-week spring campaign in DV360 with a cap of 3 impressions per person per day on each of its display line items, and receives 31 complaints in a fortnight from customers who say the ad is everywhere. The campaign reach report shows 640,000 people at an average frequency of 2.6 per day, comfortably under the cap.

The planner reads the distribution instead of the average: 8% of the people reached account for 41% of the impressions, at a modelled frequency above 9 per day. The campaign has no cap of its own. Under it, three display line items each target the same remarketing list of recent site visitors, one for a sale message, one for a delivery message and one a paused test that a colleague unpaused in week 3, so a visitor the DSP recognised could be served 9 impressions a day inside the settings. Separately, a 6-week video campaign on a social platform, bought by the agency's social team against the same visitor list with no frequency control, reports its own average of 5.4 per week, and none of its exposures appears in the DSP's figures at all.

The maker sets a campaign-level ceiling of 4 impressions per person per day, consolidates the three line items into one with a sequenced creative rotation, lowers the social campaign's control to 2 per week inside that platform by moving it to a reach-optimised ad set, and records an overlap assumption of 60% between the two audiences. From week 5 the share of DSP impressions above the intended frequency falls from 41% to 7%, the campaign's reach rises to 910,000 by the end of the flight, and the monthly report carries the share above the ceiling by environment, with the next flight's cap level handed to a capped-against-uncapped test.

Common mistakes

  • Reading the average instead of the distribution. An average near the cap hides the tail the cap was meant to prevent.
  • Treating a cap as a promise to the person. It is a ceiling per identifier per window inside one system.
  • Caps only on line items. Each tactic serves to its own cap and the person sees all of them.
  • Setting the cap in one system and forgetting the others. The DSP, the ad server and the walled gardens each enforce a different ceiling on different identifiers.
  • Adding platform reach figures and dividing by them. Walled gardens cannot be deduplicated from outside; state the overlap assumption instead.
  • Ignoring consent and identifier coverage. The people the system cannot recognise are the ones whose frequency nobody is managing, and they are not a random sample.
  • Pointing a large budget at a small list and lowering the cap. The money goes unspent or finds identifiers the cap cannot see; size the budget to the audience.
  • Inheriting last year's cap. The creative, the flight and the audience changed; let a test re-derive it.

Frequently asked questions

The DSP shows average frequency under the cap. How can people be seeing the ad so often?

Because the average is calculated over the identifiers the DSP can recognise, and a person is usually several of them: one per browser, one per device, and none at all where consent was declined or the browser blocks the cookie. The cap is a ceiling per identifier per window, so each of a person's identifiers can be served up to the cap and the person experiences the sum. Read the frequency distribution rather than the average, because an average near the cap can hide a long tail far above it, and add every buy outside the DSP, which the DSP never counts at all.

Should I just lower the cap until the complaints stop?

Not as a first move. Lowering a cap inside one system does nothing about exposures from sibling line items with their own caps, from a social or video campaign bought elsewhere, or from identifiers the cap cannot see, and it can leave budget unspent or push delivery towards exactly the identifiers that are not being managed. Find which system served the extra exposures first, set the ceiling at the level that bounds all of them, and let a capped-against-uncapped test decide what the right level is rather than guessing under pressure.

Where should the cap live when a plan has several insertion orders and line items?

At the campaign, as the outer ceiling for the whole plan, with tighter caps lower down only where a tactic needs them. Caps at campaign, insertion order and line item level all apply and stack, so a campaign cap bounds every object beneath it, while caps set only on line items let each tactic serve to its own limit and the same person collects exposures from all of them. Write the ceiling into the plan beside the reach it is meant to protect, and confirm it in the pre-flight check so a new line item cannot quietly run uncapped.

Terms used on this page

Tools to try

Frameworks

Where this page is used

Sources

  1. Display & Video 360 Help — Google
  2. Campaign Manager 360 Help — Google

Related