Analytics That Answer Questions Instead of Producing Dashboards

Most analytics setups measure everything and inform nothing. Start from the decision, not from the tracking plan.

Analytics graphs on a screen

Most companies have analytics installed and no idea what it is telling them. Traffic is up, bounce rate moved, the dashboard has fourteen charts, and nobody can say whether last quarter's marketing worked. The problem is that the setup started from what is measurable rather than from what is decidable.

Start from decisions

Write down the three to five decisions you make repeatedly: where to spend the next thousand dollars, which page to rewrite, whether a campaign continues. Then work backwards to the smallest set of measurements that would change those decisions. Everything else is decoration, and decoration is what makes dashboards unread.

The events worth tracking

  • The primary conversion: form submitted, call started, booking made, order placed.
  • The two or three steps immediately before it, so you can see where people stop.
  • Qualification signals: pricing page viewed, case study read, calculator used. These distinguish a browser from a buyer.
  • Micro-frustrations: rapid back-navigation, repeated failed form submissions, search with no results.

With consent banners and tracking prevention, client-side analytics undercounts - significantly in some audiences. Accept it and adjust: use the numbers for direction and comparison rather than absolute truth, keep a server-side record of the events that actually matter commercially, and stop reconciling three tools that will never agree. These are the decisions we settle in discovery before quoting a custom web application.

Reports people read

  1. One page. Five numbers, each with the previous period beside it.
  2. Every number tied to a decision someone owns.
  3. A sentence of interpretation per number. Data without a claim gets skimmed and forgotten.
  4. A monthly cadence for review, and a genuine willingness to delete metrics nobody used.
  • 3-5 decisions the setup must serve
  • 1 page of reporting
  • 0 metrics without an owner

Frequently asked questions

Do we need server-side tracking?

For commercially important conversions, it is worth it - it is more reliable and less affected by blockers and consent. For general behavioural analytics, client-side remains simpler and sufficient given you treat the numbers as directional.

How do we attribute revenue across channels?

Imperfectly, whatever tool you buy. Use last-touch for operational decisions, ask new customers how they found you as a sanity check, and treat any attribution model as a lens rather than the truth.

More on this topic: Web & Product.

Keep reading

Want this built for your business? See what we do.