Not with cookies — device switching is precisely what browser tracking cannot survive. A server-side journey record can, because it identifies returning visitors across sessions instead of storing state inside one browser.
Why Device Switching Kills Cookie Attribution
The majority of considered purchases now start on one device and finish on another. Each switch severs the tracking chain:
- Cookies Are Per-Browser: A cookie set in mobile Safari does not exist in desktop Chrome, so the desktop session starts "anonymous."
- Ad Click IDs Don't Transfer: The gclid or fbclid captured on the phone cannot be read by a different laptop's cookies.
- Privacy Features Accelerate the Split: ITP and ETP shorten cookie life so even same-device journeys break within days.
The purchase that finally happens on the work laptop looks like organic direct traffic — the Reddit or Meta ad that started everything gets nothing.
| Tracking Method | Survives Device Switch? | Survives 30+ Days? |
|---|---|---|
| First-party browser cookie | No | Rarely (ITP caps at 7 days for many) |
| Ad platform click ID in URL | No (single click) | No |
| Server-side signed journey | Yes — visitor-linked, not browser-linked | Yes — 90-day persistence |
How to Follow Buyers Across Devices
- Anchor the Journey Server-Side: Store the ad click and journey events on the server, keyed to the visitor rather than the browser.
- Re-identify on Return Visits: When the same buyer reappears from another device, their visits attach to the existing signed journey.
- Close With Payment Verification: When they finally pay — on any device, on any domain — the verified receipt completes the original journey.
- Report to the Source Platform: The original ad click receives the conversion credit it earned.
Deep Conversions anchors journeys server-side so the phone research session and the laptop purchase stay one connected, payment-verified path.
Track Cross-Device Buyers →Frequently Asked Questions
Is cross-device identification privacy-compliant?
Yes — identification happens in a first-party context on properties you control, with signed tenant-scoped records and configurable retention, consistent with GDPR/CCPA requirements.
What if the buyer never returns to my site before paying?
If the payment completes through a connected provider webhook, the verified receipt still closes the journey that the original click opened.
Does this also connect logged-in SaaS users?
Yes — logged-in users are the easiest to connect because their identity is already first-party verified on both devices.