Free tool

Facebook Pixel And Google Tag Checker

Paste your page’s source code: the checker finds the Meta Pixel, the Google Tag Manager container and the Google tag, counts how many times each one loads, and checks that Consent Mode sits in the right place.

Google asks you to set the consent default command before any config or event command, and to call config only once per tag. Meta warns that with several pixels initialized on a page, fbq('track') can cause over-firing.

    Google tags

    Meta Pixel

    Consent (Consent Mode)

    Tags deployed through Google Tag Manager do not appear in the source code: the checker sees the container, not what it fires. To check those, use Google Tag Manager’s Preview mode.

    Sources read on November 6, 2026: Meta, Get Started with the Meta Pixel, Google, Set up consent mode and Google, Configure the Google tag.

    Your Tags Are In Place. Are Your Numbers Right?

    A tag on the page does not mean a conversion counted correctly: I check what Google Ads, GA4 and Meta actually receive, and fix the gaps.

    20 minutes · No commitment · 100% confidential

    Step 1 Of 2 · Your Project

    Step 2 Of 2 · Your Details

    Who are these campaigns for? *
    What are you looking for in our collaboration? * You can pick several
    Where do your ad campaigns stand today? *
    When would you ideally like to start? *

    How the checker reads your tags

    Expected order: consent default → gtag.js loader or GTM container → config → events

    The checker looks for the signatures Google and Meta publish: the Google Tag Manager container snippet and its GTM- ID, the gtag.js loader, each config command, Meta’s fbevents.js loader, each fbq('init') and each fbq('track') event. It counts how many times each one appears.

    It then compares their positions. Google asks you to call gtag('consent', 'default', …) before any command that sends data, such as config or event, and Consent Mode v2 expects four parameters: ad_storage, analytics_storage, ad_user_data and ad_personalization.

    Each ID’s prefix tells you what the tag measures: G- for GA4, AW- for Google Ads, DC- for Floodlight, GT- for a Google tag. A UA- ID points to an old Universal Analytics tag.

    What the checker saves you from

    • Conversions counted twice: a container or pixel loaded twice, by the theme and by a plugin for instance, shows up straight away in the count.
    • Consent set too late: if the consent default command comes after the tag, the checker flags it. To see what each visitor choice changes, then try the Consent Mode v2 simulator.
    • An audit in two minutes: before taking over an account, paste the site’s source code to see which tags are in place and which ones cause problems.

    Frequently asked questions

    How do I check that my Facebook Pixel is installed correctly?

    Paste your page’s source code: the checker tells you whether the fbevents.js loader and the pixel initialization are there, with which ID, and which events the code sends. It reads the code, not the actual hits: it does not replace a check in your Meta Events Manager.

    Why can’t the checker see my Google Tag Manager tags?

    Because they are not in the source code: the container loads them afterwards. The checker sees the container and its ID; to check the tags it fires, use Google Tag Manager’s Preview mode.

    Where do I find my page’s source code?

    In Chrome, open your page and press Ctrl+U on Windows or Cmd+Option+U on Mac: the source code opens in a new tab. Select all, copy, and paste it into the checker.

    Is the code I paste sent anywhere?

    No. The analysis runs in your browser: nothing is uploaded or stored.

    Théo Maupilé

    Growth partner

    Positioning, acquisition, innovation: together we build a lasting growth system.

    Théo MaupiléFreelance Paid Media

    Google PartnerSuperMalter

    ◉ Certifications

    Official Google Partner
    & SuperMalter