The real cost of ignoring mobile analytics
We end up explaining this on discovery calls often enough that it deserved writing down. Nobody bills you for neglecting mobile analytics. The cost shows up somewhere else.
Mobile releases are slower to correct than web ones, so the cost of shipping a mistake is higher. The version that survives contact with a real deadline is the simple one.
Where the cost lands
- Time spent on work that should not have been necessary
- Enquiries that quietly never arrive
- Session data on mobile is noisier than on the web
- Rework, once the problem is finally visible
Track flows, not screens. It is worth being explicit about, because assumptions differ quietly. If two people in the business would answer this differently, that gap is the actual problem.
Where to go from here
Respect platform privacy rules or you will be removed. None of that requires a large budget, only a decision and someone to own it. Budget a little time for it every quarter and it never becomes a project of its own.
What this looks like day to day
The version of the app your customers are running is rarely the one you just shipped. Three things worth confirming about mobile analytics before you move on:
- Someone can say what the current setup is without going to look
- Respect platform privacy rules or you will be removed — and you know whether that is true here
- There is a way to tell whether the last change to this helped
The point is not perfection, it is knowing which of these you have consciously chosen to skip.