The real cost of ignoring analytics setup

Every audit we run turns up some version of this. Nobody bills you for neglecting analytics setup. The cost shows up somewhere else.

More dashboards rarely produce more decisions. The practical test is whether someone new to the project could tell, in a minute, that it had been handled.

Where the cost lands

• Time spent on work that should not have been necessary
• Enquiries that quietly never arrive
• Data you do not trust is worse than none
• Rework, once the problem is finally visible

Filter internal traffic from day one. There is a version of this that is over-engineered, and it is worth avoiding. Check it against what you would want a competitor's site to get wrong.

What to do next

Decide what you will act on before you track it. That sounds obvious written down. It is still the thing most often skipped. Budget a little time for it every quarter and it never becomes a project of its own.

In practice

Data you do not trust is worse than no data, because it gets quoted anyway. Three things worth confirming about analytics setup before you move on:

• Someone can say what the current setup is without going to look
• Filter internal traffic from day one — and you know whether that is true here
• There is a way to tell whether the last change to this helped

If any of that sounds like a description of your current setup, it is fixable.