Identity matching across devices has limits
Connecting activity across a phone and laptop can improve some analyses, but the match depends on evidence and can create privacy risk.

First, define the question
A signed-in account can provide a stronger link than a probabilistic guess based on context. Even a login may be shared, and people can use multiple accounts. A system should state which signals it relies on and whether unmatched activity is kept separate.
A measurement begins as a decision about what to observe. That decision belongs beside the resulting number, because a label alone cannot reveal the trigger, the exclusions, or the time window. The cleanest first step is a short specification written for someone who did not build the tag. It should allow that reader to reproduce the count from the same events.
The boundary of the measure
Every reported total has a boundary. Browser settings, consent choices, offline actions, and technical failures can change which events arrive. A useful report describes the visible population rather than quietly calling it everyone. When the boundary changes, annotate the chart before interpreting the new level as a change in human behavior.
Identity matching should specify whether it is deterministic, inferred, or deliberately absent. A signed-in account can link activity more reliably than a device fingerprint, but even account activity may represent a household or shared workplace. Keep the evidence and confidence of the link visible.
A small test can reveal a large definition problem. Use a clean browser, perform one action, and follow the event from the page to the final report. Repeat with an error, a reload, and a second device where relevant. This checks whether the instrumentation answers the stated question rather than merely producing a plausible dashboard tile.
Try a small example
A reader researches on a tablet and buys later on a work laptop. If no reliable common identifier exists, the report may count two people or miss the earlier visit. That does not make the purchase invalid; it limits the journey story.
Before comparing periods, ask whether the product, tag, report filter, or consent interface changed. A deployment can create a discontinuity that looks like demand. Save the earlier definition and the effective date of the new one. A careful comparison may need to start a new series instead of drawing an unbroken line through two incompatible measures.
Before drawing a conclusion
Avoid presenting an estimated identity graph as a roster of real individuals. Minimize retained identifiers and respect the choices attached to each context.
A privacy-aware analysis can use aggregate journeys when a person-level trail is unnecessary. If a join is essential, restrict access and define when the linked record expires. The ability to join data is not itself a reason to retain every identifier indefinitely.
Counts and rates ask different questions. The count tells how many observed events met a rule; a rate compares that count with a denominator that must also be defined. A striking percentage is difficult to judge without the two underlying numbers. For a narrow segment, small changes to either number may produce a large movement in the rate.
A review path for this question
The result should lead to a decision that someone can name. If the report cannot change a page, a process, or a question for further review, collecting more detail may not help. A compact measure with a clear owner is easier to maintain than an extensive list of events whose purposes have been forgotten.
Three things to record
- The exact definition or decision behind “Identity matching across devices has limits”.
- The source and date for the information being compared.
- At least one limitation or alternative explanation.
Write a brief interpretation in three parts: what the instrument recorded, the most plausible reading, and another explanation that remains possible. That discipline keeps an observation from becoming an unsupported claim about motive. It also makes a later correction more precise when a missing event or revised definition is found.
Use the guide as a starting point for reviewing a real service. Check the live configuration, current provider documentation, and applicable requirements before making a consequential change. If a page here is unclear or outdated, send its URL and the disputed passage through our contact route.


