Beyond the dashboardAI & Measurement · Independent guides
TrackingByAI Journal
← All guidesMeasurement foundations / Guide 05

Define a conversion before measuring it

The word conversion should point to a meaningful completed action, with a clear rule for when it is counted and how duplicates are handled.

Website design with web banner of order feedback on online shopping center on computer screen

First, define the question

A form submission, a payment authorization, and a fulfilled order are different milestones. A measure tied to the earliest step may be useful for diagnosing friction but should not be called revenue. Write down the event source, success condition, time window, and reconciliation method.

A measurement begins as a decision about what to observe. That decision belongs beside the resulting number, because a label alone cannot reveal the trigger, the exclusions, or the time window. The cleanest first step is a short specification written for someone who did not build the tag. It should allow that reader to reproduce the count from the same events.

The boundary of the measure

Every reported total has a boundary. Browser settings, consent choices, offline actions, and technical failures can change which events arrive. A useful report describes the visible population rather than quietly calling it everyone. When the boundary changes, annotate the chart before interpreting the new level as a change in human behavior.

A conversion can be a step in a larger process. Name the stage precisely: form accepted, payment completed, order fulfilled, or account activated. That language makes it possible to diagnose where people encounter friction without implying that an early signal has the value of the final outcome.

A small test can reveal a large definition problem. Use a clean browser, perform one action, and follow the event from the page to the final report. Repeat with an error, a reload, and a second device where relevant. This checks whether the instrumentation answers the stated question rather than merely producing a plausible dashboard tile.

Try a small example

A checkout page may fire a thank-you event twice when a browser reloads. Comparing that event with order records can expose the difference between a screen view and a completed purchase.

Before comparing periods, ask whether the product, tag, report filter, or consent interface changed. A deployment can create a discontinuity that looks like demand. Save the earlier definition and the effective date of the new one. A careful comparison may need to start a new series instead of drawing an unbroken line through two incompatible measures.

Before drawing a conclusion

A conversion rate inherits the limitations of both numerator and denominator. If either side is sampled, blocked, or defined inconsistently, the rate needs qualification.

Deduplication needs a stable transaction or event identifier and a rule for retries. A client event and a server event may both describe the same purchase. Compare them deliberately rather than adding both into one total. When a late cancellation matters to the question, decide whether the conversion report is revised or paired with a separate outcome report.

Counts and rates ask different questions. The count tells how many observed events met a rule; a rate compares that count with a denominator that must also be defined. A striking percentage is difficult to judge without the two underlying numbers. For a narrow segment, small changes to either number may produce a large movement in the rate.

A review path for this question

The result should lead to a decision that someone can name. If the report cannot change a page, a process, or a question for further review, collecting more detail may not help. A compact measure with a clear owner is easier to maintain than an extensive list of events whose purposes have been forgotten.

Three things to record

  • The exact definition or decision behind “Define a conversion before measuring it”.
  • The source and date for the information being compared.
  • At least one limitation or alternative explanation.

Write a brief interpretation in three parts: what the instrument recorded, the most plausible reading, and another explanation that remains possible. That discipline keeps an observation from becoming an unsupported claim about motive. It also makes a later correction more precise when a missing event or revised definition is found.

Use the guide as a starting point for reviewing a real service. Check the live configuration, current provider documentation, and applicable requirements before making a consequential change. If a page here is unclear or outdated, send its URL and the disputed passage through our contact route.

Continue reading

More perspectives