A relaunch is an intervention in the technical foundation of a website. New templates, forms, URLs, cookie banners, and checkout steps can alter previously functioning tracking signals. That is why measurement belongs early in relaunch planning: not just after go-live, but alongside concept, development, and quality assurance.
Why tracking frequently breaks during relaunches
Tracking depends on many components: tags are not integrated, data layers are missing, form logic changes, or consent signals no longer reach Google tags. Often, the website remains functional for visitors while conversions silently fail. New domains, redirects, and cross-domain journeys can also affect attribution and sessions.
Before the relaunch: document existing tracking
Before starting, document events, conversions, GTM tags and triggers, DataLayer parameters, consent logic, URLs, and forms. For online shops, this includes product detail pages, cart, checkout, the purchase event, and the Transaction ID. Also record which Google Ads conversion actions and GA4 key events are important. This inventory serves as the benchmark for testing on the new website.
Define the DataLayer for the new website
The new website requires a professionally documented data model. Define which events are triggered when and which parameters accompany them. In e-commerce, item data, value, currency, and Transaction ID should remain consistent across all funnel steps. The DataLayer should provide data, not hide business logic. This allows development and analytics teams to test data handovers effectively.
Prepare GTM and GA4
Verify that the correct GTM container is integrated across staging and production. Check tags, triggers, variables, consent settings, and the GA4 configuration. In GA4, relevant events should arrive with the expected parameters, and the appropriate key events must be marked. Work with a documented container version and avoid untested live changes during go-live.
Account for Google Ads conversion tracking
Google Ads requires the appropriate conversion action with the correct trigger and value logic. Check whether forms, purchases, or other goals are still mapped to the right action. If GA4 conversions are imported, additionally inspect the GA4 events. A relaunch is no reason to launch multiple parallel conversion setups in an uncoordinated manner—this increases the risk of duplicate signals.
Test consent and the CMP
Do not test the CMP merely visually. Test various consent decisions and ensure that tags and data transmissions respond according to the intended state. Changes to banners, categories, or default settings can heavily impact measurement. Consent is not an afterthought for optimization, but a central component of relaunch acceptance testing.
Test the staging environment properly
Staging enables testing before going live. Use GTM Preview, browser developer tools, and GA4 DebugView to trace events, requests, and parameters. Execute real test cases for forms and, if relevant, the entire checkout. Also ensure that test data remains clearly identifiable and does not accidentally distort operational reports or campaign optimization.
Go-live checklist
GTM loaded, consent correct, GA4 requests visible, and Google Ads conversions triggered appropriately.
Form events and purchase tested, including value, currency, and Transaction ID.
URLs, redirects, and, if applicable, cross-domain tracking verified.
The first days after the relaunch
Validate data trends against an appropriate prior period. Compare not just absolute conversion numbers, but also traffic, events, conversion rate, revenue, and channel distribution. Seasonality, campaigns, and technical migrations can explain differences. However, unexpected discrepancies should be investigated early before they affect reporting or optimization.
Detecting tracking failures after releases
Even after a successful launch, subsequent releases can alter signals. Detecting tracking failures explains why outages are often not immediately visible.
Conversion tracking monitoring
An audit and a successful relaunch are snapshots in time. Conversion tracking monitoring complements testing through continuous observation of defined signals.
Sentinel after the relaunch
After a successful relaunch, Data Flakes Sentinel can help uncover unusual subsequent changes in conversion and marketing data. Monitoring does not replace root-cause analysis, but it provides an early alert for targeted investigation.
Relaunch tracking with Data Flakes
Data Flakes supports the planning, implementation, and quality assurance of tracking during website relaunches—from DataLayer and GTM to GA4, Google Ads, and consent.
Plan tracking for your website relaunch
Frequently asked questions about relaunch tracking
When should tracking be planned during a relaunch?
Ideally during the conceptual phase. This allows requirements for forms, data layers, checkout, and consent to be incorporated directly into development.
Can the existing GTM be reused?
Often yes, provided the container, tags, and consent logic fit the new website. Thorough testing prior to go-live is essential.
Does the DataLayer have to be rebuilt from scratch?
Not necessarily. However, it must match the new website and the functionally defined events. Existing data handovers should be deliberately migrated or replaced.
How do I test tracking on staging?
Use GTM Preview, check the DataLayer, and monitor GA4 DebugView. Test real forms and checkout scenarios across various consent states.
What should be checked immediately after go-live?
Check GTM, consent, GA4 requests, Ads conversions, form events, purchase, Transaction ID, URLs, and, if applicable, cross-domain tracking.