Cross-Device Tracking

Browser tracking identifies a visitor with a cookie or a local identifier, and both live in one browser on one device. Nothing in the phone's Safari knows anything about the laptop's Chrome. Ad platforms bridge the gap inside their own logged-in ecosystems (a Meta user is the same person on every device Meta knows), but that knowledge stays inside the platform and never reaches your CRM or your report.

• Deterministic

  Two devices are joined when the same person identifies on both: a login, an email address in a form, a phone number on a call. Certain, and limited to the moment of identification.

• Probabilistic

  Two devices are guessed to be one person from signals like IP address, location and timing. Never certain, increasingly restricted by privacy rules, and not something to build attribution on.

For a lead generation business the deterministic route is enough, because every lead identifies at some point: the form, the call, the booking. The trick is to have kept the earlier device's journey long enough to join it when that moment comes.

1. Each device's visits are recorded first-party with their own identifier, source and click ID, and kept for months rather than a session.
2. The person identifies: a form with an email, a call with a phone number, a booking with both.
3. Every earlier visit that can be tied to that identity (an email link clicked on the phone, a return visit from a retargeting ad, a number that was called) is joined into one journey.
4. The first click on the phone gets its credit, and the CRM record carries the real source instead of Direct.

• Join a person who never identifiesA visitor who researches on three devices and never fills a form stays three visitors. That is correct behaviour under privacy law, not a gap to close.
• Reach back past the storage windowIf the phone's visit was recorded with a seven-day cookie and the form comes on day twelve, there is nothing left to join. First-party storage that lasts months is what makes stitching possible.
• See inside the platformsMeta's and Google's own cross-device matching improves their reporting, not yours. Sending your conversions back with hashed identifiers is how they learn what your CRM knows.

Cross-device tracking is not a fingerprinting trick. It is keeping each device's journey long enough, first-party, to join it to the person when they identify on a form or a call. Do that and the mobile ad click that started the deal gets its credit; skip it and half your journeys start with a laptop visit from Direct.