A GA4 configuration audit goes beyond checking whether events are firing. It verifies Measurement Protocol integrity, BigQuery export health, cross-domain measurement, server-side tag setup, and the 15 configuration settings that silently corrupt data when left at their defaults.
Most GA4 configuration issues aren't visible in standard reports. They require API access, network inspection, or cross-referencing multiple Admin settings. Here's what GA4 Health Check checks automatically across the Configuration & Customization module and beyond.
stripe.com, paypal.com, shop.app, and others.analytics_storage, ad_storage, ad_user_data, ad_personalization. Missing signals mean EEA traffic goes unmodelled.Many critical configuration issues are invisible in the GA4 interface. They only surface when querying the Admin API directly. These are the checks manual audits most commonly miss.
client_id, session_id), incorrect API secret usage, and event payload structure violations that cause silent data loss.transaction_id appearing multiple times in the same day indicates double-counting that inflates revenue figures.utm_medium values against GA4's default channel group rules. Non-standard values like social-media, Social, or EMAIL cause sessions to fall into (Unassigned) — invisible until you query the data directly.A configuration audit is most valuable at specific decision points — before a major spend, after a technical change, or when something in the data doesn't add up and you need to know why.
The checks above go deeper than what most GA4 setup guides cover — and deeper than what most agencies include in a standard setup. That's not a criticism; it's the nature of configuration drift over time.
See the complete 47-point checklist →47 automated checks via the Google Analytics Admin API. Full configuration review, scored PDF report, step-by-step fix instructions. Results in under 60 seconds.