Products Solutions Templates Pricing Resources

Cross-device conversion attribution: tracking visitors across devices

Home / Everything About / Everything About Analytics / Cross-device conversion attribution: tracking visitors across devices

A prospect starts on mobile. They browse your product. They leave. Hours later they come back on desktop. They read more details. They still do not convert. Two days later they search for you on a tablet. They visit again. Finally they come back on their laptop and convert. Your analytics sees three separate visitors. One mobile visitor. One desktop visitor. One tablet visitor. No conversion from any of them individually. But they are the same person. They converted from a combined experience across all devices. Cross-device attribution connects these pieces. It recognizes that the same person used three devices. It tracks their complete journey. It shows that all three devices contributed to the conversion. Without cross-device attribution, you see fragmented journeys. You do not know which devices actually work together to drive conversions. With it, you understand the complete customer path. This article explains cross-device attribution and how to track visitors across devices.

Why cross-device tracking matters

Most customers use multiple devices. They browse on phone while commuting. They research on laptop at work. They purchase on tablet at home. Your analytics without cross-device tracking sees these as separate visitors and separate sessions. You do not see that the phone browser and laptop researcher and tablet purchaser are the same person. You do not understand the role each device played. Cross-device tracking stitches these sessions together into one journey. It shows you the complete picture.

How cross-device attribution works

Cross-device attribution matches sessions from different devices to the same user. It does this through user IDs. When a visitor logs in, you know who they are. You can assign them a user ID. Every session they have on any device is tagged with that ID. Sessions become a continuous journey instead of separate islands. A visitor browses on mobile, then logs in on desktop. Both sessions are connected through their user ID.

Signed-in vs unsigned-in tracking

Signed-in users are easy to track across devices. They log in on mobile, then log in on desktop. Both sessions are linked to their user ID. Unsigned-in users are harder. They browse on mobile without logging in. Then they browse on desktop without logging in. How do you know it is the same person? Some platforms use probabilistic matching. They look at signals like IP address, location, time, device type. If a mobile user and desktop user have matching signals, they might be the same person. It is not perfect but it is better than nothing.

Device sequences in conversion paths

Track the sequence of devices used before conversion. Do customers typically start on mobile and end on desktop? Or the reverse? Do they use three devices or two? Understanding device sequences shows you the typical customer journey. A SaaS company might find that customers always start on mobile for research, then switch to desktop for signup. This sequence is valuable information. Mobile needs to inform and engage. Desktop needs to convert.

First-touch and last-touch by device

Knowing which device delivered the first touch and which delivered the last touch is valuable. Mobile might deliver first touch (awareness). Desktop might deliver last touch (conversion). Both are valuable. Mobile for awareness. Desktop for conversion. Do not optimize mobile for conversion if mobile's job is awareness. Optimize it to move people forward in the journey.

Cross-device conversion value

A mobile session might have low direct conversion. But if most conversions are preceded by mobile sessions, mobile is valuable. Its value is in assisting, not converting. Cross-device attribution shows you this. It shows you which devices assist and which convert. Allocate budget accordingly. Budget for devices that convert. Budget for devices that assist because they support the converting devices.

Privacy and cross-device tracking

Cross-device tracking requires linking user data across devices. Privacy regulations like GDPR and CCPA restrict this. Get user consent before tracking across devices. Use first-party data (logged-in users) when possible. This is less invasive than probabilistic matching. Respect user privacy while building understanding of customer journeys.