Why your tracking broke after a developer or theme change
You did not touch analytics, but a developer shipped an unrelated change or you switched theme, and now the data is wrong. Tracking lives in the same code everyone else edits, so it is easy to break without anyone noticing until the numbers go quiet.
How a routine change breaks it
- Template replaced: the new theme or template does not include the GTM snippet, so tags vanish.
- Data layer removed: a refactor drops the data layer values your tags read, so events fire with no detail.
- Markup changed: a tag that relied on a CSS class or element ID stops matching when the developer renames it.
- Consent re-ordered: scripts now load in a different order and tags fire before, or are blocked by, consent.
How to catch it
Line the data drop up with your deploy history, the break is dated to the change. Confirm with GA4 DebugView and GTM Preview whether tags still fire and still carry their values. A sudden conversion drop after a release is the usual first symptom.
How to prevent it next time
Treat tracking as part of the deploy, not an afterthought: keep the GTM snippet and data layer in a stable template that refactors do not casually remove, add a tracking check to your launch checklist, and re-test key conversions after every significant change. A pre-launch health check catches this before it costs you weeks of data.
Want us to check your tracking in 10 seconds?
Pop in your domain and we will show you what is firing, what is not, and where data is leaking. Free, no signup.
Check my tracking freeGet a plain-English audit
We check your live GA4, Google Tag Manager and consent setup by hand and tell you exactly what is wrong. The audit comes off any build.
See how it works & pricingDatahound are analytics and ad-tracking specialists. We fix broken GA4, Google Tag Manager and server-side tracking so every sale, form and call gets counted. Back to datahound.agency · All tracking guides · Tracking broke after a redesign