Monitor your first website free - no card needed. Explore SENRIKO

Free Conversion Tracking Checker

Is your conversion tracking actually recording anything?

Check whether Google Analytics 4 (GA4), Google Tag Manager (GTM), Google Ads conversion tracking and the Meta (Facebook) Pixel are present on any public page.

Paste a URL and SENRIKO scans the page for visible tracking tags, their IDs, conversion signals, forms and cookie consent signals. No signup or access to your Google or Meta accounts is required.

One request to one page. Nothing is stored: not the address, not the result.

example.com/contactExample result
  • Google Tag ManagerDetectedGTM-XXXXXXX
  • Google Analytics 4DetectedG-XXXXXXXXXX
  • Google Ads tagDetectedAW-123456789
  • A Google Ads conversion on this pageNot observed
  • Meta PixelLikely configured
  • Cookie consentLikely configured

The Google Ads tag is here, but no conversion fires from the page itself. Only a real form submission can tell a GTM setup from a broken one.

WHAT ONE SCAN LOOKS FOR

Check website tracking tags in one scan

One scan reads the page the way a visitor’s browser receives it and looks for the tags most conversions depend on: GA4, Google Tag Manager, Google Ads and the Meta Pixel. Where an ID is readable, we show it, so you can compare it with the one you meant to install.

  • G-XXXXXXXXXX

    Google Analytics 4

    Whether GA4 is installed, and its measurement ID when the markup shows it.

    Run the GA4 checker
  • GTM-XXXXXXX

    Google Tag Manager

    Whether a GTM container loads, and which one. A container can carry GA4 and Google Ads inside it.

    Run the Google Tag Manager checker
  • AW-XXXXXXXXX

    Google Ads tag

    Whether the Google Ads tag is on the page, with its conversion ID when it can be read.

  • 'event', 'conversion'

    Google Ads conversion signals

    A conversion fired from the page itself. The tag can be loaded while no conversion is set up to fire here, and that gap is where money is lost.

    Run the Google Ads conversion tracking checker
  • fbq('init', …)

    Meta Pixel (Facebook Pixel)

    Whether the Meta Pixel is installed, and its pixel ID when it is written into the page.

    Run the Meta Pixel checker
  • <form>

    Forms

    The forms on the page. Whether submitting one records a conversion is out of reach of a passive scan, and the result says so.

  • gtag('consent', …)

    Cookie consent

    Whether a consent banner is present, and whether Google Consent Mode is set up behind it. A tag waiting for consent is not a missing tag.

    Run the Google Consent Mode v2 checker
  • HTTP 200

    The page and bot protection

    Whether the address answered, and whether a CAPTCHA wall answered instead of your page. A checker that hit a wall and reported “no tags” would be wrong about your site.

This scan reads the page before anybody answers the cookie banner. To see what the same tags do after a visitor accepts or rejects, run the cookie consent checker: it tests tracking before and after consent in three clean browser sessions.

HOW TO READ THE RESULT

What does the conversion tracking checker tell you?

Whether each tag is on the page, and how sure we are. A tracking script on the page is not proof that a conversion is recorded: it can be installed and still send nothing when a visitor converts. So every observation gets one of four words, each claiming exactly as much as we saw.

Detected
We saw it, with its ID. That is the strongest thing a passive scan can say, and it still does not prove that a conversion fires.
Likely configured
The tag’s shape is there, but its ID could not be read from the markup, which is common when a tag manager assembles things at runtime. It is almost certainly present, but not verified.
Not observed
Not on this page as it was served to us. This is a statement about one page and one request, not a verdict that the tag does not exist. The next section shows the ordinary reasons a working tag reads this way.
Unable to verify
Something kept us from an honest look: bot protection, a page that would not load, markup we could not read. We would rather say so than guess.
BEFORE YOU CALL IT BROKEN

“Not observed” is not “broken”

The scan reads the HTML your server sends, once, before anything on the page runs. Everything a site does after that moment is out of its sight, and that is where most working tags live.

  1. Read by this scan

    The page arrives

    Tags written into the page, with their IDs. If a tag should be here and is not, this is where it shows.

  2. After our read

    Scripts run

    A tag manager injects GA4 or the Ads tag, and some tags load late, after a scroll or a delay. We may see the GTM container and not what it carries.

  3. After our read

    The visitor answers the banner

    A correctly set up banner holds tags back until the visitor agrees. Our request never answers, so we see the held-back state.

    Check whether your cookie banner blocks tracking
  4. After our read

    The visitor converts

    Form submissions, sign-ups, checkouts and purchases fire their conversion events only when they happen, often on a thank-you page rather than the one you scanned.

  5. After our read

    Your server reports

    Server-side tagging and Meta’s Conversions API send events from your backend. By design, no page and no browser can see them.

If none of these fits and the tag should be right here, on this page, then “not observed” deserves your attention: the tag may really be missing, and that is the case this tool is for.

FAQ

How to check GA4, GTM, Google Ads and Meta Pixel

How do I check if Google Analytics 4 is installed on a website?
Paste the page’s address into the checker. It looks for GA4 in the page’s markup and shows the measurement ID (G-…) when it can read it. If the result is “Likely configured” or “Not observed”, GA4 may still be running: it is often loaded through Google Tag Manager or added by a script after the page loads, and a single passive scan does not see what those add later. To open the page in a real browser and see what GA4 sends, use the GA4 checker.
How do I check if Google Tag Manager is installed?
Run the checker on any page of the site. It looks for the GTM container snippet and shows the container ID (GTM-…) when it is written into the page. A readable ID lets you confirm it is your container and not an old one left behind by a previous agency or plugin. The scan sees the container itself, not every tag configured inside it. To see whether the container loads and what its published version sets up, use the Google Tag Manager checker.
How do I check Google Ads conversion tracking?
Check the pages where the conversion happens, not only the homepage: the landing page your ads point to, the page with the form, and the thank-you page. On each, the checker looks for the Google Ads tag with its ID (AW-…) and for a conversion fired from the page itself. Conversions fired from Google Tag Manager or from your server will not show here, so “Not observed” on the conversion is a reason to look closer, not proof that it is broken. To see which conversions the page and its GTM container set up, use the Google Ads conversion tracking checker.
How do I check if a Meta Pixel or Facebook Pixel is installed?
The checker looks for the Meta Pixel code, which used to be called the Facebook Pixel, and shows the pixel ID when it is written into the page. If the pixel is loaded through Google Tag Manager, or your events go through Meta’s Conversions API from your server, the scan may not see it. To see whether Meta knows the pixel ID and which events a real browser sends, use the Meta Pixel checker.
Can this checker prove that a conversion actually fires?
No. A passive scan reads the page without acting on it, and many conversion events only appear after something happens: a form is submitted, a checkout completes, somebody signs up or buys. Server-side tracking can also be invisible to any browser or page scan. Proving that a conversion fires means making one, which is what SENRIKO’s monitored checks do on a site whose owner has verified it.
Is it safe to point this at my site?
It is one GET request with our named user agent, the same weight as one visitor opening one page. It submits nothing and stores nothing: not the address, not the result. Ten checks an hour per visitor, so it cannot be used to hammer anybody.
Everything says “not observed”, but my ads work. Which of us is wrong?
Possibly neither. The section above shows where a working tag hides from a passive read, and server-side tagging alone explains most of these cases. If your reports show conversions, trust your reports, and use this page to learn where the recording happens.
Why does it not ask for my Google or Meta account?
Because it only reads what any visitor’s browser is already given. Anything deeper, such as proving that a conversion actually records, requires acting on your site, and acting on a site requires proof that it is yours. That is the real check, and the only thing an account is for.
What would the real check add?
The submit. A monitored check fills your form with a clearly marked test identity, sends it, and watches whether the conversion signal actually fires. Then it repeats this on a schedule, so you hear about it on the day the signal stops firing.

Articles on this check

All articles
THE HONEST PART

What this cannot tell you

  • 01

    It only reads the page. It never fills a form, never clicks, never answers a consent banner and sends nothing to your analytics, so your reports see no trace of it. Anything that appears only after someone interacts with the page stays out of its reach.

  • 02

    It reads one page, once. A tag that loads for half your visitors, only after the banner, or only on mobile can read differently on another day. Treat the result as a photograph, not a diagnosis.

  • 03

    Dynamically loaded tags and server-side events may not be visible to it. “Not observed” does not always mean your tracking is broken.

  • 04

    Whether a form submission records a conversion is only answerable by making one: filling the form in, sending it and watching for the signal that should follow. That means acting on your site, so it needs proof the domain is yours.

The real check, in the cabinet: every step from the open page to your CRM, proved one by one or marked with what it still needs.

Verify my domain and run a real checkCheck another page