Twitter/X Zero Volume Active Events
One or more X Pixel event tags on this account are marked active in Events Manager but have recorded zero events over the reporting window. Either the tag is wired but the trigger never fires on the site, the tag is being blocked, the tag is firing with a malformed event ID, or the underlying user activity does not actually exist. None of these are good states for a tag that campaigns may be optimising against.
Why It Matters
An active event in Events Manager with zero volume is a measurement liability. If a campaign is optimising against that event, the bidder has no signal and either fails to spend or spends without a meaningful target. If no campaign is optimising against it yet but one is planned, launch day starts from a cold pixel with no learnings. The usual root causes: 1. Tag is wired but the trigger condition never matches. A Purchase tag attached to a thank-you page selector that changed after a redesign. A SignUp tag tied to a form submit listener that the new framework no longer dispatches. 2. Tag is firing but the event ID is malformed, so X drops the hit. This is the failure mode the `twitter-event-id-format` check catches separately, and the symptom in Events Manager is identical: zero volume. 3. Request is being blocked. Tracking protection in the user's browser, a CSP that does not allow the X analytics endpoint, or a network-level block at the visitor side. 4. The underlying business activity does not exist. The site does not currently have any of the configured action happening, for example a CheckoutInitiated event on a site that has no checkout flow in production yet. Distinguishing between these requires checking the tag on the site, the outgoing request, and the business funnel separately.
How To Fix It
- For each zero-volume active event, fire the user action on the site in a clean browser and watch the Network tab for the outgoing request to the X analytics endpoint.
- If no request fires, the tag is not triggering. Re-validate the trigger condition (selector, event listener, Data Layer push) against the current site.
- If the request fires but Events Manager still shows zero, inspect the event ID in the payload and confirm it matches the `tw-XXXXX-XXXXX` ID registered for that event.
- If the request and ID are both correct, check for tracking protection or CSP blocks by repeating the test in a different browser without extensions.
- If the tag is genuinely correct and there is simply no traffic doing that action, either pause the event to keep Events Manager clean or accept the zero state until the funnel produces activity.
Example
Active events with zero volume over last 7 days:
Purchase (tw-o1234-abcde)
AddToCart (tw-o5678-fghij)
Real orders in commerce platform same period: 220
Likely cause: thank-you page selector changed in last release; tag trigger no longer matches.Your X Pixel has active event tags reporting zero volume over the audit window. Per X Ads Help Center documentation on the X Pixel and conversion tracking for websites, an active event in Events Manager with no recorded volume indicates one of four failure modes: the tag trigger never matches because of a site change, the tag fires but the event ID does not match a registered `tw-XXXXX-XXXXX` tag, the outbound request is blocked by browser tracking protection or CSP, or the underlying business activity does not currently exist on the site. Any of these leaves campaigns that optimise against the event without a signal, and a planned campaign launch against a cold pixel will start with no learnings. Fix: replay the action on the site in a clean browser, inspect the outbound request for both presence and a correct event ID, repeat in a CSP- and extension-free environment, and either repair the trigger, correct the ID, or pause the event if no real activity exists yet. Source: business.twitter.com/en/help/campaign-measurement-and-analytics/twitter-pixel.html.
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