Does LeadJourney offer cross-domain tracking?
How LeadJourney keeps a visitor's journey connected when it spans more than one domain – your marketing site, a separate funnel and a checkout on its own domain.
Yes. LeadJourney is built to follow a visitor across more than one domain – for example from your marketing site, to a funnel on a different domain, to a checkout that lives on its own domain. The journey stays connected, so the lead and the revenue still land on the ad that started it.
In short
Cross-domain tracking works because LeadJourney's anchor is a click ID, not a per-domain cookie. As long as that click ID travels with the visitor from one domain to the next, every step belongs to the same journey.
Why cross-domain tracking is normally hard
Browser cookies are first-party – they belong to a single domain and can't be read on a
different one. So the moment a visitor crosses from yourbrand.com to yourcheckout.com,
a cookie-based tracker loses the thread and starts a brand-new, anonymous session. The ad
click and the sale end up looking like two unrelated people.
LeadJourney avoids that in two ways.
How LeadJourney solves it
1. The tracking script is first-party on every domain
You install LeadJourney from a tracking subdomain on your own website (a CNAME that
points to package.leadjourney.io). You can do this on each domain you own. That means
LeadJourney runs first-party everywhere – it's more resilient to ad blockers and browser
restrictions than a third-party tag, on every site in your funnel.
2. The click ID travels in the URL
The real magic is the click ID. When someone clicks an ad that points at your LeadJourney tracking link, a click ID is created and attached to that visitor. When you send them on to the next domain, the click ID rides along in the URL:
https://yourcheckout.com/?click_id=8f3c… ← carried across the domain boundaryThe LeadJourney script on the next domain reads click_id (and any lj_* campaign
parameters) straight from the URL and continues the same journey instead of starting a new
one. Because the ID is in the link rather than in a cookie, the domain change doesn't break
anything.
The one thing you need to do
When you link from one of your domains to another, pass the click ID along in the URL.
Append ?click_id=<the visitor's click id> (and keep any lj_* parameters) to the
destination link. That single step is what keeps the two domains on the same journey.
A typical multi-domain journey
- A visitor clicks your ad → LeadJourney creates a click ID and records the campaign,
ad set and ad from the
lj_*parameters. - They land on
yourbrand.com, browse, then click through to your funnel onfunnel.com– the click ID is carried in the link. - They reach the checkout on
checkout.comand submit a form – the lead is tied to the same click ID. - The sale is reported back (via your CRM or a postback) – matched to that click ID.
Three different domains, one connected journey, and the revenue is attributed to the exact ad that earned the click.
What to keep in mind
- Install the script on every domain in the journey – the marketing site, the funnel and the checkout should each load LeadJourney first-party.
- Carry the click ID across every hop. If a link to another domain drops it, the journey restarts as anonymous on the new domain.
- Subdomains are easy (
shop.yourbrand.com). Genuinely separate domains (yourcheckout.com) are where passing the click ID in the URL matters most. - You stay responsible for your own cookie/consent setup on each domain.
Related articles
Where do I find my Workspace ID?
Your Workspace ID identifies your workspace to LeadJourney's Conversion API and webhooks. Here's exactly where to find and copy it.
Does LeadJourney offer cross-device tracking?
How LeadJourney keeps a click on one device connected to a conversion that happens later on another – on the phone, then the laptop, or closed offline in your CRM.