The playbook
Thank You Pages: Metrics and Measurement
Measure thank you pages by defining confirmed actions matched to records precisely enough that two people can reproduce the result from the same records. Keep the reporting unit, date basis, and scope visible. Without those definitions, a change in the report may reflect a changed calculation rather than a changed customer outcome.
Put the task in context
Confirm the submitted action and explain the next step. If a form failed to reach the backend, show a recoverable error instead of the same success page. Repeatedly refreshing confirmation should not generate another customer record or another counted purchase.
Create a metric definition
| Definition field | What it must explain |
|---|---|
| Measure | confirmed actions matched to records |
| Unit | What one page or interaction record or completed outcome represents |
| Included records | The scope identified by completed action and reference |
| Date basis | The event date or period used to include a record |
| Exclusions | Tests, duplicates, or other records outside the agreed definition |
| Source owner | site owner |
Separate delivery checks from outcome measures
A delivery check asks whether the team completed a specific task, such as clearly state which action succeeded. An outcome measure asks what happened for the user or business afterward. Keep both visible. Completing the task is useful evidence of execution, but it does not by itself prove that the broader outcome improved.
Worked arithmetic example
Suppose an illustrative review includes 80 eligible records, and 60 satisfy the explicitly defined completion condition. The completion share is 60 ÷ 80 × 100 = 75%. This is hypothetical arithmetic, not an industry benchmark or a predicted improvement. It describes only the population and condition you defined.
For thank you pages, explain the condition before applying that calculation. If the question is whether the team can avoid counting reloads as new business outcomes, a record counts only when the evidence demonstrates that condition. Do not replace missing outcomes with successful ones just to complete a report.
Compare like with like
Keep the scope, date basis, and exclusions consistent between observations. If reference changes meaning between periods, note the change and rebuild a comparable view where possible. A rate can also move because the composition of the underlying group changed, even when individual performance did not.
Investigate an unexpected result
- Check whether the underlying completed action records are complete.
- Look for this known failure: displaying success before the backend has accepted the request.
- Verify that the process still includes: explain response timing and preparation where relevant.
- Reconcile a sample with the original record before changing the operating plan.
Use the report to choose an action
If the evidence supports a correction, tie confirmation to a verified completion response. Record when the change occurred and what should be checked next. Keep uncertainty visible when the sample is small or the observation period is incomplete. The purpose of measurement is a better decision about confirmed actions matched to records, not a favorable-looking number.
Verify the actual visitor journey on a narrow screen and with a keyboard. A design can look complete while hiding an unreachable control or a missing confirmation. Record the task attempted and what happened at the end.
Skip the manual steps. Let AgentixHUB run this for every client.
Start now