Skip to content
home

Analytics implementation · 2 min read

GA4 audit: twelve settings to check this week

A practical checklist, with why each setting matters.

By WebIQ Analytics · 27 November 2025

Many GA4 properties were set up quickly during the migration from Universal Analytics and never revisited. These twelve checks find the most common problems.

Twelve GA4 settings to check.1. Data retention set to the maximum2. Internal and developer traffic filtered3. Unwanted referrals excluded4. Cross-domain measurement configured5. Key events defined and named consistently6. Enhanced measurement reviewed7. Currency and time zone correct8. Consent Mode working9. BigQuery export switched on10. Google Ads and other links active11. Custom dimensions registered12. Access reviewed and documentedCheck each property; record who owns each setting.
Twelve GA4 settings to check.
  1. Data retention. The default for event-level data in explorations is two months; most teams want the longest period available.
  2. Internal traffic. Define your office and developer traffic and activate the filter, or test sessions inflate everything.
  3. Unwanted referrals. Payment providers and login domains appearing as referrers break sessions and steal credit.
  4. Cross-domain measurement. If users move between your domains, configure it, or every crossing starts a new session.
  5. Key events. The actions that matter are marked as key events, named consistently, and not duplicated.
  6. Enhanced measurement. Review what's switched on. Automatic events like form interactions can create noise or duplicates.
  7. Currency and time zone. They should match finance reporting; mismatches make reconciliation painful.
  8. Consent Mode. Check consent signals actually reach GA4 and change tag behaviour, in both accepted and declined states.
  9. BigQuery export. Switch it on. The raw data is invaluable for analysis and modelling, and history only starts from the day you enable it.
  10. Product links. Google Ads and other links are active and owned by someone current.
  11. Custom dimensions. Parameters you send are registered, or they're invisible in reports.
  12. Access. Review who has access and at what level; remove leavers and document owners.

How to run the audit

Work through the list in the admin settings, then test in debug view with a few real journeys: a purchase, a form, a cross-domain step. Record what you found and who owns each fix.

What usually comes next

The audit often reveals a deeper issue: events defined differently by different teams. The lasting fix is an event specification, a single document listing every event, parameter and owner, used to build and test tags. It makes future audits short.

Tracking you can trust, with consent handled properly

We implement GA4, server-side tagging and Consent Mode v2, with an event specification your team can maintain.