How do I attribute revenue when a prospect converts on mobile after earlier desktop engagement?
Quick Answer: Attribute revenue by stitching the desktop and mobile sessions into a single person-level journey using first-party identity resolution, then assign conversion credit based on the touchpoints that influenced the deal before the mobile conversion. In practice, that means capturing a persistent lead ID from the first desktop visit, passing it into your CRM and analytics stack, and using a multi-touch model—preferably time-decay or data-driven attribution—to avoid over-crediting the final mobile conversion event.
Detailed Explanation
When a prospect first engages on desktop and later converts on mobile, the core problem is not channel attribution—it is identity continuity. To measure revenue accurately, you need to connect anonymous and known behaviors across devices using first-party identifiers such as email capture, CRM lead IDs, or authenticated sessions, then reconcile those events inside a unified reporting layer. Once the journey is stitched together, revenue should be assigned with a multi-touch model that reflects both the initial desktop engagement and the final mobile conversion, rather than last-click crediting the mobile session alone. This is especially important in B2B and high-consideration sales cycles, where desktop often drives research and mobile closes the loop; without cross-device identity resolution, your CAC, channel ROI, and campaign-level revenue reporting will be systematically distorted.
Key Technical Drivers
- Implement first-party identity resolution: capture a durable lead key on the first desktop visit and persist it through CRM, CDP, and analytics events so mobile conversions can be matched back to the same person.
- Use multi-touch attribution, not last-click: apply time-decay or data-driven models to distribute revenue across desktop research, retargeting, email, and the final mobile conversion touchpoint.
- Normalize reporting at the person and opportunity level: join web sessions to pipeline records in your CRM so attributed revenue reflects the full conversion path, not isolated device-specific sessions.