Google Tag Manager and GA4 Tracking Audit Checklist

What this tracking audit is designed to find

This checklist helps teams find missing conversions, duplicate events, unreliable attribution, consent mistakes and tags that slow down the website. It is useful before increasing advertising spend, rebuilding a website or trusting a new dashboard.

A good audit follows one business event from the application through GTM and into every reporting destination. It does not stop when a tag appears in preview mode.

1. Confirm access and ownership

• List every GA4 property, GTM container, Google Ads account and connected reporting tool

• Confirm which accounts and containers are used in production

• Identify administrators and remove unnecessary access

• Record who may publish GTM changes

• Check whether agencies or former employees still control critical assets

• Confirm that test, staging and production environments are separated

2. Inventory the website implementation

• Find every Google tag, GTM container and hard-coded advertising pixel

• Check whether the same vendor is installed both directly and through GTM

• Review custom HTML tags and undocumented scripts

• Identify tags injected by a CMS, ecommerce platform, consent tool or plugin

• Confirm which routes and subdomains load each container

• Measure the performance cost of the current third-party scripts

Duplicate installation is common after redesigns and agency changes. Use browser network tools and rendered source, not only the GTM interface.

3. Review the measurement plan

• List the business outcomes that count as primary conversions

• Separate primary conversions from engagement events

• Document event names, triggers and required parameters

• Identify the source of truth for leads, orders and revenue

• Confirm which conversions advertising platforms use for optimization

• Remove events that no longer inform a decision

Each conversion should describe a successful outcome. A button click can be useful for diagnosing a funnel, but it should not replace confirmation that the requested action completed.

4. Inspect the data layer

• Check that event names follow a consistent convention

• Make sure events are pushed after success

• Verify value, currency, product, lead and transaction properties

• Confirm transaction and event identifiers are stable and unique

• Check that no restricted personal data is included

• Test asynchronous actions and client-side route changes

• Document which application code produces each event

5. Test consent behavior

• Verify the default consent state before tags load

• Test accepted, rejected and partially accepted choices

• Change consent after the page has loaded and retest

• Open a deep landing page with no existing cookies

• Check every market or regional configuration

• Confirm the consent tool and GTM use the same categories

• Verify that tags do not begin firing unexpectedly after client-side navigation

6. Audit GA4

• Confirm the correct property and web stream are used

• Check page views for initial loads and SPA route changes

• Review event names and unwanted duplicates

• Validate key events and their counting behavior

• Check cross-domain measurement and unwanted referrals

• Review internal and developer traffic handling

• Confirm ecommerce parameters, revenue and transaction IDs

• Compare important events with backend, CRM or order data

• Review retention, access and data-sharing settings with the responsible owners

7. Audit Google Ads

• List active conversion actions and identify the primary ones

• Check whether direct Ads tags and GA4 imports overlap

• Verify conversion IDs, labels, values and currencies

• Confirm a Conversion Linker is present where required

• Check enhanced-conversion configuration and data handling

• Test campaign parameters through redirects and checkout domains

• Review which conversions are included in bidding

• Compare platform conversions with qualified leads or orders

8. Audit Meta

• Confirm the production Pixel ID

• Review standard and custom events

• Validate value, currency and content parameters

• Check browser and Conversions API event deduplication

• Test event quality across consent states

• Compare reported leads and purchases with source systems

• Remove obsolete pixels and duplicate triggers

9. Test React, Next.js and headless behavior

• Navigate without full page reloads and confirm page views

• Use browser back and forward controls

• Submit forms with success and error responses

• Test authentication, embedded forms and cross-domain checkout

• Confirm cached pages do not resend prior conversion data

• Test slow connections and delayed scripts

• Check that hydration or route transitions do not fire tags twice

10. Check data quality and reporting

• Compare daily totals across analytics, ad platforms, CRM and backend

• Explain expected attribution differences

• Find sudden changes around deployments and campaigns

• Review unknown, not set and self-referral values

• Check that dashboards use defined metrics and current fields

• Confirm report owners know which system is authoritative for each question

11. Review governance and maintenance

• Use GTM environments, workspaces and clear version notes

• Require review for custom JavaScript and conversion changes

• Keep a written event specification

• Assign an owner to every third-party script

• Schedule recurring data-quality checks

• Remove unused tags and variables

• Add measurement checks to release testing

What the audit should deliver

The output should be more useful than a screenshot of warnings. Ask for:

• A map of the current tracking architecture

• A prioritized issue list with business impact

• Evidence for duplicates, gaps and consent problems

• A corrected measurement and event plan

• Implementation tasks with owners

• A QA plan and acceptance criteria

• Documentation the team can maintain after the audit

From checklist to implementation

If the checklist reveals a few configuration issues, the team may be able to fix them directly. When the root cause sits in application events, routing, checkout, consent or website performance, it needs engineering work.

Makers' Den can audit and repair the complete path through our Web Performance & Growth Engineering service . For more context on event design and reporting, read our web analytics guide and GTM guide for Google Ads and Meta .