Conversion tracking, explained without the jargon

It comes up on almost every project, usually later than it should. Here is conversion tracking without the vocabulary that usually surrounds it.

Measurement is only useful when someone has agreed in advance what they would do differently. Assume whoever inherits this will have half your context and none of your patience.

The short version

If you cannot measure it, you cannot improve it. This is the sort of thing that compounds, quietly, in both directions. Write the reasoning down alongside the decision, because the reasoning is what changes first.

Why people complicate it

Most of the confusion comes from tooling rather than from the idea itself. That sounds obvious written down. It is still the thing most often skipped.

Track the actions that map to revenue. The cost of getting this wrong is rarely visible on the day it happens. The version that survives contact with a real deadline is the simple one.

Turning this into a decision

Test that the tracking fires before relying on it. It is worth being explicit about, because assumptions differ quietly. It is worth deciding this deliberately rather than inheriting whatever the last person set up.

In practice

More dashboards rarely produce more decisions. Three things worth confirming about conversion tracking before you move on:

• Someone can say what the current setup is without going to look
• Test that the tracking fires before relying on it — 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.