Test what survives your domain hop
Walk the journey that crosses to your checkout or booking domain, then paste the URL you started on and the URL you landed on. This checks what survived — the linker parameter, the click identifier, the UTMs. Reading the arrival URL is the only thing that actually proves cross-domain linking works; a configuration screen showing both domains listed proves only that someone typed them in.
Free30 minutesNo obligation
Test a cross-domain hop
Walk the journey that crosses to your checkout or booking domain, then paste the URL you started on and the URL you landed on. This checks what survived the hop — the linker parameter, the click identifier, the UTMs — which is the only thing that actually proves cross-domain linking works. A configuration screen doesn't.
Paste both URLs from a real journey. Everything happens in your browser. Nothing is sent anywhere.
Cross-domain tester · what breaks
What this tool is for — Cross-domain tester
- 01
Your own domain is a top referrer
The signature symptom of a broken hop.
- 02
Checkout is on another domain
And revenue isn't attributing to campaigns.
- 03
You configured linking
And want evidence it works.
Cross-domain tester · the fix
What you get out of it — Cross-domain tester
A survival verdict per parameter
Linker, click IDs, UTMs.
Confirmation the hop happened
Same-host pairs are flagged.
A referral exclusion reminder
Because linking can work and self-referral still ruin attribution.
Cross-domain tester · architecture
Why domain hops break attribution structurally
This isn't a bug in anything. It's how browsers scope storage, and no amount of configuration inside one domain changes it.
- 1
Cookies are scoped per domain
The checkout domain cannot read the cookie your site set. That's the security model working correctly.
- 2
A new session credits your own site
The purchase appears to come from a visitor who arrived from your homepage, so the campaign gets nothing.
- 3
Redirects eat parameters
A shortener or login bounce in the middle drops the linker silently, and a clean test path won't show it.
- 4
Some checkouts can't be tagged at all
Hosted payment pages and booking engines often allow nothing, and then only a server-side path reaches them.
Cross-domain tester · diagnose
What this tool cannot tell you — Cross-domain tester
Stated up front, because a tool that implies more confidence than it has is worse than no tool. These are checks you have to run yourself.
- 01
Whether linking is configured
It reads the result. If the parameter is missing, configuration is one of several possible causes.
- 02
Which redirect stripped it
Follow each hop individually — the tool sees only the endpoints.
- 03
Whether referral exclusions are set
That's an analytics setting and it always warns you to check it.
- 04
Whether the second domain can be tagged at all
Ask the provider. It changes the whole approach.
Cross-domain tester · prove
How to confirm the result — Cross-domain tester
Against your own records, not against the tool's output.
Source of truth
your backend order records, with the original click ID attached
- Linker parameter confirmed present on arrival.
- Every redirect in the real path tested individually.
- Self-referral revenue reduced to near zero.
- A live conversion walked end to end across both domains.
- Reconciled over a fully closed window, matched per record rather than on totals.
- Re-checked after your next site release, which is when most breaks happen.
Cross-domain tester · free audit
What we check in the free audit
- Whether linking is configured
- Which redirect stripped it
- Whether referral exclusions are set
- Whether the second domain can be tagged at all
Checked against
your backend order records, with the original click ID attached
Free30 minutesNo obligation
Cross-domain tester · when not to buy
Why this isn't gated — Cross-domain tester
There's no email form in front of it, and that's deliberate.
- A tool you have to pay for with your contact details is a lead form wearing a costume. If this is useful, it should be useful without a transaction.
- Everything it does runs in your browser. There is no endpoint, so there is nothing for us to collect even if we wanted to — open your network tab and check.
- It will tell you when you don't have a problem. That outcome costs us a sale and happens regularly, which is the point of publishing it rather than putting it behind a call.
- If it does find something and you'd rather fix it yourself, the reference pages on this site cover the how. Hiring us is one option, not the conclusion.
Cross-domain tester · what we deliver
What it checks — Cross-domain tester
The _gl linker parameter
Present on arrival, which is the evidence linking fired.
Click identifiers
Anything present on departure and absent on arrival.
UTM parameters
Less serious, still fragmenting.
Host difference
Confirms an actual cross-domain hop occurred.
Pricing
Pick the package that fits your ad spend
Browser-side starter
$400One-time fee · lifetime ownership
If the tool found something and you'd rather not fix it yourself: we repair the root cause in your existing setup and verify it on a live conversion.
- Root cause fixed, not worked around
- Verified on a live conversion
- Reconciled against your own records
- Written handover
1st-party server-side
Recommended$800One-time fee · most popular
Removes the class of failure rather than the instance. Money events from your own records through a first-party container on your subdomain.
- First-party server container on your own subdomain
- Events from your records, not the browser
- Deduplicated on a shared event ID at every destination
- First-party cookies beyond Safari's 7-day cap
- 95%+ accuracy and 8+ Meta EMQ, guaranteed in writing
Full 1st-party stack
$1,800One-time fee · lifetime ownership
Every paid channel server-side plus the offline loop, with monitoring so the next break surfaces in days rather than at quarter end.
- Everything in 1st-party server-side
- Pinterest, Snapchat, Reddit and LinkedIn CAPI
- CRM and offline conversion loop
- Refunds and cancellations corrected wherever each platform allows it
- Monitoring on every destination
FAQ
Cross-domain tester questions, answered
Because the second domain saw a visitor arrive with no prior session. That's the textbook cross-domain symptom.
Either linking isn't configured for this pair, or a redirect in between stripped it. Follow each hop individually to find out which.
Then the conversion has to come from the order record server-side, with the click ID captured before the visitor left your site.
No — an iframe isn't a navigation, so there's no arrival URL to paste. Iframes need a different approach entirely.
Free · 30 min
Fix attribution across your checkout domain
WhatsAppFree30 minutesNo obligation
