Keep GA4 useful after the next site redesign
A redesign that breaks tracking doesn't announce itself - it just leaves a gap in the data that nobody notices until a report comes back looking wrong.
In short
A site redesign routinely breaks GA4 tracking without anyone noticing until a month of data is already gone, because event tags are usually wired to specific page elements that a new design quietly replaces. A versioned tracking plan and a pre-launch QA checklist catch that before launch instead of a month after. The redesign should change how the site looks, not whether anyone can tell what happened on it.
The Situation
"Marketing signs off on a new site design, and three weeks later someone notices the conversion count has been at zero since launch."
A redesign that breaks tracking doesn't announce itself - it just leaves a gap in the data that nobody notices until a report comes back looking wrong, and by then the missing weeks can't be recovered.
We document your GA4 event setup as a versioned reference and run a pre-launch checklist against every redesign, migration, or platform swap - comparing live events to the documented plan before launch, not after - this is part of an analytics platform migration discipline applied to redesigns, not just full platform moves.
What You Get
- Historical reporting continuity preserved across a redesign, so this year is still comparable to last year
- Tracking issues caught in a pre-launch QA pass instead of a post-launch report review
- One documented reference the design and dev teams can check against before shipping changes
Illustrative, not a measured result: a company mid-redesign might find a pre-launch QA pass catches that three of twelve tracked events were tied to CSS classes the new design removed - catching that before launch is the entire value of the checklist, versus finding it in next month's numbers. (Illustrative scenario - not a measured result.)
Frequently Asked Questions
Does this require changing our redesign or dev process?
Just adding one step - a tracking QA pass against the documented plan before launch, alongside whatever QA the design and dev teams already run.
What if the redesign is already live and something broke?
The same audit process applies retroactively - comparing what's currently firing against the documented plan (or reconstructing one if none exists) to find and fix the gap.
Don't Let the Next Launch Break Tracking
Tell us when the redesign ships and we'll scope a pre-launch tracking QA pass.
Talk to a GA4 Consultant