How to Check if Google Analytics is Installed

01  Why This Check Matters

Before you can trust any report, any conversion figure, or any attribution model, you need to confirm that your GA4 tracking code is actually installed — and that it is installed correctly. This sounds obvious, but analytics audits consistently reveal that a large proportion of websites contain at least one tracking configuration issue.

The most damaging scenario is not a missing tag. It is a duplicate tag — one that inflates every metric silently while dashboards continue to populate with numbers that look plausible. Teams make budget decisions on that data. The errors compound.

The fastest first check for sites using a direct gtag.js installation. It will not reveal tags deployed through Google Tag Manager, but it immediately surfaces hardcoded snippets and — critically — duplicate Measurement IDs.

How to do it

1. Open the page source — In Chrome or Firefox, press Ctrl+U (Windows) or Cmd+U (Mac). The raw HTML of the page opens in a new tab.
2. Search for your Measurement ID — Press Ctrl+F and search for ‘G-‘ (the prefix of every GA4 Measurement ID). You can also search for ‘gtag/js’ or ‘googletagmanager.com/gtm.js’.
3. Interpret the result — One match is correct. Zero matches means either GTM is being used or GA4 is not installed. Two or more matches of the same ID is a duplicate — fix immediately.

What a correct direct installation looks like

<script async src="https://www.googletagmanager.com/gtag/js?id=G-XXXXXXXXXX"></script>
<script>
  window.dataLayer = window.dataLayer || [];
  function gtag(){dataLayer.push(arguments);}
  gtag('js', new Date());
  gtag('config', 'G-XXXXXXXXXX');
</script>

When page source shows nothing

If you find no ‘G-‘ reference, it does not necessarily mean GA4 is absent. Google Tag Manager deploys tags through JavaScript at runtime — they do not appear in the static HTML source. Search instead for ‘GTM-‘ or ‘googletagmanager.com/gtm.js’. If GTM is present, move to the network-level methods below.

This is the most reliable method and the one professional analytics auditors use as standard. It works regardless of whether GA4 is installed directly or through GTM, and it reveals duplicate tracking that the page source check cannot.

Step-by-step

1. Open DevTools — Press F12 or Cmd+Option+I. Click the Network tab.
2. Filter by ‘collect’ — In the filter bar, type ‘collect’. This surfaces only GA4 data collection requests, filtering out all other network activity.
3. Reload the page — Hard reload with Ctrl+Shift+R to clear cache and trigger a fresh page load.
4. Inspect the request — Look for a request to https://www.google-analytics.com/g/collect. Click it and examine the Payload tab to confirm your Measurement ID and the event type.

Reading the request payload

// GA4 data collection endpoint
https://www.google-analytics.com/g/collect?v=2&tid=G-XXXXXXXXXX

// Key parameters to verify:
v=2               // GA4 protocol version (must be 2, not 1)
tid=G-XXXXXXXXXX  // Measurement ID — confirm this matches your property
en=page_view      // Event name — should be page_view on load
dl=https://...    // Document location (full URL)
dt=Page+Title     // Document title
gcd=11l3l3...     // Consent Mode state string

Reading the Consent Mode GCD parameter

While in the Network tab, check the gcd= parameter. This tells you whether Consent Mode is active and what state it is in:

If gcd= is absent entirely, Consent Mode is not implemented on this site.

The Realtime report in GA4 confirms that data is arriving at the property — not just that a request was sent from the browser. A network request can be sent but rejected if the Measurement ID is wrong, the property is disabled, or the data stream is misconfigured.

How to use it

1. Open GA4 and navigate to Realtime — In Google Analytics, go to Reports > Realtime. This shows live activity in the last 30 minutes.
2. Load a page on your site — Open your website in a separate tab or window. Navigate through a few pages to generate events.
3. Confirm data arrives — Within 5–10 seconds, you should see your session appear. The Event Count panel should show page_view events incrementing.

DebugView is a real-time event stream from a single device that shows every event, every parameter, and the exact sequence in which they fire. It is the most granular verification tool available and the one to use when checking custom events, parameter values, and ecommerce data.

How to enable it

• Via Google Tag Assistant: Install the Chrome extension and click ‘Connect’. This automatically enables debug mode for your browser session without any code changes.
• Via GTM Preview Mode: Launch GTM Preview Mode on your site. This activates debug mode automatically and sessions will appear in DebugView.
• Via URL Parameter: Append ?gtm_debug=x to your URL. Works if GTM is installed, even without the browser extension.
• Via GA4 Admin: Navigate to Admin > DebugView. Once a debug session is active in the browser, events stream in live under your device.

What to look for in DebugView

A clean, correctly installed GA4 property on a standard page load shows exactly this event sequence: one page_view, followed by a user_engagement event as the user interacts. Every custom event you trigger — a button click, form submission, product view — should appear within 2–3 seconds.

Common problems visible in DebugView: duplicate page_view events firing on a single load, events missing expected parameters (appearing with (not set) values), and events firing on page load when they should only fire on interaction.

Google Tag Assistant records an entire user session and produces a tag-by-tag report of what fired, what did not, and what errors were detected. It is particularly useful for auditing checkout flows, multi-step forms, and ecommerce funnels.

1. Install the Chrome extension — Search ‘Google Tag Assistant’ in the Chrome Web Store and install it.
2. Start recording — Navigate to your website. Click the Tag Assistant icon and select Record. A new browser window opens connected to your site.
3. Complete the user journey — Navigate through the pages and interactions you want to audit — add a product to cart, complete a form, move through the checkout.
4. Review the report — End the recording and review which tags fired on each page. GA4 tags should fire once per page. Red or orange indicators signal errors.

Duplicate tracking is the single most common GA4 implementation error. It inflates page views, sessions, and events — making all downstream analysis unreliable — while producing no obvious error messages. The numbers still look reasonable, which is what makes it so dangerous.

The most common causes

What duplication does to your data

Run through this checklist after any new GA4 installation, after a website redesign, after adding or changing a CMS plugin, or when you notice unexpected data anomalies.