Meta Event Volume Concentration
Your Meta Pixel has one event (other than PageView) carrying more than 95 percent of all reported volume. That pattern usually means the rest of the funnel is missing, mis-named, or mis-fired. A healthy pixel shows volume tapering from PageView through ViewContent, AddToCart, InitiateCheckout, and Purchase, not a single spike with nothing else around it.
Why It Matters
Meta's optimizer reads the relative shape of your event volume as a health signal. When ViewContent, AddToCart, and InitiateCheckout are absent or near zero, but a single mid-funnel event is responsible for almost everything, two things tend to be true. First, the dominant event is probably mis-mapped. A common case: AddToCart is wired to every product page view instead of the actual cart-add click, so it counts as both browsing and intent. The volume looks great. The signal is garbage. Campaigns optimized against it learn to chase product page traffic, not real cart adds. Second, the surrounding events probably exist on the site but are not reaching Meta. A consent gate, a CSP rule, or a broken trigger lets PageView through but blocks the rest. The pixel grading panel in Events Manager will not flag this directly because each individual event passes its own health check; only the ratio gives it away. A single dominant event also distorts lookalike seed quality. Meta uses the event's audience as the source. If that audience is bloated with non-intent traffic, the lookalike inherits the noise.
How To Fix It
- Identify which event is dominating. AdLint reports the name and percentage.
- Pull the actual trigger configuration for that event in GTM, the tag manager, or the source code. Walk a real session and confirm the event only fires on its intended action. If it fires on every page or on every click, fix the trigger.
- Check the events that should sit around it in the funnel. ViewContent should be roughly 1x to 3x the AddToCart volume. AddToCart should be roughly 3x to 10x the Purchase volume. If those events are missing entirely, see meta-ecommerce-funnel. If they exist but are starved, investigate consent gating and CSP.
- In Events Manager, open the Overview tab and look at the event ratio over the last 28 days. The shape should taper, not spike.
- Once the ratios look right, re-evaluate any campaigns built against the dominant event. They may have been optimizing on inflated signal and need a learning reset.
Example
Healthy shape (28 days): PageView 50k -> ViewContent 12k -> AddToCart 1.5k -> InitiateCheckout 600 -> Purchase 220.This Meta Pixel shows one non-PageView event carrying more than 95 percent of total event volume. Per Meta's pixel documentation, a healthy ecommerce pixel produces a funnel-shaped volume distribution from PageView through Purchase; a single spike usually indicates either a mis-mapped trigger (the event firing on a broader action than intended) or that surrounding funnel events are blocked by consent gating, CSP rules, or missing tags. Either pattern degrades optimization signal quality and bloats lookalike seed audiences with non-intent traffic. Fix: verify the dominant event's trigger fires only on its intended user action, restore the surrounding funnel events (ViewContent, AddToCart, InitiateCheckout) where missing, confirm consent paths permit the full pixel, and reassess campaigns that may have been optimizing against the inflated signal. Source: developers.facebook.com/docs/meta-pixel.
Drop this paragraph into your client deliverable. Sources back to the canonical platform documentation linked below.
References
Audit your own files for this check
AdLint runs this check (and 177 others) against your GTM, Google Ads, Meta, TikTok, LinkedIn, Pinterest, Twitter/X, and Snapchat exports. Everything stays in your browser. No uploads, no accounts.
Run a free audit