Cross-Device Tracking

Cross-device tracking connects the actions one person takes on different devices into a single journey. Someone reads a newsletter on their phone during a commute, clicks an affiliate link, then signs up for the product two days later on a work laptop. Without a cross-device connection, those are two unrelated visitors, and the click gets no credit.

This matters disproportionately in B2B SaaS because the buying journey is long and research-heavy. Discovery often happens on mobile through social feeds and newsletters, while signups and purchases happen on desktop. Every device switch is a point where attribution can silently break and a partner can silently lose a commission.

How it works in B2B SaaS

There are two broad approaches. Deterministic cross-device tracking joins devices through an identifier the user provides, almost always a login or an email address. Once someone signs up, every device they log in from is provably the same person. Probabilistic cross-device tracking guesses at the join using network and behavioral signals, with the accuracy problems that guessing implies.

The hard part for affiliate attribution is that the identity join usually arrives after the click. The click happens on the phone as an anonymous visitor; the identity appears at signup on the laptop. Bridging that gap requires something that travels with the person instead of the device: a coupon code they remember, a personalized link, or an email captured on the first device.

A worked example

Take a developer tools SaaS with a $100 per month plan and 25% recurring commissions. A newsletter affiliate drives 1,000 clicks a month, and roughly 60% of them come from phones. Cookie-based tracking attributes 35 trials.

The program then adds two device-independent paths: a memorable coupon code in the newsletter and a self-reported attribution field in the signup form. Attributed trials rise to 45 for the same traffic. The extra 10 were always happening; they were simply invisible because the click and the signup lived on different devices.

At a 30% trial-to-paid rate, those 10 recovered trials are about 3 paying customers, worth $75 per month in ongoing commission. For the affiliate, that is the difference between a program that seems mediocre and one worth promoting harder.

Ways to close the cross-device gap

No benchmark can tell you how much you are losing, so the practical move is to build fallbacks and measure the lift. Four work well:

• Coupon codes, the classic one: a code travels in the buyer's memory, not their browser.
• Personalized vanity links, which work the same way for partners with strong brands.
• Early email capture on the first device (newsletter signup, gated content), creating a deterministic join when that email reappears at signup.
• A simple self-reported attribution field, asking new signups where they heard about the product.

None of these are perfect; together they recover a meaningful share of broken journeys.

Cross-device tracking vs cross-domain tracking

These get confused constantly, and they solve different problems. Cross-domain tracking follows one browser across different websites, for instance from a marketing site to an app subdomain to a checkout on another domain. The device never changes; the challenge is keeping the identifier alive across domains.

Cross-device tracking follows one human across different hardware, which is fundamentally harder because browsers share nothing across devices. Fixing your cross-domain setup, which is largely an engineering task, does nothing for cross-device loss, which requires an identity join. Teams often celebrate solving the first while the second quietly keeps eating conversions.

How it shows up in affiliate and partner programs

Mobile-heavy affiliates, such as newsletter writers, podcasters, and social creators, are hit hardest, since their audiences click on phones and buy on desktops. Coupon-based attribution and personalized links exist largely to protect them. Referral programs are naturally more resilient because referral links are tied to accounts, and the referred user creates an identity at signup.

Cross-device loss is also behind a classic dispute pattern: an affiliate insists they sent 50 signups, the dashboard shows 30, and both are right.

Common mistakes

The most damaging mistake is interpreting measurement loss as performance. An affiliate whose traffic skews mobile will look weaker than one with desktop traffic even when they convert identically. Cutting the mobile-heavy partner's commission based on that data punishes them for your tracking gap.

Other frequent errors include:

• Assuming an analytics tool's cross-device reports extend to affiliate attribution, which they usually do not.
• Ignoring self-reported attribution data because it feels unscientific.
• Promising partners precise tracking without disclosing that device switches can drop conversions.

Frequently asked questions

Frequent questions about device switching and attribution.

How big is the cross-device problem in B2B?

No universal number exists, and anyone quoting one precisely is guessing. The loss depends on your audience's mobile share and how long your consideration window is. You can estimate your own exposure by comparing the device mix of clicks against the device mix of signups; a large skew suggests journeys are crossing devices.

Can I track across devices without invasive data collection?

Yes, and the boring methods are the defensible ones. Coupon codes, referral links, early email capture, and self-reported attribution all rely on information the user knowingly provides. Probabilistic device graphs raise far more privacy questions and are rarely necessary for a B2B affiliate program.

Does logging in solve cross-device attribution?

It solves it from the moment of signup onward, which is why post-signup expansion revenue attributes cleanly. It does not fix the pre-signup gap, where the click happened on a device the user never logs in from. That gap is exactly where coupon codes and email capture earn their keep.