Yes, frequency capping on X Ads (formerly Twitter Ads) can be unreliable, and what you're seeing is users getting hit with your ad 7–8 times a day despite a cap, which is a known issue among advertisers.
Why Frequency Caps Don’t Always Work on X Ads:
Placement-Level Variation
Frequency caps often apply at the campaign or user level, but X delivers ads across multiple placements—like main feed, replies, quote tweets, profiles, etc. A user might see the same ad in different contexts, and X counts that as separate exposures.
Limited Enforcement Across Devices
If someone is logged in on mobile and desktop, the cap might not sync properly across both. That can lead to more impressions per person than intended.
Campaign Structure Interference
If you're running multiple ad groups or creatives under the same objective, X may serve different variations to the same user. Frequency caps may apply per creative or per ad group—not overall—depending on your setup.
Algorithm Overrides
In some cases, especially during high-budget pushes or under tight targeting conditions, the algorithm may prioritize delivery even if it means exceeding soft frequency guidelines.
What You Can Do:
Check your campaign-level frequency cap settings (not just ad group level).
Consider segmenting audiences more granularly to reduce overlap.
Monitor placements in your reporting. If a lot of impressions are coming from replies or quote tweets, that could be the leak.
If possible, lower daily budgets or add delivery pacing to smooth things out.
Yes, frequency capping on X Ads isn’t as strict or reliable as you'd expect. It’s helpful, but not bulletproof—so it’s smart to monitor actual impression data closely and combine caps with creative rotation and audience segmentation to avoid overexposure.
