← Blog·Analytics Implementation

Analytics Implementation

Google Analytics audit checklist: 10 checks for GA4

Ten GA4 audit checks, from property setup to consent and custom dimensions: what each one catches, the evidence to inspect, and who owns the fix.

David PombarSwiss army knife at Trackingplan
17 min read · 3816 words

This checklist is the hands-on part of a Google Analytics audit, the GA4 version of the web analytics audit: the ten checks that invalidate a GA4 report when they fail, in the order to run them.

A Google Analytics audit checks whether your GA4 property collects the right data, under the right consent conditions, with the right event and parameter structure. Start with property configuration and data streams, then verify events, campaign tagging, User-ID, key events, privacy, tag management, anomalies, cross-domain tracking, and custom definitions.

Use this checklist by hand for a one-time review or after a major release, or get a free GA4 audit built from your real traffic. To catch drift between audits, you need continuous monitoring; when a metric has already moved, you need root-cause diagnosis. The difference is covered at the end.

Start with the data that can invalidate every report

Before you review a single event, confirm three things: you are auditing the right GA4 property and data streams, access is limited to the people who need it, and you know the consent and privacy rules that apply. A careful event review is useless if it runs on the wrong property, misses a major traffic segment, or covers data that should never have been collected.

Run the ten checks in order when you validate a setup from scratch. If you are investigating a sudden change, jump to check 8, compare the affected segments, and trace the change back to the request, the dataLayer, the tag, the consent state, or the release that introduced it.

The 10 checks at a glance

Audit areaFailure it catchesEvidence to inspectLikely owner
1. Property and account structureData lands in the wrong property, stream, time zone, or currency, or access is too broadAccount and property hierarchy, stream IDs, time zone, currency, user permissionsAnalytics lead or administrator
2. Events and parametersImportant events are missing, duplicated, renamed, or sent with incomplete parametersTracking plan, network requests, dataLayer, DebugView, parameter valuesAnalytics engineer or developer
3. UTM and campaign taggingCampaign traffic splits across inconsistent source, medium, or campaign valuesLive campaign URLs, acquisition reports, naming convention, auto-taggingMarketing operations
4. User-IDLogged-in journeys fragment across devices, or an ID persists after logoutLogin and logout requests, user_id values, reporting identity, consent stateProduct analytics and engineering
5. Key eventsBusiness-critical actions don’t fire, fire twice, or are marked incorrectlyKey event definitions, test journeys, transaction_id, value, and currencyGrowth or analytics owner
6. Consent and privacyTags fire before consent, consent signals are missing, or personal data enters requestsConsent state, tag firing order, request payloads, URLs, custom dimensionsPrivacy, analytics, and engineering
7. Tag management and dataLayerTriggers, variables, or dataLayer pushes send wrong values or stop tags from firingGTM Preview, dataLayer pushes, trigger conditions, container versionsTag management owner
8. Anomalies and data qualityA release, campaign, browser, region, or source causes a sudden changeTime series, segmented reports, release calendar, request-level comparisonsAnalytics and engineering
9. Cross-domain trackingSessions restart, your own domain shows up as a referral, or the journey breaks at checkout or loginDomain map, _gl linker parameter, unwanted referrals, ga_session_id continuityAnalytics engineer
10. Custom dimensions and metricsDefinitions are unregistered, wrongly scoped, high-cardinality, or no longer populatedCustom definitions, parameter names, scope, data types, observed valuesAnalytics owner

The table is a triage map, not a substitute for the checks below. When a check fails, record the affected page, event, parameter, consent state, release, and owner, so the fix can be retested.

Verify property configuration and account structure

A poorly organized account leads to data silos, inconsistent reporting, and security risks. Auditing the GA4 account hierarchy, naming conventions, and user permissions comes first because every other check depends on it.

A laptop displaying property audit data with charts and graphs, next to a notepad, pen, and glasses on a wooden desk.

Why it matters

If you analyze the wrong property or data stream, every conclusion that follows is wrong. This check confirms the “what” and “where” before you analyze the “how” and “why.”

How to audit your account structure

Audit event implementation and parameter naming

Events capture every interaction in GA4, from a button click to a purchase. If implementation is inconsistent or naming is chaotic, analysis breaks. This check makes sure what you think you are tracking is what is actually collected.

Overhead view of a person coding on a laptop, with a notebook and glasses on a wooden desk.

Why it matters

If the web team sends form_submit and the app team sends formSubmitted, you can’t analyze form submissions across platforms. A consistent event schema is what makes cross-team analysis possible.

How to audit your event implementation

Validate campaign tagging and UTM parameters

Without consistent UTM parameters, you can’t attribute conversions, compare channels, or calculate return on spend. This check prevents (direct) / (none) and (not set) from swallowing your acquisition reports.

Why it matters

If one person tags utm_medium=cpc and another ppc, GA4 reports two channels and your paid search data splits in half. Budget decisions made on split data are wrong.

How to audit your campaign tagging

Review User-ID for cross-device tracking

Standard GA4 tracking identifies users by browser cookies or app instance IDs, so one person on three devices looks like three users. User-ID stitches authenticated sessions together.

Why it matters

Without a working User-ID, you overcount users and undercount lifetime value. That skews conversion rates, acquisition costs, and retention.

How to audit your User-ID implementation

Assess key events and conversion completeness

GA4 calls conversions key events. This check confirms that every business-critical action, from a purchase to a sign-up, is mapped to an event, marked as a key event, and sent with the right parameters. Without it, you can’t optimize campaigns or justify budgets.

Why it matters

If purchase is missing transaction_id, or trial_signup fails on one browser, the data that connects your tracking to revenue is gone, and nothing in the standard reports says so.

How to audit your key events

Audit data collection for privacy and PII

Collecting personally identifiable information (PII) in GA4 breaks Google’s terms of service and can lead to penalties under GDPR and CCPA. Auditing for PII, checking consent, and reviewing data handling settings protects your users and your business.

Why it matters

If emails or names reach GA4 through URLs or event parameters, you can lose that data, your property can be suspended, and the legal exposure lands on the company. Data collected without valid consent can’t be used with confidence either.

How to audit your privacy compliance

Verify tag management and dataLayer structure

Your tag manager, usually Google Tag Manager, decides which tags fire and with what data. A misconfigured container, or a poorly structured dataLayer (the JavaScript object that passes information from your site to the tag manager), leads to missing events and wrong values.

A tablet displays 'Data Layer' with a flowchart diagram on a wooden desk alongside notebooks.

Why it matters

GA4 is only as good as what it receives. A misfiring tag or an inconsistent dataLayer pollutes every report downstream, and fixing it in GA4 is impossible after the fact.

How to audit your tag manager and dataLayer

Analyze traffic anomalies and data quality issues

Once the setup is validated, look at the data itself. Sudden spikes, unexplained drops, and persistent inconsistencies are often the first sign of a broken tag, an unaccounted-for traffic source, or a collection failure.

Why it matters

A traffic spike can look like a marketing win and turn out to be bots diluting your engagement metrics. A drop in app conversions after an OS update can be a tracking failure, not lost demand. Neither shows up as an error in GA4; both distort decisions.

How to audit for anomalies and quality issues

Validate cross-domain and cross-subdomain tracking

When a user moves from yourbrand.com to shop.yourbrand.com or a third-party checkout, a wrong configuration makes GA4 start a new session. User counts inflate, the original source is lost, and conversions are misattributed.

Why it matters

Without cross-domain tracking, the move to a new domain starts a new session, often attributed as a referral from your own site. That distorts attribution and session counts across the whole journey.

How to audit your cross-domain setup

Review custom dimensions and metrics

Custom dimensions and metrics answer the business questions standard events can’t. This check confirms they are accurate, correctly scoped, and still populated.

Why it matters

A dimension with the wrong scope (event-scoped instead of user-scoped for a customer segment, for example) produces reports that look fine and are wrong.

How to audit your custom dimensions and metrics

Beyond GA4: two checks across the stack

GA4 is rarely the only destination. The same site usually feeds an ad platform, a product analytics tool, a CRM or a warehouse, and the people reading each one expect the same numbers. Two checks cover that, whatever the analytics tool.

Compare the same metric across destinations. Map where each key event goes, and note every filter or transformation on the way. Then compare event volumes, users and conversions between the tools for the same days. A gap that holds steady is a definition to document. A gap that changes after a release is a delivery failure: an event that stopped reaching one destination, or reaches it twice.

Validate the dashboards people actually use. An audit that stops at the property misses the last step. Open the reports stakeholders read, check that each chart uses the event, filter and date range it claims, and that a metric defined in two dashboards is defined the same way in both. A correct property behind a wrong chart still produces a wrong decision.

Benchmarks: reading the results

Finding issues is only half the job. You also need to know whether your baseline metrics are healthy before and after the fix.

MetricTypical GA4 benchmarkAction if below benchmark
Engagement rate46% to 54%Check bounce triggers and page load speed
Session duration2 to 2.8 minutesReview content relevance and UX flow
Conversion rate (eCommerce)1% to 4% (varies by sector)Audit checkout event firing and funnel steps
Event hit rateConsistent across sessionsInvestigate tag firing gaps with DebugView

When you compare your numbers to these benchmarks, context matters. A media site will have different engagement patterns than a B2B SaaS product. Use benchmarks as a directional signal, not a hard pass/fail threshold.

Prioritizing your findings:

Communicating audit results clearly is as important as running the audit itself. Frame findings in business terms: “We’re missing conversion data from 18% of users due to a consent configuration error” lands harder than “Consent Mode V2 isn’t set up correctly.” Use GA4 anomaly detection reports to show stakeholders the before-and-after impact of your fixes.

How often should you audit GA4?

Audit GA4 at least once or twice a year, and every quarter for high-traffic or high-revenue sites. Always run one after a major website change, a platform migration, or an unexpected KPI shift. Between audits, monitor the live implementation continuously: an audit shows the setup on the day you check it, and the next release can break it again.

A one-time audit is better than nothing, but it’s not a strategy. Tracking implementations drift. Sites change. Consent regulations evolve. Your audit schedule needs to keep pace.

A three-step system for sustainable audit practice:

  1. Set calendar reminders for scheduled audits tied to your business planning cycle. Quarterly reviews align well with budget and strategy reviews.
  2. Use automated monitoring tools to catch issues between manual audits. GA4 audit tools that monitor live traffic are now the preferred approach for continuous data quality, because they surface problems in real time rather than weeks later; the data quality tools comparison separates the ones that watch the warehouse from the ones that watch the tags.
  3. Review KPIs quarterly against your audit findings. If a metric shifts unexpectedly, check whether a tracking change preceded it before drawing any conclusions.

Pro Tip: Always run a focused audit immediately after any significant site change, including CMS updates, checkout redesigns, or new tag deployments. These are the moments when tracking breaks most often, and catching issues early saves hours of retroactive analysis.

For a structured starting point every time, keep a copy of the GA4 audit checklist bookmarked and ready to go.

After the audit, choose the right follow-up

A manual audit tells you whether the setup was sound when you inspected it. It doesn’t tell you what changed after the next release. These three activities solve different problems:

If you need to…Use…What it does
Establish whether a GA4 setup is configured correctlyA one-time auditReviews the property, implementation, consent, and reporting configuration at a point in time
Detect drift after releases, campaigns, or vendor changesContinuous monitoringWatches live collection for missing events, malformed parameters, consent failures, and unexpected changes between audits
Explain a change that has already happenedRoot-cause diagnosisCompares the affected requests, dataLayer, tags, consent state, segments, and recent releases to find the cause

If you need a repeatable process, with prerequisites, benchmarks, and an audit schedule, use the Google Analytics audit template. Come back to this checklist when you need the technical map of what to inspect.

For the monitoring part, Trackingplan works where the data is produced: the hit, the dataLayer, the consent state, the GTM release. It learns your baseline from real traffic and flags missing properties, broken triggers, duplicate fires, and consent breaches as they appear, with links to the affected hits. Rethink, a digital analytics agency, gets notified “sometimes even just a couple of hours after a release,” instead of waiting a day for GA4 data (read the story). To run this checklist on your own traffic, the free GA4 audit covers events, parameters, UTMs, pixels, consent, and PII over a 9-day trial.

Use the findings from this checklist to decide which events, parameters, and consent states matter most, and when a metric moves, trace it back to the request before you change the report.

Go deeper

David PombarSwiss army knife at Trackingplan

Read more from David, a Senior Product Strategist with 18+ years in digital product development and an atypical error detection knack.

Read next

All Blog →

Trackingplan

See everything. Miss nothing.

Your implementations audited around the clock with real-time, real-user data. Real-time alerts about errors or changes in your data, campaigns, pixels, privacy and consent. Let AI flag issues before they cost you.