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

GA4 checker

Free GA4 Checker

Check whether Google Analytics 4 is installed on a page, which measurement IDs it uses and whether a real visit sends GA4 any data.

Paste a page address. We open it once in a real browser and read its G- measurement IDs from the HTML, from the published GTM container and from the requests the browser sends.

No signup and no access to your Google account. The result shows what was found, where it was found and what a browser check cannot see.

We open the page once in a real browser from Germany. The site's analytics may count that visit as one page view. We click nothing and send nothing.

example.com/pricingExample
  • GA4 streamDetectedG-XXXXXXXXXX
  • page_view sentDetectedpage_view
  • generate_lead set upLikely configuredgenerate_lead
  • Server-side eventsUnable to verify

The stream sent a page_view in the visit. generate_lead is set up in the container and waits for a form.

What it looks for

What the GA4 checker reads on a page

A GA4 tag can be written in the HTML, set up inside a Google Tag Manager container, or only appear once the browser runs the page. The check reads all three and shows the evidence behind every finding.

  • gtag/js?id=G-XXXXXXXXXX

    The Google tag script

    A script loading gtag.js with a G- ID. It shows the page asks for that stream.

  • gtag('config', 'G-…')

    A config call

    gtag('config', 'G-…') in the page's code, with settings such as send_page_view.

  • GTM-XXXXXXX

    The published GTM container

    We read the container Google serves for each GTM ID and list the GA4 streams and events it sets up.

  • /g/collect?tid=G-…

    A hit sent to GA4

    A request to /g/collect with the stream's ID. It shows the browser sent data in this visit.

  • en=page_view

    Event names

    Which events the browser sent, such as page_view, and which the container sets up for later.

  • server_container_url

    A server container

    A server_container_url means some data goes through the site's own server, which a browser cannot see.

Reading the answer

Four words, and where each one came from

Every line of the result carries one of four words, and under it the evidence at its own level. A tag seen sending data is a stronger fact than an ID seen in the HTML, and the result never passes the weaker one off as the stronger.

Detected
The browser saw it load or send a request in this visit.
Likely configured
It is in the page's code or in the published container, and nothing ran it while we watched.
Not observed
We did not see it in this visit. That is not the same as broken: it may wait for consent, a click or a server.
Unable to verify
We could not look: a bot check, an error or a page that did not open.

The levels of evidence, weakest first

  1. In the HTMLThe ID is written somewhere in the HTML the server sent.
  2. In the containerThe published GTM container, as Google serves it to every visitor, sets it up.
  3. In the code, not runThe page's code would send it, for example in a click handler, and nothing ran that code.
  4. LoadedIts script or container loaded in a real browser.
  5. Request sentThe browser sent a request with its ID or event. That shows the request left the page, not that the platform accepted it.
Troubleshooting

Why GA4 is not tracking: six common causes

When Google Analytics 4 shows no data, or less than it should, the cause is usually on this list. Each card says what the checker shows when it happens.

  • 01

    Data goes to the wrong measurement ID

    A G- ID copied from an old property or a test stream sends hits where nobody looks. The result lists every measurement ID on the page, so you can compare them with the web stream in your property.

  • 02

    The GA4 tag is in an unpublished GTM change

    A tag added in a Tag Manager workspace does nothing until someone publishes the container. The checker reads the published version, which is what visitors get, so a GA4 tag missing there is missing for them too.

  • 03

    Analytics waits for the cookie banner

    On sites with a consent banner, GA4 often stays silent until a visitor accepts. This check leaves the banner alone, so such a tag reads as not observed. The Cookie Consent Checker opens the page again after Accept all.

  • 04

    No page_view on load

    A config with send_page_view set to false leaves the first load without a page_view, and single page apps often send page views only on route changes. The result flags send_page_view: false when the code has it.

  • 05

    Every event is counted twice

    The same G- ID loaded by a gtag.js snippet in the theme and again by a GTM tag sends each event twice. The result shows every place an ID is set up, so a double install is easy to see.

  • 06

    Hits go through a server container

    After a move to server-side tagging, GA4 hits go to the site's own domain first and on to Google from there. The checker recognises a configured server container and says that part is out of a browser's sight.

By hand

How to check if GA4 is installed, step by step

You can check GA4 by hand in any desktop browser. The checker above runs the first three steps in one visit and reads the GTM container as well. The last step needs your GA4 property.

  1. Step 1

    Search the page source

    Open the page and press Ctrl+U (Option+Cmd+U on a Mac), then search for G- and GTM-. You find IDs written into the HTML and miss the ones that live only in a Tag Manager container.

    G-XXXXXXXXXX
  2. Step 2

    Watch the Network tab

    Open DevTools, choose Network, type collect into the filter and reload. A request to /g/collect with tid=G-… means the browser sent GA4 a hit, and en= names the event.

    /g/collect?en=page_view
  3. Step 3

    Answer the cookie banner

    If no hit shows up, accept the banner and reload. Hits that appear only now were held until consent, which is usually what the site intends.

    gtag('consent', 'update', …)
  4. Step 4

    Confirm it in GA4

    Open the Realtime report in your property, or DebugView if your browser runs in debug mode. Only the property can show that GA4 received the data and kept it.

    DebugView
Compared

GA4 checker, Tag Assistant or DebugView: when to use which

The three answer different questions. The checker needs nothing but a link; the other two need your own browser session or access to the property.

Needs a page address

This GA4 checker

Opens the page in a clean browser from Germany, with no cookies, extensions or login. It reads the HTML, the published GTM container and the requests, and gives you a result link to send to a developer. It sees one page load and clicks nothing.

Needs your own browser

Google Tag Assistant

You connect it to the site at tagassistant.google.com and click through the pages yourself. It lists the Google tags and events on each page, with the data layer and the consent state, and with access to the container it can preview changes before they are published.

Needs access to the property

GA4 Realtime and DebugView

Reports inside Google Analytics. They show what the property received, which no outside tool can, and they cannot show a page where the tag never loaded.

Questions

GA4 checker: common questions

How do I check if GA4 is installed on a website?
Paste the page address above. The result lists every G- measurement ID we found, whether it was in the HTML, in the GTM container or in a request the browser sent, and says which of those this visit confirmed.
The ID is there but no GA4 request was seen. Is it broken?
Not necessarily. Common reasons are a consent banner that holds analytics until someone accepts, send_page_view set to false, tags that fire on a click or a later page, and data sent from a server. The result names the reasons it can see, and it does not guess the rest.
Where do I find my GA4 measurement ID?
In Google Analytics, open Admin, then Data streams, and choose your web stream. The measurement ID starts with G- and is shown in the stream details. Compare it with the IDs the checker found on the page.
Does a GTM container mean GA4 is installed?
No. A container can hold GA4 or nothing to do with it. We read the published container and list the GA4 streams and events it sets up.
What is a GT- ID?
A Google tag. One Google tag can send to GA4, to Google Ads or to both, so a GT- ID alone does not tell you which GA4 stream is in use. When the tag starts a G- stream in the browser, the result shows that stream.
Does it work when GA4 was added by WordPress, Shopify or Wix?
Yes. It makes no difference what put the tag on the page. The check reads the page as a browser receives it, so a tag added by a plugin, a store integration or a site builder shows up the same way.
Does a request sent mean GA4 recorded the data?
No. We see the request leave the browser. Whether GA4 accepted it, filtered it or counted it as a key event is only visible in your GA4 property.
Can I check GA4 on a website I do not own?
Yes. The checker reads what any visitor's browser receives, so it works on any public page. It shows measurement IDs and event names, never the data in someone's GA4 property.
Is it safe to run this on my site?
It is one visit, like one person opening one page, from a browser that names itself as SENRIKO. It clicks nothing and sends no form. Your analytics may count it as one page view. The result is kept for 24 hours and is not listed anywhere.
The other tools

The other free tools

Check a page in one tool and open the result in another without waiting again. The four tag tools share one visit, and the two consent tools share three.

Limits

What this cannot tell you

  • 01

    One visit to one page. A stream that loads only on some pages, for some visitors or after a delay can read differently on another day.

  • 02

    We do not answer the cookie banner here. Tags held until consent stay silent in this check; the Cookie Consent Checker opens the page three ways to see them.

  • 03

    Data sent from a server, through server-side tagging or the Measurement Protocol, never passes through the browser and is not visible.

  • 04

    A request that left the browser is not proof that GA4 recorded it. Only your GA4 property can show that.

Verify my domain and test a real conversionCheck another page