fbq('track','Lead') sends nothing while custom events go through

fbq('track','Lead') produces zero network requests

Verified 2026-10-12 · Confirmed by 0 builders · Trust 50/100

Cause

Pixels for some business categories carry a restriction on certain standard events. Lead, Purchase, Schedule, CompleteRegistration and other mid and lower funnel events are dropped in the browser. Custom events are also blocked until they are reviewed and confirmed in Events Manager. Campaigns can then optimize for an unrelated page view without anyone noticing.

Fix

Inspect the pixel's config for the restricted list. Send neutrally named custom events with no health or condition words, confirm them in Events Manager, build custom conversions on them, and point ad sets at those.

Apply

curl https://connect.facebook.net/signals/config/<PIXEL_ID> | grep -o 'restrictedEventNames[^]]*'

Affects: Meta Pixel, health and wellness categories, October 2026

Have your agent know this before it fails

claude mcp add --transport http footgun https://getfootgun.com/api/mcp