Fireshift / Guides

Meta Pixel Lead event in GTM: what 344 sites fire it on

By the Fireshift team · Updated 2026-11-07

What do sites fire their Lead event on?

We read every Meta Pixel template tag and every fbq('track', ...) in Custom HTML. 512 of the 898 sites (57.0%) send Meta events we could read beyond PageView, 2,472 in all (1,290 template, 1,182 Custom HTML). 344 of those 512 send at least one Lead-type event: 668 events, 346 of them named Lead.

That is cleaner than Google Ads, where 31.6% of 886 sites fire a conversion on a click (5 Nov study). 281 of the 344 are B2B SaaS. 29 of them send a Lead-type event on a click and 17 on a page load.

Which Meta events count as a lead?

We counted 7 standard events as Lead-type. Meta's own definitions (Meta Pixel reference):

• Lead: "When a sign up is completed." CompleteRegistration: "When a registration form is completed."
• StartTrial, Subscribe, SubmitApplication and Schedule: a trial started, a subscription, an application, a booked appointment.
• Contact: "When a person initiates contact with your business via telephone, SMS, email, chat, etc." A click on a tel: or mailto: link fits that one. A click on "Book a demo" fits none of them.

Is the GTM Form Submission trigger safe?

Only with Check Validation on. Without it the trigger fires even when the submit fails (Tag Manager Help), so a form that rejects a bad email still sends Lead. 42 of the 344 sites use this trigger for a Lead-type event. Many form tools (HubSpot, Typeform, Calendly) push their own success event to the dataLayer. Fire on that instead.

What else do sites send to Meta?

Across all their Meta events, 152 of the 512 sites (29.7%) send one on a click and 207 (40.4%) on a click, a plain page view, a login or every page. Most of those carry custom names: 315 sites (61.5%) send at least one custom event. A custom event on a click is fine for audiences. It becomes a problem when someone builds a custom conversion on it and an ad set optimises for it.

Same trigger, same mistake in Google Ads? Often. 31 of the 37 sites with a Lead-type event on a click also send Google Ads conversions, and 22 of those 31 count a click there too. Fix it once in GTM: click conversions, page-load conversions, and the same check for LinkedIn and Microsoft Ads.

Does the TikTok pixel have the same problem?

Same check, smaller base. 201 counted sites in the study load the TikTok pixel. On 7 Nov 2026 we read their public containers and page HTML for ttq.track(...) calls. 36 of the 201 (17.9%) send an event we could read, 84 events in all, every one in Custom HTML. 14 of those 36 send a lead-type event (CompleteRegistration, SubmitForm or Contact). 4 of the 14 (28.6%) fire it on a click, a page view that is not a thank-you page, or a login. 8 of the 36 (22.2%) have at least one event on a click, a page load or a login.

That is 14 sites, so read it as a pointer, not a rate. 7 of the 14 fire on a dataLayer event, which usually means a form or sign-up that finished. The method is the same as above. Check the same way: click your own button, watch the network tab for analytics.tiktok.com, and look for a conversion event before the form exists. 165 of the 201 sites load the TikTok pixel and show no ttq.track we could read, so their events come from somewhere we can't see from outside.

Will the pixel and Conversions API count one lead twice?

Not if both carry the same ID. Meta drops the copy when the pixel's eventID matches the server's event_id and the event names match, within 48 hours (Meta: deduplicate pixel and server events). Of 273 live Lead-type events sent with the Meta template, 69 (25.3%) set an event ID. Pixel only? You don't need one. Sending leads from your server or CRM too? Every Lead tag needs the same ID as the server event.

How do I check my own setup in 10 minutes?

1. In GTM, list every Meta tag: the Meta Pixel template tags plus a search for fbq in Custom HTML. Write down each event name and its trigger.
2. In DevTools, Network, filter on facebook.com/tr. Click "Book a demo" without sending the form, then load pricing and a blog post. Each request's ev parameter names the event. Any ev=Lead before a form is sent is a false lead.
3. Send a test form with a bad email. If Lead fires on the error, turn on Check Validation or move the tag to the form tool's success event.
4. In Ads Manager, check which event each lead ad set optimises for, and which custom conversions sit on a click or page-view event.

Does the pixel wait for the cookie banner? That is a separate test: Meta Pixel firing before consent.

What can't we see from outside?

• Your Meta account. Which event an ad set optimises for, your custom conversions, and Conversions API events sent from a server. Every number here counts events sent.
• Anything else hidden: 297 of the 809 readable sites load the pixel but send no event we could read beyond PageView. Pixels set up in Meta's own tools outside GTM, server-side tags, containers past the first 6, and Google Ads primary or secondary status for the cross-check above.
• The sample: our 1,727-site study, built from lists, not random.

Published 7 Nov 2026. Data: docs/research/meta-events-2026-11-07.json (tools/research/meta_scan.py, meta_analyze.py); base = the 898 study sites with the Meta Pixel (study scanned 5 Nov 2026, Meta events read 7 Nov). Triggers sorted with engine/score.py, same rules as the Google Ads study. Recheck: tools/research/meta_recheck.py. TikTok section: 201 study sites with the TikTok pixel, read 7 Nov 2026, docs/research/tiktok-events-2026-11-07.json (tools/research/tiktok_scan.py, tiktok_analyze.py, tiktok_recheck.py). Method.

FAQ

Should a Meta Lead event fire on a demo button click?

No. The click comes before the form, so Meta learns from people who never sent it. Fire Lead on the form tool's success event or the thank-you page, and send the click as a custom event if you want it for audiences.

Does the free Fireshift scan check Meta events?

Not the events yet. It reads Google Ads and GA4 from the same public containers, so on 22 of the 31 sites above it shows the Google Ads side of that click.