Cross-Domain Tracking 101: Keeping Your Google Analytics Data Intact After You Add a Custom Domain

You did everything right. You built an audience, launched a store, connected Google Analytics on Pro, and watched a clean line of sessions and sales climb week over week. Then you bought a custom domain — something short and brandable — pointed it at your store, and finally felt like a real business. A few days later, your reports look off. Sessions spike for no reason. Your best traffic source, the one actually driving sales, now reads as almost nothing. Nobody broke your analytics. This is a well-documented, entirely fixable collision between how browsers track visits and how domains work, and it trips up creators every week. Here's the fix, in plain language.

Why a custom domain breaks tracking that used to work fine

Google Analytics identifies a visitor mostly through a cookie scoped to the domain they're on. When someone lands on your storefront, clicks around, and buys, Analytics stitches all of that into one session because the cookie says same person, same domain, same visit. The instant you move your storefront to a custom domain, that cookie doesn't travel with the visitor — a fresh domain means a fresh cookie jar, even for someone who's followed you for a year. If any part of your funnel still touches the old domain — an old link in a bio, a saved bookmark, a redirect step — Analytics sees two domains touching one visit and can split it into two sessions, or attribute the sale to "direct" traffic instead of the Instagram story that actually drove it. Your reports aren't lying; they're seeing exactly what the cookies tell them, and the cookies changed addresses.

The three symptoms that mean you have a cross-domain problem

Before you touch a single setting, confirm you're actually looking at a domain-migration issue and not something unrelated. Three patterns are the classic tell.

If two or more of these apply, you're not imagining things — you're looking at exactly what happens when a domain switch isn't paired with a cross-domain tracking configuration. The good news: this is one of the more mechanical problems in analytics. There's a known fix, and it doesn't require touching your storefront's design or content at all.

The fix: telling Analytics your domains are one journey, not two

Google Analytics 4 has a built-in feature for exactly this situation, usually labeled something like cross-domain measurement inside the data stream settings of your GA4 property. What it does is simple in concept: it tells Analytics "treat visits across these specific domains as a single continuous session, and pass identifying information in the URL instead of relying purely on a domain-locked cookie." Once configured, a visitor who somehow touches both your old link and your new custom domain in the same session still gets counted once, still gets credited to the source that actually brought them, and still shows up as one coherent path to purchase instead of two disconnected fragments.

1. 1Open your GA4 property and go to Admin, then Data Streams, then select your web stream
2. 2Click into "Configure tag settings" and find the cross-domain measurement option
3. 3Add every domain that could plausibly appear in a customer's path — your custom domain and any older link you're phasing out
4. 4Save, then do a real test purchase from a fresh browser or incognito window to confirm the session stays unified
5. 5Give it 24-48 hours and check that Direct traffic has settled back down to its normal baseline

What you can't fix, and why that's okay

Be honest with yourself about one thing: historical data attached to your old domain doesn't retroactively merge with the new one. If you had three months of sessions under the old address, those numbers stay put — you won't unify them into one seamless dataset going back to day one. That's a real loss, but it's a one-time, bounded loss, not an ongoing problem. The point of setting up cross-domain tracking correctly is making sure that loss happens exactly once, on migration day, and never again. Every session from here forward should be clean and correctly attributed, once you treat the post-migration window as its own baseline.

The goal isn't a perfect unbroken line back to your very first visitor. It's making sure the line stays unbroken from today onward.— A useful reframe for anyone stressing over a one-time dip in the reports

Where this fits with the rest of your store setup

It's worth zooming out, because tracking hygiene only matters if the store underneath it actually converts and gets you paid reliably. A custom domain is a genuine upgrade — more professional in a bio, easier to say on a podcast, more trustworthy the moment someone lands on it. But the storefront still needs to do the real work: deliver digital downloads instantly, hand off course access the second payment clears, send meeting links for coaching calls automatically, and route Stripe or PayPal payments straight into your own account with no wallet to withdraw from. Google Analytics on the Pro plan is how you see which content, launches, and promotions are actually responsible for that revenue — cross-domain tracking simply keeps that visibility intact once your business looks and feels more like your own brand. Check a live example store to see what a fully dialed-in setup looks like end to end.

A five-minute post-launch check

Every time you touch your domain setup — connecting a new one, changing a redirect, or even just renewing after a provider migration — run this same quick pass. It costs almost nothing and it's the difference between catching a tracking gap on day one versus discovering it a month later when you're trying to figure out why a launch "underperformed" that actually performed fine, just invisibly.

None of this is a reason to hold off on a custom domain — it's simply the checklist that makes the upgrade clean instead of costly. If you haven't made the jump yet and you're weighing whether now's the time, the underlying question is usually less about analytics and more about whether your store is actually set up to capture the sales a sharper brand will send its way. That's worth getting right first. Read more guides on the blog, check the FAQ for setup specifics, and reach out to contact support any time a domain or tracking question doesn't have a clean answer yet.