Conversion audit after a site migration
When orders fall after a new site goes live, a conversion audit after a site migration shows whether the drop is real and which checkout step lost the sales. It matches tracked purchases to the order system first, then compares each step by device for matched weeks either side of launch and ranks the falls.
Before and after, by step, example
Mobile delivery details step fell from 78.0% to 61.5% after launch
| Period | Orders in order system | Tracked purchases | Match |
|---|---|---|---|
| 4 weeks before launch | 7,480 | 7,318 | 97.8% |
| 4 weeks after launch | 6,410 | 6,271 | 97.8% |
Result: the tracking gap is the same in both periods, so the funnel below can be compared.
Tracked purchases matched the order system at 97.8% before and after.Funnel: mobile, matched weeks (launch week left out)
-
2Added to basket
−0.1 points
-
3Checkout started
+0.5 points
-
4Delivery details completed
−16.5 points
-
5Order placed
−0.2 points
Ranked list (the audit's output)
- 1.
Delivery details, mobile: −16.5 points (interval −18.1 to −15.0). About 960 mobile orders lost over the four weeks (interval 869 to 1,051). Suspected cause: the postcode lookup on the new delivery form.
- 2. to 4.
Basket, checkout start and order placed: each interval crosses zero, so no change can be called.
Show the numbers
| Step | Before: sessions | Before: step conversion | After: sessions | After: step conversion | Change (points) | 95% interval (points) |
|---|---|---|---|---|---|---|
| 1 Product viewed | 96,400 | 95,800 | ||||
| 2 Added to basket | 11,568 | 12.0% | 11,400 | 11.9% | −0.1 | −0.4 to +0.2 |
| 3 Checkout started | 6,362 | 55.0% | 6,327 | 55.5% | +0.5 | −0.8 to +1.8 |
| 4 Delivery details completed | 4,963 | 78.0% | 3,890 | 61.5% | −16.5 | −18.1 to −15.0 |
| 5 Order placed | 4,566 | 92.0% | 3,571 | 91.8% | −0.2 | −1.3 to +0.9 |
What this fixes
What the conversion audit hands over
How a post-migration conversion audit runs
- 1
Tracking
The audit counts tracked purchases against orders either side of launch. A duplicate event, a missing one or a changed currency setting shows up as a gap that moved.
- 2
Matching weeks
The comparison uses equal full weeks either side of launch week, names any sale or bank holiday on one side only, and adds the same weeks a year earlier.
- 3
Step comparison
Each step gets compared on mobile, desktop and tablet with a 95% interval, so a step that moved by chance isn't sent to the developers.
- 4
Handover
The ranked list, the step table and the SQL go into your drive, so the query reruns after a fix.
Where replatforming audits go wrong
Launch week stays out of every comparison, because it carries fixes and test orders.
Site migration audits by industry
When the cause is broken tags, the fix is tracking work. When the fix is a design choice, such as how the postcode lookup should behave, it goes on the experimentation and CRO roadmap as an A/B test.
Questions people ask
How soon after launch can the audit run?
Once there are full weeks on the new site to set against the same number before it, like the four and four in the example above. Fewer weeks give wider intervals, and the report says which steps it can't call yet.
Do you audit replatforming for ecommerce sites?
Yes. Orders come from the order system on both platforms, so the comparison holds when the two checkouts track differently, and steps match by meaning, such as basket page to basket drawer.
Our GA4 setup changed during the migration. Can you still compare?
Yes. The old steps map to the new by hand, and the mapping goes in the report. A step with no matching event gets compared from server logs or the order system, or left out and named.
Do you fix the step that fell?
No, whoever builds the site makes the fix. Once it ships, we compare that step again for matched weeks, or test it as an A/B test if the fix is a design choice.
When did your new site go live?
On the call we compare your weekly orders either side of the launch date and check whether the tracking can be trusted.