Beyond the dashboardAI & Measurement · Independent guides
TrackingByAI Journal
← All guidesMeasurement foundations / Guide 10

Cross-device journeys are easy to overstate

A journey chart is a constructed view of events. It may omit offline steps, other browsers, and moments when a person chooses not to be tracked.

Man in a hoodie using a new smartphone and laptop on a sofa, indoors.

What the system can observe

Journey analysis needs a clear unit: an account, a browser, a device, or a modeled person. It also needs rules for ordering, timeouts, and incomplete paths. A tidy funnel can conceal users who enter at a later step or return after the chosen window.

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.

Where the comparison begins

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.

Funnels are often displayed only for completed paths. Check how the report handles a person who skips a step, starts elsewhere, or returns after the cutoff. A path visualization is a selection rule over observed events, and that rule should be documented.

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.

A practical test

If a service reports that everyone followed the same three-step path, inspect whether the chart includes only people who completed all three steps. That selection can make the path look more universal than it is.

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.

Keep the uncertainty visible

A missing event is not proof that an action never happened. Label observed paths as observed and explain what the instrumentation cannot see.

Use a few manually reviewed paths to test the chart. Include a mobile-to-desktop case, a blocked-script case, and a person who abandons and later returns. If the report cannot represent them, describe the omission rather than implying the displayed path is universal.

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 “Cross-device journeys are easy to overstate”.
  • 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.

Continue reading

More perspectives