Testing Tracking Across Old and New Store Domains

A domain move can break measurement even when the store looks normal. Sessions can restart at checkout, payment redirects can appear as referrals, and purchase events can fire twice. Test the journey before using the new analytics numbers to judge marketing performance.

How to make the decision

Document every domain in the buying path: old store, new store, checkout, payment return and thank-you page. Record the analytics property, tag placement, consent mode, cross-domain settings and event names. For GA4, check whether the linker parameter survives transitions and redirects. Place a controlled test order with a known order ID; inspect DebugView, realtime reports and the store record. Confirm one purchase event with the expected value and currency, and check that the original traffic source is retained where technically possible. Compare results before and after cutover using a clearly labeled date.

Worked example

Synthetic store moves from shop.example.ae to example.ae. A test visitor starts on the new product page, reaches checkout, returns from payment and sees the thank-you page. GA4 shows two purchases for one order ID and a payment-provider referral. The team finds both old and new tags firing on the confirmation page, removes the duplicate, updates cross-domain settings and repeats the order. The corrected test shows one order and one purchase event.

What to verify

• Is every domain in the path listed?
• Does one test order create one purchase event?
• Is value and currency correct?
• Are payment referrals reviewed?

Limits and ownership

Cross-domain settings do not fix every redirect or consent problem. Keep the purchase record as the financial truth and treat analytics as a measured observation.

What to hand over

Keep the controlled order ID and screenshots of the analytics debug view with the store receipt. Mark the test date and the property or stream used. When reporting the first post-launch week, annotate the domain change so an apparent traffic or revenue jump is investigated before it is celebrated.

Common question

Can we compare pre- and post-migration revenue in GA4 immediately?

First reconcile test and live orders with the store, then annotate the cutover; otherwise tracking changes may look like business changes.

Next useful step

Use Planning a Catalog Freeze Before Ecommerce Cutover for the adjacent decision. For an implementation review, see Megvi’s ecommerce website development service and bring the source records, proposed checks and open exceptions.

Source checked 28 October 2026: Google Analytics Help: set up cross-domain measurement. Check current platform settings before changing a live store or report.

The worked example is illustrative and is not presented as a Megvi client outcome.