Conversions dropped after the relaunch? It is usually tracking, not demand.

A new website, a new checkout or a new shop system goes live, and the numbers fall off a cliff. In most cases the customers are still buying. The tags that should report it were lost, renamed or blocked on the way.

The usual suspects.

data layerthe new templates no longer send the purchase event, or send it under a new name
thank-you pageits URL changed and the trigger still waits for the old one
cookie bannera new banner, and the tags now wait for a consent signal that never comes
containerthe Tag Manager snippet is missing on new templates, or loads twice
paymentan external payment page breaks the session and the sale lands as a referral
domainsa new checkout domain is missing from the cross-domain settings

Most of these are invisible from the front end. The site looks perfect. Only the reports go quiet.

What the silence really costs.

It is not just a hole in the report. Smart bidding sees fewer conversions, lowers bids and loses reach exactly when the new site needs traffic. Once the tracking is fixed, the algorithms need time to learn again. A few days without measurement can cost weeks of performance.

And the decision makers look at a relaunch that seems to have failed, when in fact it may be selling better than the old site.

Just relaunched? Check in 30 seconds what your new site still sends.

The first 48 hours after you notice.

testplace a real test order and watch what fires, in preview mode
compareshop orders against platform conversions, day by day since launch
fixrestore the purchase event, with transaction ID and correct value
documentmark the gap in your reports, so nobody compares the wrong weeks
recoverwhere possible, upload missed conversions later; Google Ads needs the click ID for that

Make the next launch boring.

Tracking breaks in relaunches because it is treated as the last ticket instead of part of the specification. A launch is safe when the tracking is written down before development starts, tested with real orders on staging, and watched by a monitor that alerts within hours, not at the end of the month.

beforea tracking spec in the briefing, signed off by marketing
on stagingtest orders in every market, every payment method
at go-livea checklist, and someone who owns it
aftermonitoring that compares orders and conversions daily

The written spec is your measurement plan. If you do not have one, the relaunch is the moment to create it.

Questions about tracking after a relaunch.

Why did our conversions drop after the website relaunch?

Most often because the purchase event no longer fires, fires under a new name, or waits for a consent signal from a new cookie banner. Check your shop orders: if they are stable while conversions dropped, it is tracking, not demand.

Can we recover the lost conversion data?

Partly. Google Ads accepts offline conversion uploads if you still have the click IDs of the orders. GA4 history cannot be filled in afterwards. That is why fast detection matters more than any repair.

Does a tracking outage hurt Google Ads performance?

Yes. Smart bidding strategies learn from conversions. Fewer reported conversions mean lower bids and less reach, and after the fix the strategies need time to recover.

Who is responsible, the development agency or marketing?

Usually nobody, and that is the problem. Tracking needs one owner who writes the spec, signs off the test and watches the numbers after go-live.

How fast should we notice a tracking outage?

Within a day. A simple monitor that compares orders and conversions daily per market catches most outages before they cost real money.

Keep reading