GA4audit examines existing Google Analytics 4 implementations - for the audit to have something to examine, your website must first be collecting data into a GA4 property. If you don't have one, here's the road map. Deliberately brief: Google maintains the full, always-current instructions, and we link to the right places.
Step 1: create a GA4 property
G-XXXXXXX format.Google's official guide: Set up Analytics for a website and/or app
Step 2: deploy the tag on your website
Three typical routes - from simplest to most flexible:
A plugin / setting in your CMS or store platform.
WordPress (e.g. Google's Site Kit), Shopify, WooCommerce, Wix and most platforms have ready-made fields for the G-… identifier or official integrations. The least work, sufficient for simple websites.
Google Tag Manager (recommended for most businesses).
You install a single GTM container on the site, and configure the GA4 tag (and all future tags) in the GTM panel, without code changes. The most flexible and maintainable option - most checkpoints concerning custom events assume GTM-based work down the line. Guide: Install Google Tag Manager
Direct gtag.js code.
Pasting the snippet from the GA4 panel into the <head> of every page. It works, but every future change requires editing code.
Important: pick one route. Deploying GA4 simultaneously through a plugin and GTM (or GTM and gtag) is the most common cause of duplicated events - a mistake our audit regularly finds with new users.
Step 3: verify and wait for data
Step 4: come back to us
An audit is most valuable once the property has gathered some data - a number of checkpoints analyze the last 30 days (event continuity, channel conversions, the purchase funnel). You can audit a brand-new property right away - the configuration checkpoints will work fully - but you'll get the most value after 2-4 weeks of data collection. A good sequence: implementation → a quick configuration audit → a month of data → a full rescan.
Related articles: