How to Audit Google Tag Manager and Google Tags on a Website

You can learn a surprising amount about a website’s measurement setup without having access to its Google Tag Manager account. The useful goal is not to copy somebody else’s container. It is to identify which Google tags load, which events are sent, whether consent is working and where duplicate or missing measurements may exist.

This guide shows the current, practical way to audit GTM and Google tags using Tag Assistant and browser developer tools. Use it on sites you own, manage or have permission to test.

What you can and cannot see

A public page can reveal container IDs, Google tag IDs, network requests and data-layer activity that reaches the browser. That is enough to answer questions such as:

• Is Google Tag Manager installed?
• Which GA4, Google Ads or Floodlight destinations receive data?
• Does a page view fire once or several times?
• Which events are sent when a visitor submits a form, watches a video or buys something?
• Are tags blocked before consent and released afterwards?
• Do event parameters contain the values the report needs?

You cannot reconstruct the complete private GTM workspace from a public page. Unpublished changes, permissions, notes and server-side logic are not exposed. The delivered container JavaScript is compiled for execution, not presented as a readable export of every tag, trigger and variable.

Method 1: use Google Tag Assistant

Google Tag Assistant is the best starting point because it identifies Google tags on a page and creates a structured event timeline. Google’s current Tag Assistant documentation describes it as the troubleshooting tool for checking whether Google tags fire correctly and whether the data they send is accurate.

If you have GTM access

1. Open the correct container and workspace in Google Tag Manager.
2. Click Preview.
3. Enter the site URL and connect it to Tag Assistant.
4. Complete the journey you want to test, such as landing page → form → thank-you page.
5. Inspect each event to see which tags fired, which did not fire and the variable values used.

Preview mode is the only reliable way to inspect the container’s internal firing decisions. Google’s preview and debug guide also supports sharing a preview session and previewing an older container version.

If you do not have GTM access

Open Tag Assistant, add the domain and connect to the site. You can still detect Google tags and follow the events sent by the browser, although you will not see the private GTM workspace detail. The Chrome extension is useful for pop-ups, new tabs and tags loaded inside iframes.

Method 2: inspect the Network panel

Browser developer tools show what the page actually requested. In Chrome, open DevTools, choose Network, preserve the log and reload the page. Useful filters include:

Select a request and inspect its query string or payload. For GA4, look for the measurement ID, event name and relevant parameters. A page can contain the right GTM snippet while still sending the wrong event, so the request is stronger evidence than the presence of a script alone.

Method 3: inspect page source and the data layer

Search the rendered source for GTM-, G-, AW- and DC-. This quickly identifies likely containers and destinations, but treat the result as a lead rather than proof. IDs may appear in consent tools, old code comments or scripts that never execute.

The browser console can also show the current dataLayer array on a site that uses it. This is useful for confirming whether ecommerce or lead events are pushed before GTM evaluates them. Be careful with real customer sites: the data layer may contain personal or transaction information that should not be copied into tickets, screenshots or AI tools.

How to find duplicate and missing tracking

Run one controlled journey and record the expected events before testing. For a lead form, that might be one page view, one form-start event and one qualified lead event after a confirmed submission.

1. Clear the Network log and reconnect Tag Assistant.
2. Reload the starting page once.
3. Perform one action at a time.
4. Count matching requests and compare their event IDs, destinations and parameters.
5. Repeat with consent denied, then granted.
6. Test a second page to rule out a template-specific problem.

Two page-view requests can come from a hard-coded Google tag plus GTM, from two GTM containers, or from an automatic page view combined with a manual event. A missing conversion can come from a trigger condition, consent state, iframe, single-page application route change or a form that never reaches a genuine success state.

Consent and ad blockers can change the result

Test in a clean Chrome profile without an ad blocker, then repeat under the conditions real users experience. A consent platform may prevent the initial tag from loading, send consent-mode pings, or release tags only after an update. Tag Assistant may also fail to connect when extensions, redirects or iframe restrictions interfere.

Record the consent state alongside the event evidence. Otherwise a technically correct “nothing fired” result can be mistaken for a broken implementation.

A reusable website tag audit checklist

• Correct GTM and Google tag IDs found
• One intended page view per load
• Required lead or ecommerce events observed
• Event parameters populated with sensible values
• No direct personal data sent to analytics endpoints
• Consent defaults set before measurement runs
• Consent update reflected after the visitor’s choice
• Google Ads and GA4 destinations agree with the account setup
• Cross-domain and iframe journeys tested where relevant
• Evidence captured with timestamps and exact test steps

When a browser audit is not enough

A public audit tells you what reached the browser and the network. It cannot confirm attribution settings, GA4 filters, Google Ads conversion configuration, server-side transformations or whether imported conversions are deduplicated correctly.

I provide independent GA4 and Google Tag Manager audits that connect the browser evidence to GTM, consent, GA4 and Google Ads. The outcome is a prioritised list of tracking faults and the exact changes needed to fix them.

Ben

Ben Luong is a technical marketing consultant who operates where AI falls short. In a world flooded with cheap, mediocre code and automated strategies, he provides the expert integration, verification, and strategic accountability required to make modern marketing stacks profitable. He specialises in architecting Google Ads, SEO, and GA4 into a single, high-performance system that is accountable to the bottom line.