META·Meta Pixel·warning

Meta Zero Volume Active Events

Your Meta Pixel has events with status Active but zero recorded volume across the audit window. Active means Meta is listening; zero volume means nothing is arriving. The event exists in Events Manager only on paper, and any campaign optimizing toward it has no signal to learn from.

CL
By Christopher LandaverdeCreator of AdLint · ad-tech tracking specialistUpdated

Why It Matters

An active event with no volume is one of three things. First, the trigger is broken: the tag is configured against a CSS selector, a route, or a data layer key that no longer exists after a site change. The pixel call never executes. Second, the event is gated behind a consent state that never resolves to granted, so the request is built but never sent. Third, the event name on the pixel side does not match what Meta expects (subtle casing or spacing differences), so it routes somewhere else and the active row stays empty. The consequence depends on which event is empty. An empty Purchase event is the most damaging case because every revenue-optimized campaign on the account is silently broken. An empty AddToCart kills abandoned-cart audiences and Advantage+ Catalog Ads retargeting. An empty Lead event makes lead-gen optimization impossible. The quiet part is that the pixel still passes a surface health check. Events Manager shows the event as configured. Pixel Helper does not complain about its absence. Only the Overview tab's 28-day volume column gives it away, and only if someone looks.

How To Fix It

  1. For each zero-volume event AdLint flagged, walk the user action that should trigger it in a real browser with Meta Pixel Helper open. If Pixel Helper does not show the event, the trigger is broken.
  2. Inspect the tag configuration: GTM trigger conditions, CSS selectors, data layer keys, route patterns. Confirm each still matches the current site.
  3. Walk the consent path. Deny consent, then grant consent, then refresh. The event should fire after grant. If it never fires, the consent gating is misconfigured.
  4. Check the exact event name on the pixel side against Meta's standard events reference. `Purchase` not `purchase`. `AddToCart` not `Add_To_Cart`.
  5. After fixing, wait 24 hours and confirm volume appears in Events Manager Overview. If a campaign was optimizing against the empty event, expect a learning reset.

Example

Configuration
Events Manager > Overview > 28-day volume column should show non-zero numbers for every Active event.
For Your Client Report

This Meta Pixel has one or more events with status Active but zero recorded volume across the audit window. Per Meta's pixel documentation, an active event with no volume is almost always one of three failures: a broken trigger (CSS selector, data layer key, or route pattern that no longer matches the live site), a consent gate that never resolves to granted, or an event name mismatch where the pixel uses different casing than Meta's canonical standard events. The downstream damage scales by event: an empty Purchase silently breaks revenue-optimized campaigns, an empty AddToCart kills abandoned-cart audiences and Advantage+ Catalog Ads retargeting, an empty Lead disables lead-gen optimization. The pixel passes surface health checks while the underlying signal is absent. Fix: walk each zero-volume event in Meta Pixel Helper, repair the trigger or consent path, verify exact-cased standard event names, then confirm 24 hours of recovered volume in Events Manager Overview before resuming optimized delivery. 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