What cross-device tracking is
Analytics identifies a browser, not a person. Each phone, laptop and browser gets its own visitor ID. When someone clicks your Instagram ad on their phone, then comes back on their work laptop a week later to buy, a tool without cross-device tracking sees two strangers: one mobile visitor from Instagram who never paid, and one desktop visitor who arrived direct and paid.
That breaks attribution. The ad gets no credit, direct gets too much, and mobile looks like a channel that never converts.
How devices get linked
- Deterministic: a login. When a user signs in, your app tells the analytics tool their user ID. Every device they sign in on joins the same profile. This is accurate and the method to rely on.
- Email at checkout. A purchase made with the same email as a known user can be joined to their earlier visits.
- Probabilistic matching. Guessing from IP address, location and device traits. Ad networks use it at scale; for your own analytics it is error-prone and harder to justify on privacy grounds.
A related problem is cross-domain tracking: the same device moving between your marketing site and an app on a different domain. That one is solved by passing an ID in the link, not by logins.
How to set it up
- Call identify with your own stable user ID on every sign-in and signup, from each platform you have.
- Sign the identify call on your server, or send it from your backend, so nobody can claim another user's ID.
- Reset the identity on sign-out, so the next person on a shared device doesn't join the previous profile.
- Pass the visitor ID to checkout, so payments link to a device even before login.
Common mistakes
- Using an email as the user ID. Emails change; use your database ID.
- Identifying only in the web app. Mobile apps and the marketing site need the same user ID.
- Expecting anonymous visitors to merge. Visits on a device that never signs in stay separate.
- Forgetting shared devices. Without a reset on sign-out, two people become one.
How MetricRaven tracks across devices
MetricRaven links devices through identify. Pass your user ID from the browser (unsigned, marked unverified), from the browser with a token your server signed, or from your backend with the secret key; the npm package and the iOS, Android, React Native and Flutter SDKs have the same call. Goals, payments and visits on every linked device join one journey, and a customer is credited to their earliest tracked visit across all of them (first-touch attribution).
Payments link to a visitor when checkout passes the visitor ID or the user has been identified. Devices that are never identified stay separate: in Paths to payment, a customer seen on two devices counts as two paying visitors, with their revenue counted once. Separate domains of one site are joined by cross-domain tracking.
Questions
- How does cross-device tracking work?
- Most reliably through logins. When a user signs in on a device, the app sends their user ID to the analytics tool, which joins that device's visits to the same person.
- Why does cross-device tracking matter for attribution?
- Many people discover a product on their phone and buy on a computer. Without linking the devices, the purchase looks like a direct visit and the channel that found the customer gets no credit.
- Is cross-device tracking possible without a login?
- Only by guessing from signals like IP address and device traits, which is unreliable. An email at checkout can join a purchase to a known user; otherwise devices stay separate.
- What is the difference between cross-device and cross-domain tracking?
- Cross-device joins one person on several devices, usually through a login. Cross-domain keeps one device's visit going when it moves between your own domains, usually through an ID in the link.