GA4 Tracking QA Checklist for Website Launches and Migrations
When a new website goes live, GA4 can still appear active while forms, key events, ecommerce tracking, consent behaviour or campaign attribution have changed. Use this checklist to spot the tracking checks that should happen after launch — before reporting, ads and client decisions rely on broken data.
A website can launch cleanly and still break measurement
The site may look fine. GA4 may still collect page views. But commercially important tracking can still be missing, duplicated, mislabelled or distorted.
A launch, rebuild or migration can change templates, forms, URLs, GTM placement, checkout journeys, consent behaviour, thank-you pages, ecommerce events and campaign attribution. This matters when clients use GA4, Google Ads, dashboards or ecommerce reports after launch.
Use this checklist if you are asking:
- Did the new website launch affect GA4 tracking?
- Are enquiry forms still tracked properly?
- Are purchases and revenue still being recorded sensibly?
- Did the migration change URLs, thank-you pages or key event triggers?
- Has the GTM container been carried over correctly?
- Are Google Ads conversions still aligned with GA4?
- Has consent behaviour changed after launch?
- Can the client trust the first reports after launch?
Quick risk scan: signs launch tracking needs checking
These are not proof that tracking is broken, but they are strong signals that GA4/GTM should be checked after launch.
GA4 traffic dropped or spiked sharply after launch.
Leads, enquiries or purchases no longer broadly match the CRM, inbox or ecommerce platform.
Key events stopped firing after new templates, forms or checkout steps went live.
The GTM container was re-added, duplicated or moved during the build.
Thank-you pages, confirmation pages or form behaviour changed.
Payment providers, booking tools or third-party domains appear as referrals.
Google Ads conversions changed unexpectedly after launch.
UTMs or campaign landing URLs were changed, redirected or stripped.
Cookie banner or consent settings changed during the launch.
Nobody has tested GA4 after the launch using DebugView, Tag Assistant or GTM Preview.
How to use the checklist
Interpretation guide
- 0–2 issues: GA4 may be broadly usable, but still review after major launch, form, checkout or consent changes.
- 3–5 issues: launch tracking confidence is moderate. Prioritise checks linked to leads, purchases, paid media or client reporting.
- 6+ issues: GA4 should not be treated as launch-ready without a structured review.
- Any issue affecting leads, purchases, revenue or Google Ads conversions should be prioritised.
The launch tracking QA checklist
Work through each section after a new website launch, rebuild or migration. The aim is to identify whether GA4 and GTM are still capturing the actions that matter.
GA4 and GTM foundations
Start with the basic setup. If tags are missing, duplicated or connected to the wrong property, the rest of the data becomes harder to trust.
Check whether:
- GA4 is installed on the new site.
- The correct GA4 property, data stream and Measurement ID are being used.
- The intended GTM container is present.
- GA4 or GTM has not been duplicated through plugins, hard-coded tags or theme settings.
- The new site templates include tracking across important page types.
- Realtime, DebugView, Tag Assistant or GTM Preview show expected behaviour.
- Internal traffic, staging traffic and launch testing are understood where relevant.
- Old supplier tags or legacy containers have not been carried over blindly.
Key events and conversion actions
After launch, the most important question is whether business-critical actions are still being captured correctly.
Check whether:
- Main enquiry, quote, demo, booking or contact forms are tracked.
- Successful submissions are separated from form starts, button clicks or failed attempts.
- Key events still reflect meaningful business outcomes.
- Event names remained consistent through the launch.
- The same action is not counted multiple times.
- Google Ads conversion actions still align with GA4 where relevant.
- Phone clicks, email clicks and secondary enquiries are handled sensibly.
- Thank-you pages, confirmation messages or redirect behaviour still support tracking.
Forms and lead generation journeys
Form changes are one of the most common ways tracking breaks during a launch.
Check whether:
- Every commercially important form has been tested.
- New forms use the same or updated tracking logic.
- Confirmation messages, redirect URLs or thank-you pages work as expected.
- Embedded forms, third-party forms or booking widgets are tracked where relevant.
- Spam/test submissions are not mistaken for real lead volume.
- CRM, inbox, form tool or booking platform numbers are directionally compared with GA4.
- Different lead types are separated where useful.
- Tracking is tested on mobile as well as desktop.
Ecommerce tracking, if relevant
For ecommerce launches, the priority is whether purchases, revenue and product data still make sense after platform, theme, checkout or payment changes.
Check whether:
- Purchase events are still being recorded.
- Purchase events include transaction ID, value and currency.
- Revenue is directionally compared with Shopify, WooCommerce, Stripe or the ecommerce platform.
- Duplicate purchases are checked.
- Add-to-cart, begin checkout and purchase events behave sensibly where used.
- Payment provider referrals are reviewed.
- Discounts, shipping and tax treatment are understood where relevant.
- Product/item data is present where useful.
- Checkout changes have been tested after launch.
Consent, cookies and tag behaviour
Consent changes can make tracking look broken, or make broken tracking look normal if nobody tests accepted, rejected and default states.
Check whether:
- Cookie banner or CMP behaviour has been tested after launch.
- Consent defaults are set before Google tags fire where relevant.
- GA4/GTM behaviour is reviewed before and after consent.
- Accepted, rejected and default states have been checked.
- Tags fire in line with the configured consent model.
- Consent changes are understood when comparing pre-launch and post-launch data.
- Google Ads, GA4 and other marketing tags are reviewed together where relevant.
- No personal information is being sent to GA4 through URLs, page titles, event names or parameters.
URL, UTM and campaign preservation
Launches and migrations often change URLs. That can affect campaign reporting, landing page analysis and attribution.
Check whether:
- Important campaign landing pages still resolve correctly.
- UTM parameters are preserved through redirects where relevant.
- Paid search, paid social and email campaign URLs have been tested.
- Redirects do not strip useful campaign parameters.
- Old high-value URLs have appropriate redirects.
- Landing page paths in GA4 look plausible after launch.
- Source/medium reporting is reviewed after launch.
- Direct traffic has not increased unusually because campaign data is being lost.
Cross-domain and third-party journeys
Some websites rely on booking engines, payment providers, portals, subdomains or third-party checkout journeys. These should be checked after launch.
Check whether:
- Cross-domain measurement is configured where journeys genuinely span domains.
- Subdomains are handled sensibly.
- Booking engines, payment providers or third-party checkouts are reviewed.
- Sessions are not restarting mid-journey.
- Important referral exclusions are reviewed.
- Confirmation steps after third-party journeys are tracked where possible.
- Attribution is not being distorted by self-referrals or payment providers.
- Client reporting reflects known third-party journey limitations.
Reporting and handover
Launch tracking QA is not only about whether tags fire. Someone needs to know what changed, what was tested and what the client can trust.
Check whether:
- The client knows which GA4 property and GTM container are live.
- Key event definitions are documented.
- Launch-related tracking changes are recorded.
- Data Studio dashboards still use the right fields, events and definitions.
- Reports are reviewed after the first few days of post-launch data.
- Stakeholders understand any expected differences between old and new tracking.
- Access to GA4, GTM and dashboards is available to the right people.
- There is a named owner for future tracking changes.
What to check first after launch
Prioritise the checks that affect business outcomes, paid media and client reporting first.
Highest priority
Leads, purchases, revenue, key events, Google Ads conversions, form submissions, checkout journeys, consent behaviour and campaign attribution.
Medium priority
Event naming, landing page reporting, secondary enquiries, internal traffic, GTM documentation, dashboard fields and handover notes.
Lower priority
Minor naming inconsistencies, legacy events, low-value engagement tracking and historic issues that do not affect current launch reporting.
Need launch tracking checked before reports or ads rely on it?
Choose the route that best matches what has happened after launch.
Website just launched or migrated?
Ask MeasureNest to QA launch tracking across GA4, GTM, key events, forms, ecommerce where relevant, consent behaviour and campaign reporting.
Ask MeasureNest to QA launch tracking →Already know something is broken?
Use Tracking & Implementation Support for known GA4, GTM, form, ecommerce, key event or Google Ads conversion tracking issues.
View Tracking & Implementation Support →Not sure what changed?
Start with a structured GA4 Clarity Audit to understand what is working, what is broken and what to fix first.
Request a GA4 Clarity Audit →Related MeasureNest services
Useful support routes if launch tracking needs review, repair or partner input.
Tracking & Implementation Support
For known issues with GA4, GTM, forms, ecommerce, key events or launch tracking.
View service →GA4 Clarity Audit
For a structured review of tracking confidence, reporting quality and fix priorities.
View service →GA4 Support for Agencies
For agencies and studios that need GA4/GTM partner support around launches, migrations or client reporting.
View service →Launching a new site should not mean guessing whether tracking still works
MeasureNest can review the GA4/GTM tracking setup after launch and identify what is working, what is unclear and what should be checked first.