How to run a full tag QA before launch

Launching with broken analytics is expensive. Here is the preflight we automate, and you can run manually if needed:

1) Environment sanity

• GA4 measurement ID points to the right property.
• GTM container version is published from staging with expected tags only.
• Consent banner loads before analytics requests.

2) Coverage

• Key flows: landing → form submit; product view → add to cart → checkout; pricing CTA → signup.
• Check that every CTA click has a unique selector or data attribute.
• Ensure commerce attributes (items, value, currency) are populated where relevant.

3) Consent & regions

• In EU/EEA: analytics fires only after consent granted (or as cookieless pings if explicitly allowed).
• In US/CA: confirm region-specific behavior if you gate per state/country.

4) Payload correctness

• Use GA4 DebugView: verify event names, params, and no duplicate fires.
• Confirm page_location/page_referrer are set; strip PII from URLs.

5) Drift prevention

• Compare container to last approved manifest; remove orphaned tags/triggers/variables.
• Lock down GTM access to the deployment account only.

TagZen automates this checklist: crawl, propose manifest, deploy safely, then run Playwright-based QA against GA4 DebugView. If you want the checklist baked into your pipeline, reach out at hello@tagzen.ai.