Why mobile analytics matters more than it looks

Every audit we run turns up some version of this. Mobile analytics is easy to treat as a detail, and that is exactly why it is worth a few minutes of attention.

You do not control the device, the network, or the operating system version, and the design has to accept that. Budget a little time for it every quarter and it never becomes a project of its own.

Why this earns attention

Session data on mobile is noisier than on the web. There is a version of this that is over-engineered, and it is worth avoiding. If it only works because one person remembers to do something, it does not work yet.

Track flows, not screens. None of that requires a large budget, only a decision and someone to own it. It is worth deciding this deliberately rather than inheriting whatever the last person set up.

Where it usually goes wrong

Respect platform privacy rules or you will be removed. There is a version of this that is over-engineered, and it is worth avoiding. The practical test is whether someone new to the project could tell, in a minute, that it had been handled.

In practice

Mobile releases are slower to correct than web ones, so the cost of shipping a mistake is higher. Three things worth confirming about mobile analytics before you move on:

• Someone can say what the current setup is without going to look
• Track flows, not screens — and you know whether that is true here
• There is a way to tell whether the last change to this helped

None of this needs a rewrite. Most of it is a morning's work once someone decides to do it.