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.
Yes – for the journey that matters most: from ad click to closed sale. Someone can click your ad on their phone during lunch and only become a paying customer days later on their laptop, or after a call your sales team logs in the CRM. LeadJourney is designed so that sale still lands on the original ad click.
In short
LeadJourney attributes through a click ID that is stored server-side, not a cookie tied to one browser. So a conversion reported later – from another device, your CRM, or a payment provider – is matched back to the click that started it.
Why cross-device tracking is normally hard
Most tracking lives in a browser cookie. A cookie set on a phone can't be read on a laptop – so a cookie-only tracker sees the mobile click and the desktop purchase as two different, unrelated people. The ad gets no credit for the sale it actually produced.
The deeper problem: there's no perfect way to know that an anonymous phone visitor and an anonymous laptop visitor are the same human. Any honest tool has to be clear about where it can stitch a journey together and where it can't.
How LeadJourney bridges devices
The key is that LeadJourney's anchor is a click ID captured at the moment of the click and kept on the server, not only in the visitor's browser. From there, two things connect the dots across a device switch.
1. The click ID follows the lead through your funnel
When someone clicks your ad, the click ID is created and travels with them – through the URL into your funnel, and onto the lead the moment they submit a form. That click ID is now attached to a real person in your system, independent of which browser or device they used.
2. Conversions are matched server-to-server
When the sale finally happens – maybe later, maybe somewhere else entirely – it's reported back to LeadJourney server-side:
- your CRM marks the lead as won, or
- a postback / webhook from your checkout or payment provider fires.
That report carries the click ID, so LeadJourney matches it to the original click without needing the same cookie, browser or device. (Each conversion also carries a transaction ID, so a re-fired postback is de-duplicated rather than counted twice.)
Where the device switch disappears
Because the match happens through the click ID on the server, the question "was it the same device?" stops mattering. A mobile click and a desktop (or offline) conversion become one journey as long as the click ID carried through to the conversion event.
A typical cross-device journey
- Lunch break, phone: a visitor clicks your ad. LeadJourney captures the click ID and the campaign, ad set and ad.
- The click ID follows them into your funnel and onto the lead when they enter their details.
- That evening, laptop – or three days later after a sales call: they buy.
- Your CRM or a postback reports the sale with the click ID. LeadJourney attributes the revenue to the phone click from step 1.
What it can and can't do
It bridges devices when there's a click ID to follow – which covers the journey that actually drives revenue: click → lead → sale, even when the sale lands on a different device, offline, or weeks later.
It does not guess that two anonymous visitors are the same person. If someone browses anonymously on a phone, never identifies themselves, and later buys from a fresh, parameter-free visit on a laptop, there's no shared click ID to connect them – and LeadJourney won't invent one. To get the most coverage:
- Keep the click ID flowing. Carry it through redirects and into your funnel and CRM so it's present when the conversion is reported. See cross-domain tracking for how it travels between domains.
- Report conversions server-side (CRM or postback) rather than relying only on a browser pixel that can't see the other device.
Related articles
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.
Does LeadJourney offer cross-browser tracking?
How LeadJourney keeps a journey connected when the click and the conversion happen in different browsers – for example a tap in the Instagram in-app browser, then a purchase in Safari or Chrome.