The new site looks fantastic — cleaner layout, faster pages. Then a fortnight later someone opens the reports and the numbers have fallen off a cliff: leads dried up, conversions zero, the traffic graph flatlining on launch day.
Nine times out of ten nothing is wrong with the marketing. The tracking simply broke when the site was rebuilt. At ZenWeb we run analytics for 500+ Malaysian SMEs, and broken tracking after a redesign is one of the most common — and most preventable — fire drills we handle. Restore it and your digital marketing reporting tells the truth again.
It’s a close cousin of rankings dropping after a redesign and traffic crashing after a site migration — same trigger, different symptom. The issue isn’t Google’s view of your pages; your own measurement stopped recording. The video below covers why Google Analytics stops showing data, before the redesign-specific fixes.
Source video: Analytics Mania on YouTube
Broken tracking after a redesign feels alarming because the timing lines up with the launch. Sales panic, someone blames the new site. In reality, both share one cause: the developer rebuilt every page from scratch, and the snippets that quietly counted your visitors and leads didn’t come across.
This guide keeps it practical for a Malaysian SME: why a rebuild breaks measurement, the warning signs, what breaks most often and why, how long the damage runs before anyone notices, a step-by-step restore, how much lost data you can get back, and when to call a specialist.
Quick Answer: A redesign rebuilds your pages on a new theme, and tracking code lives inside the old theme’s files. Unless the developer re-installs your GA4 tag, GTM container, and conversion events on the new build, they get left behind and data stops on launch day.
Your tracking isn’t part of the visible design. It’s a set of hidden snippets: a Google tag in the header, a Tag Manager container, conversion events on your forms and buttons, a Meta Pixel for ads. These sit inside the theme, a plugin, or a header script — exactly the parts a redesign replaces.
A developer’s brief is the look and the content. Analytics is easy to forget because nothing on the page shows it’s missing — the site works, buttons click, forms send. Only the measurement layer is gone, invisible until you open a report. It’s the same root issue behind a Google tag not being detected: the tag simply isn’t on the new pages.
Three common rebuild scenarios trigger it:
Quick Answer: The clearest sign is a sharp drop in sessions, users, or conversions dated to launch day. If GA4’s Realtime report shows no active users while people are browsing, your tag isn’t firing. Missing conversions with steady traffic points to broken events, not a broken tag.
Broken tracking rarely announces itself — you have to go looking, and the pattern of the drop tells you what broke. Watch for these signals after a launch:
If the drop is total and dated to launch, you’re likely looking at the same emptiness described in GA4 showing no data; a partial drop means some tags survived and others didn’t.
Not sure whether your data actually broke?
A quick tracking check tells you exactly which tags survived the rebuild and which didn’t. See how our digital marketing team audits it →
Quick Answer: The GA4 base tag going missing is the single most common casualty, followed closely by conversion events for forms, calls, and purchases. Tag Manager containers, Meta Pixels, and redirect-dependent tracking break less often but hurt just as much. Most sites lose more than one at once.
Across the post-redesign audits we run, the same handful of elements break again and again. A rebuild rarely takes out just one — the base tag and its dependent events go together. Here’s how often each shows up broken.
| Element found broken | Share of audits |
|---|---|
| GA4 base tag missing on some or all pages | 61% |
| Conversion events not migrated (forms, calls, purchases) | 54% |
| Google Tag Manager container not reinstalled | 38% |
| Meta Pixel or Conversions API dropped | 33% |
| Changed URLs with missing redirects | 29% |
| New consent banner blocking tags | 22% |
Source: ZenWeb client sample, 500+ Malaysian SME accounts, 2024–2026. Shares exceed 100% as most sites lose more than one element.
The top two are a pair: a failing base tag takes every event with it, so a site that loses its Google tag also shows zero conversions. A dropped Meta Pixel separately starves your ad campaigns of signals.
Quick Answer: The number-one root cause is tags living only in the old theme and never being rebuilt on the new one. A close second is the tracking snippet simply being left out of the new template. Staging-to-production gaps, incomplete redirects, and default-blocking consent tools account for the rest.
Knowing what broke tells you what to fix; knowing why tells you how to stop it recurring next time. In our audits the causes cluster into five, and the top one alone explains roughly four in ten cases.
| Root cause | Share | What it looks like |
|---|---|---|
| Tags lived only in the old theme | 40% | Base tag and events vanished together on launch |
| Snippet left out of the new template | 24% | Some pages track, others don’t |
| Staging had tracking, production didn’t | 16% | Tested fine, then live site records nothing |
| URLs changed, redirects incomplete | 12% | Broken event triggers and lost UTM continuity |
| New consent tool blocks tags by default | 8% | Tags wait for a consent signal that never comes |
Source: ZenWeb client tracking across 12 industries, Malaysia, 2024–2026.
The pattern that matters: most causes are a handover gap, not a technical fault. The old tags worked fine; nobody was asked to carry them across. It’s also why events break even when the base tag survives — the trigger conditions changed, which we cover in fixing GA4 events that aren’t firing.
Quick Answer: It depends on how you monitor. Teams with post-launch QA or real-time alerts catch it the same day. Those relying on weekly reviews lose about a week; monthly-report-only teams lose a month. Sites with no monitoring often run two months or more before someone notices.
Every day tracking stays broken is a day of data you never get back. GA4 doesn’t backfill, so the gap is permanent. How wide it grows depends on how quickly someone looks — and the gap between best and worst case is enormous.
| How you monitor | Typical time to notice | Data lost |
|---|---|---|
| Post-launch QA or Realtime alert | Same day | Little to none |
| Weekly performance review | ~1 week | ~7 days |
| Monthly reporting only | ~1 month | ~30 days |
| No monitoring (spotted by accident) | 2 months+ | 60+ days |
Source: ZenWeb client sample, Malaysia, 2024–2026.
The lesson: a five-minute check on launch day is worth weeks of recovered data. The same discipline catches quieter problems too — the missing automatic events behind GA4 Enhanced Measurement being switched off or GA4 not recording conversions.
Every day of missing data costs you decisions.
We restore tracking and set up alerts so a break never runs silent again. Get your analytics restored and monitored →
Quick Answer: Restore tracking in order: confirm what’s broken in Realtime, re-add the GA4 tag and GTM container across every page, rebuild each conversion event, restore ad pixels, fix redirects and UTMs, clear any consent block, then verify in DebugView before you trust the numbers again.
Work top-down — fixing events before the base tag is back just hides the problem. These seven steps rebuild the measurement layer in order.
Once all seven pass, watch the data for a day or two and reconcile it against a second source — your CRM, ad platform, or payment gateway — so you trust the restored numbers.
Quick Answer: Once tracking is fixed, collection is perfect again — but the gap itself is gone for good, because GA4 can’t backfill the days it wasn’t recording. Catch it before launch and you lose nothing; catch it a quarter later and you’ve lost your baseline for months.
Here’s the hard truth: the fix is quick, but the lost days don’t come back. The table below models the permanent loss based on when the break is caught — an illustrative scenario built on GA4’s no-backfill behaviour, so the shape holds even if your dates differ.
| When you catch it | Permanent data lost | What survives |
|---|---|---|
| Before launch (pre-launch QA) | 0 days | Everything |
| Within week 1 | up to 7 days | Almost all; short gap |
| Within month 1 | up to 30 days | Most; one month dented |
| After a quarter | 90+ days | Little; baseline damaged |
Illustrative scenario, based on GA4’s no-backfill behaviour. Actual loss depends on your launch and detection dates.
If a campaign or seasonal peak ran during the gap, that period is simply missing — making year-on-year comparisons and diagnosing later performance drops harder for months. The only real recovery is catching it fast.
Quick Answer: If only the base GA4 tag is missing, most teams re-add it in an afternoon. Bring in help when conversion events, GTM, ad pixels, and consent all broke at once, when revenue tracking is involved, or when GA4 and your ad platforms disagree on attribution.
A single missing tag is a DIY job. A tangle of broken events, mismatched ad conversions, and consent blocks is where a specialist saves you days. Judge it by scope:
As a Google Partner running digital marketing for 500+ Malaysian SMEs, ZenWeb restores tracking after redesigns and sets up the alerts that stop the next launch running blind.
Broken tracking after a redesign is loud in its symptoms but simple in its cause. The new build replaced the parts your tags lived in, and nobody carried them across. Your marketing didn’t fail; your measurement did.
Confirm the break in Realtime, restore the base tag first, then rebuild events, pixels, redirects, and consent, and verify against a second source. Move quickly — the data gap is permanent. Better still, make a tracking check the last item on every launch checklist, and it stops being a fire drill for good.
Open GA4 and check for a sharp drop in sessions or conversions dated to your launch day. Then open the Realtime report and browse your live site — if you don’t appear as an active user, your tag isn’t firing. Steady traffic with missing conversions means the base tag survived but your events broke.
No. GA4 only records from the moment tracking works again, and it can’t backfill the days it wasn’t collecting. Once you restore the tags, future data is complete, but the gap is permanent. That’s why catching a break within days instead of months matters so much — speed is the only way to limit the loss.
Because your tracking code lived inside the old theme, plugin, or header, and the redesign replaced those parts without carrying the code across. The most common cause is tags existing only in the old build. A close second is the snippet simply being left out of the new template, so some pages track and others don’t.
Re-adding a single missing GA4 tag usually takes under an hour. A full restore — base tag, GTM, conversion events, ad pixels, redirects, and consent checks — is typically half a day to a day, plus a couple of days of watching the data to confirm everything fires correctly and matches a second source like your CRM or ad platform.
Put tracking on the launch checklist as a required sign-off. Before go-live, confirm the GA4 tag, GTM container, conversion events, and ad pixels are all on the new build and firing in Realtime. Add a same-day post-launch check and a simple alert. That five-minute discipline is what separates a same-day catch from a lost quarter.
Tracking gone quiet after your redesign?
Book a free 30-minute session. We’ll check your GA4 tag, conversion events, and ad pixels on the new site, tell you exactly what broke, and give you a clear plan to restore it — plus alerts so it never runs silent again.
Complete the form and our team will contact you to discuss your goals. Let’s grow your business.
Online
