2 September 2025
Identity Stitching Without Overclaiming Certainty
How to talk about linked devices in stakeholder meetings when deterministic IDs are partial and probabilistic matches are imperfect.
Product leads want a single number for “users who finish on a second device.” Analysts know that number depends on how aggressively you stitch anonymous visits to logged-in accounts. The tension shows up when marketing reports a higher cross-device conversion rate than product sees in account-level logs.
A workable habit is to publish two figures side by side: confirmed same-account handoffs, and probable same-person handoffs based on shared device graphs. Label both clearly in every slide. Stakeholders then argue about thresholds instead of accusing the dashboard of lying.
When deterministic coverage is thin—common for guest checkouts—document the share of journeys you simply cannot join. That honesty keeps roadmap debates grounded. Cross-device analysis is still valuable; it just needs an explicit confidence band.
If you are preparing a Cloudroutebase audit, bring both confirmed and probable definitions. We will map which decisions require certainty and which can tolerate a provisional link.