12 August 2026
One adoption language, without forcing every platform to match
A useful cross-platform view starts with shared decisions, not identical event names.
Web, mobile and desktop products rarely behave in exactly the same way. Treating them as interchangeable produces tidy dashboards and weak decisions. Begin instead with the behaviour you need to understand: first value, repeated value, movement between devices and meaningful return.
Define the decision first
Write down what a product team would do differently if adoption rose or fell. That question gives each metric a job. A shared definition of activation can then allow platform-specific evidence while preserving comparability.
Keep the exceptions visible
Document where offline use, store releases, permissions or account state alter the journey. Exceptions should be part of the model, not notes hidden beneath a chart. This makes review conversations faster and prevents teams from treating instrumentation differences as customer behaviour.