How to Audit Your Google Analytics Configuration

A GA4 property that's been running for a year without a formal review has almost certainly accumulated some drift — a conversion nobody remembers configuring, a data filter that was never actually activated, a custom event with inconsistent naming from different contributors. None of this shows up as an error; it just quietly makes the data less trustworthy over time. A periodic, structured audit is how you catch it before it meaningfully skews a decision.

Section 1: Foundational Settings

• Time zone and currency — confirm both match your actual business location and primary transaction currency under Admin → Property Settings. These can't be retroactively corrected for historical data, so this is mainly a check that nothing was set wrong initially and left uncorrected.
• Data retention — confirm it's set to 14 months (the standard maximum), not the 2-month default, under Admin → Data Settings → Data Retention.
• Internal traffic filter — confirm a filter excluding your own team's IP addresses exists under Admin → Data Settings → Data Filters, and that it's set to Active, not left in Testing mode indefinitely.

Section 2: Tracking Implementation

• Tag coverage — crawl your site (manually or with a tool like Screaming Frog) to confirm the GA4 tag fires consistently across every page template, including any custom landing pages or checkout flows built outside your main CMS.
• Duplicate tracking — check for signs of the tag firing twice on the same page (inflated pageview counts relative to what seems reasonable, or duplicate events visible in DebugView), which can happen after a migration or a GTM container change that wasn't fully cleaned up.
• Realtime verification — visit your own site from an incognito window and confirm you appear correctly in the Realtime report, with the expected page path.

Section 3: Events and Conversions

• Conversion list review — go through every event marked as a conversion under Admin → Events, and confirm each one still represents genuine, current business value, not a stale campaign-specific event or a duplicate of another conversion.
• Custom event naming consistency — check for near-duplicate event names (signup_complete vs. signup_completed) that suggest inconsistent implementation across different parts of the site or by different developers over time.
• Parameter values in DebugView — spot-check a handful of custom events to confirm parameters carry real, non-empty values, not undefined or placeholder text that slipped through untested.

Section 4: E-commerce (If Applicable)

• Full event set implemented — confirm view_item, add_to_cart, begin_checkout, and purchase are all firing correctly, not just purchase alone, since the intermediate events are what make funnel analysis possible.
• Transaction ID uniqueness — confirm purchase events include a unique transaction_id to prevent duplicate-counting from page refreshes.
• Revenue reconciliation — compare a recent period's GA4-reported revenue against your actual order or payment system for the same period, expecting a small, explainable gap rather than an exact match.

Section 5: Privacy and Consent

• Consent Mode implementation — if operating in a region requiring it, confirm default consent state is set correctly and updates properly when a user interacts with your cookie banner.
• Privacy policy accuracy — confirm your privacy policy's description of analytics usage reflects your actual current GA4 and Google Signals configuration, not outdated language from a previous tool or setup.
• Google Signals — confirm whether it's enabled deliberately (for cross-device reporting benefits) or left at a default without an explicit decision, given its privacy and consent implications.

Section 6: Access and Governance

• User access review — check Admin → Property Access Management for former employees, old agency relationships, or overly broad Administrator access granted to people who only need Viewer or Analyst permissions.
• Clear ownership — confirm someone is explicitly responsible for reviewing the property's configuration periodically, rather than it being nobody's specific responsibility.
• Documentation — check whether custom dimensions, conversion events, and audiences have any documentation explaining their purpose, especially for anything not self-explanatory from its name alone.

Section 7: Integrations

• Search Console link — confirm it's connected and populating data under Admin → Product Links.
• Google Ads link (if running ads) — confirm it's connected, auto-tagging is working, and the right conversions are imported for bidding.
• BigQuery export (if applicable) — confirm the export is still running without errors, and that recent daily tables are actually populating in your BigQuery dataset.

Running the Audit Efficiently

For a property you haven't reviewed in a while, work through the sections in the order above — foundational settings first, since a wrong time zone or retention setting affects everything built on top of it, followed by tracking implementation, then the more specific event, e-commerce, privacy, and governance sections. A first full audit on a neglected property might take a few hours; subsequent quarterly reviews are typically much faster, since most sections will already check out cleanly.

Turning Findings Into Action

An audit is only useful if findings get addressed, not just documented. For each issue found:

1. Assess urgency — a wrong currency setting affecting active revenue reporting is more urgent than a stale conversion event from a long-ended campaign.
2. Assign an owner — even informally, someone specific should be responsible for each fix.
3. Set a deadline, especially for anything affecting active decision-making, rather than letting fixes linger indefinitely on a backlog nobody revisits.

FAQ about Auditing Your Google Analytics Configuration

How often should a GA4 property be formally audited?

At least annually for most businesses, with a lighter quarterly check-in on the highest-risk areas (conversions, tracking coverage) for properties with significant business dependence on accurate data.

What's the highest-priority thing to check first in an audit?

Foundational settings — time zone, currency, and data retention — since these affect every other piece of data built on top of them and can't be retroactively corrected for historical data.

Can I audit a GA4 property without any specialized tools?

Yes — most of this checklist relies on GA4's own Admin interface and DebugView, plus basic manual site navigation; specialized crawling tools help with tag-coverage checks on larger sites but aren't strictly required for a smaller one.

Should every business have a BigQuery export to properly audit their data?

No — BigQuery export is useful for advanced, long-term analysis but isn't required for a standard configuration audit, which mostly relies on GA4's built-in interface and settings.

How do I know if a conversion event is still relevant or should be removed?

Ask whether it still represents genuine, current business value — a conversion tied to a discontinued campaign or offer is a strong candidate for removal, even if it was legitimate when first configured.

What's the best way to prevent configuration drift between audits?

Assign clear, ongoing ownership of the GA4 property to a specific person or role, rather than treating configuration as a one-time setup task nobody revisits until problems surface.

Conclusion

A periodic audit is how you catch the quiet configuration drift that accumulates in every Google Analytics property over time — a stale conversion, an inconsistent event name, a filter left in testing mode. Work through the checklist systematically, assign clear ownership for fixes, and your website's analytics will stay something you can genuinely trust rather than something that merely looks like it's working.