Changing Your Shopify Domain Without Losing Conversion Tracking

TL;DR

A domain change is two migrations wearing one name. The Shopify half is close to automatic: set the new primary domain, and every other domain you own redirects to it [1]. The measurement half is manual and nobody sends you a checklist for it. Cookies are scoped to a domain, so visitor identifiers do not travel. Meta's domain verification is tied to the domain you verified, so the new one starts unverified. Search Console needs telling, and it forwards signals for a fixed window. Plan the second half or you will spend a quarter explaining a traffic cliff that never happened.

Key Takeaways

• Change the primary domain from Settings → Domains → Change domain type → Primary domain; other domains, including your .myshopify.com address, then redirect to it automatically [1].
• The GA4 _ga cookie is written from the site's own domain with a 2-year lifetime [2]. A new domain means a new cookie, so returning visitors are counted as new and prior sessions cannot be stitched to them.
• Meta domain verification is per domain, so the new one arrives unverified. Re-verify it on the day of the switch, then review the event configuration in Events Manager, because domain-scoped settings do not follow you across [3].
• File a change of address in Search Console: it forwards signals for 180 days after you start, works only between domain-level properties you own on the same account, and does not move subdomains for you [4].
• Add the old domain to GA4's unwanted referrals list at Admin → Data streams → Web → Configure tag settings → List unwanted referrals, which appends ignore_referrer for matching events [5].
• Checkout runs on the shop domain rather than a separate checkout host, so the funnel stays on one domain before and after the switch [6].
• Server-side order events do not depend on the storefront domain at all, so the purchase side of your tracking survives the cutover untouched.

What actually breaks when the domain changes?

One thing, and it explains almost every symptom you will see: cookies belong to a domain. Google's own cookie reference lists _ga as set from the site's domain with a two-year duration [2]. A shopper who has been browsing oldstore.com for six months carries a _ga value that newstore.com cannot read, because the browser will not hand it over. The same is true of the advertising cookies your pixels rely on for click matching.

So on cutover day, everybody is new. GA4 reports a spike in new users and a collapse in returning ones. Any audience built on cookie recency starts shrinking. Sessions that began on the old domain and finished on the new one split into two, and the second lands as a referral from your own former self unless you exclude it. The first-party cookie mechanics on Shopify go deeper into what each identifier does; the consequence here is that pre-cutover browsing identity is gone and no setting recovers it.

What does not break is anything keyed to an account rather than a domain. Your GA4 property, its measurement ID, its full history, and its custom dimensions are untouched. Your Meta pixel ID stays the same. Your Google Ads conversion actions stay the same. The destinations are fine. The visitor identity that connects one visit to the next is what resets.

What does Shopify handle, and what does it leave to you?

Shopify's half is genuinely simple. From Settings → Domains, pick the new domain, choose Change domain type, select Primary domain, and confirm. After that, other domains you own point at the new one, "the primary domain URL replaces other domain URLs in the browser", and your your-store.myshopify.com address redirects too [1].

Checkout comes along without any action from you. Shopify moved checkout onto the shop domain rather than a separate checkout host, and a store forcing redirects to its primary domain has its checkouts occur on that primary domain [6]. So the funnel stays on a single domain on both sides of the switch, which is the reason a domain change is survivable for tracking at all.

What Shopify does not cover is anything living outside it, which is where the entire measurement story sits. Nobody at Google, Meta, or TikTok is watching your Shopify domain settings.

The one piece of Shopify infrastructure worth checking anyway is the theme, because app embeds and any pasted snippets live there and travel with the theme rather than the domain. If you switched themes at the same time as the domain, you have two changes and one symptom, and our guide to tracking that broke after a theme or checkout change is the right place to start unpicking that.

The platform-side checklist

1. Meta: verify the new domain. Business settings, brand safety, domains, then add and verify the new domain. Verification is per domain, and until it is done your business account has no verified claim on the new one [3].
2. Meta: review the event configuration after verifying. Domain-scoped settings in Events Manager do not follow you from the old domain, so read the configuration on the new one and reproduce what you had rather than assuming it copied across.
3. GA4: exclude the old domain as a referral. Go to Admin → Data streams → Web, open the stream, Configure tag settings, Show all, then List unwanted referrals and add the old domain. Analytics then appends ignore_referrer set to true for matching events [5].
4. GA4: update the stream URL on the same screen, so enhanced measurement and the tag setup assistant point at the site that exists.
5. Google Ads: update final URLs on ads, sitelinks, and any URL rules. The redirect keeps clicks working meanwhile, but a redirect hop is latency you pay for on every click.
6. Search Console: file the change of address. It requires both properties verified under the same account, works only at domain level, does not move subdomains automatically, and forwards signals for 180 days from the day you start [4]. Set a calendar reminder for day 150.
7. Everything else with a domain field: consent management platform, email platform link domains, affiliate and partner platforms, and any allowlist a payment or fraud tool keeps.

The first hour after the switch

Minute 0 is the moment the new domain goes primary. Do the Meta verification immediately, because it is the only item on the checklist that can affect ad delivery while you are still at your desk.

By minute 15, place a real order on the new domain. Watch it in GA4 Reports → Realtime and confirm both the purchase event and the correct hostname, then open Meta Events Manager → Data sources → Test events and confirm the same order arrives against the pixel.

By the end of the hour, the referral exclusion and the GA4 stream URL should be saved, the Google Ads final URLs updated, and the Search Console change of address filed. Everything after that is watching rather than doing.

The following morning is when the referral exclusion proves itself. If the old domain is showing up as a traffic source in GA4's acquisition report, step 3 did not take, and it is a two-minute fix that gets much more annoying once a fortnight of sessions carry the wrong source. A rise in unattributed orders in those first days is expected rather than broken, for the cookie reason above, and our note on why orders arrive with no source covers how that category behaves.

What you cannot recover, and what to do instead

Nobody can hand you continuity of browser identity across a domain change. The honest plan is to accept the break and shorten it.

Two things narrow the damage. Server-side order events do not read cookies from the storefront at all: they originate from Shopify's order webhook, so they keep delivering purchases with the customer record intact through the cutover and past it. And where a shopper arrives on the new domain from an ad, the click identifier sits in the landing URL, so it can be recovered from the order itself when the browser-side capture is blocked or has not initialized yet. WeltPixel Conversion Tracking does both, which is why the purchase side of a domain migration usually reads clean while the session side does not.

That split is the thing to explain to whoever reads the dashboards, and to explain before the switch rather than after. Revenue, order counts, and platform-side conversion totals should hold, because they ride the account-scoped and server-side paths. Returning-visitor rate, cookie-based audience sizes, assisted-conversion paths, and anything measuring a shopper across more than one visit will step down at the cutover and climb back as new cookies accumulate. Write down the cutover timestamp, mark it on the charts, and compare the four weeks after against the four weeks before with that break annotated on the chart rather than argued about in a meeting. Multi-domain setups that keep both domains live have a genuinely different problem, covered in cross-domain tracking on Shopify.

FAQ

Will I lose my GA4 data when I change my Shopify domain?

No. The property, its history, its measurement ID, and its configuration are unrelated to your domain. What you lose is visitor continuity, because the _ga cookie is written from the site's own domain [2], so returning shoppers are counted as new after the switch.

Do I need to verify my new domain with Meta again?

Yes. Verification is per domain, so the new one starts unverified no matter how long the old one was verified [3]. Do it on the day of the switch so ad delivery is not interrupted, then review the event configuration in Events Manager rather than assuming it came with you.

Does Shopify redirect the old domain automatically?

Yes, once the new domain is set as primary. Other domains you own, including the .myshopify.com address, redirect to the primary, and the primary domain URL replaces other domain URLs in the browser [1].

How long does Search Console keep forwarding ranking signals?

180 days from the day you start the change of address [4]. Both properties must be verified under the same account and both must be domain-level, and subdomains need the tool run separately for each.

Will my conversion tracking app need to be reinstalled?

Not for a domain change. The app is installed against the shop, not the storefront domain, and its server-side order events do not read the storefront's cookies. Re-check the theme app embed only if you also changed themes in the same window.

The install path is unchanged too: WeltPixel Conversion Tracking keeps delivering server-side orders to its nine integrations across the cutover at $39 a month flat, with a free GA4-only plan for up to 100 storefront orders a month [7].

The number that will scare somebody first is returning visitors, and it is the one number on the dashboard that is supposed to fall. Everything account-scoped and everything server-side comes through the switch intact.

Sources

1. Shopify Help Center, "Change your primary domain", help.shopify.com/en/manual/domains/domain-type/change-primary-domain, accessed September 4, 2026
2. Google, "Advertising and measurement cookie reference" (_ga, set from the site's domain, 2 years), business.safety.google/adscookies, accessed September 4, 2026
3. Meta Business Help Center, "About Domain Verification in Business Manager", facebook.com/business/help/286768115176155, accessed September 4, 2026
4. Google Search Central Help, "Change of address tool", support.google.com/webmasters/answer/9370220, accessed September 4, 2026
5. Google Analytics Help, "Ignore unwanted referrals", support.google.com/analytics/answer/10327750, accessed September 4, 2026
6. Shopify Developer Changelog, "Checkouts will occur at the shop domain instead of checkout.shopify.com", shopify.dev/changelog/checkouts-will-occur-at-the-shop-domain-instead-of-checkout-shopify-com, accessed September 4, 2026
7. WeltPixel Conversion Tracking, Shopify App Store listing, apps.shopify.com/weltpixel-conversion-tracking, accessed September 4, 2026