Why audit conversion tracking in GA4
Accurate conversion data is the foundation of ROI calculations, budget allocation and creative optimisation. In GA4 the event‑based model gives flexibility but also creates opportunities for misconfiguration that can silently skew performance reports.
Pre‑audit preparation
Before you dive into the checklist gather the following:
- Access to the GA4 property and the associated Google Tag Manager container
- A list of business‑critical conversions (purchase, lead, sign‑up, add‑to‑cart, etc.)
- Documentation of any custom parameters that feed downstream models
Checklist
1 Verify that each conversion is marked as a conversion event
In the GA4 UI go to Configure → Conversions. Ensure every event you rely on for optimisation appears in the list and that the toggle is switched on. If an event is missing, add it using the event name exactly as it is sent from the site.
2 Confirm event naming consistency
Inconsistent naming (e.g., purchase vs Purchase) creates duplicate entries in reports. Export the event list via the DebugView or BigQuery export and scan for case or spelling variations. Standardise the name in your tag manager.
3 Validate required parameters for each conversion
Each conversion should include the parameters you use for attribution and value calculations. For a purchase event, typical parameters are value, currency, transaction_id. Use the GA4 real‑time report or DebugView to confirm the presence and data type of each parameter.
4 Check for duplicate event firing
Duplicate hits inflate conversion counts. Test the flow in a private browser window, trigger the conversion, and watch the event stream in DebugView. If the same event fires more than once per user action, adjust the tag trigger or add a once‑per‑session condition.
5 Review cross‑domain tracking configuration
If your funnel spans multiple domains, ensure the measurement_id and client_id are carried over. Verify the allow_cross_domain_tracking flag is enabled in GTM and that the linking parameters appear in the URL on the destination page.
6 Audit data privacy and consent handling
GA4 respects consent mode. Confirm that the tag fires only after the user has given the appropriate consent for analytics and conversion measurement. Check the consent state in the Consent Overview report.
7 Verify conversion value accuracy
For revenue‑based conversions, compare the value parameter reported in GA4 against the order total recorded in your e‑commerce platform. Small mismatches often indicate currency conversion or rounding issues.
8 Test server‑side vs client‑side event parity
If you use the GA4 Measurement Protocol or server‑side tagging, send a test conversion through both paths and compare the event payloads in DebugView. Ensure no parameters are dropped in the server‑side flow.
9 Ensure proper attribution window settings
GA4 defaults to a 30‑day conversion window. Verify that this aligns with your business cycle. Adjust the window in Admin → Data Settings → Attribution Settings if needed.
10 Document the audit outcome
Record any findings, changes made, and a date stamp in a shared audit log. This creates a baseline for future reviews and helps new team members understand the current configuration.
Next steps after the audit
With the checklist complete, schedule a quarterly repeat to catch configuration drift. Integrate the audit into your performance‑marketing SOP and tie any detected issues to campaign optimisation cycles.
Leave a Reply