Measurement / calculator / Free to use
Agentic Checkout Outcome Coverage Calculator
Calculate known and unresolved outcomes for one matched checkout cohort, with clear boundaries and no customer data.
Growthcraft Editorial · 2026-10-29. AI-assisted research and implementation. Examples are synthetic; Akshay's personal review is not claimed.
Enable JavaScript to change inputs in the interactive calculator. The complete formulas, default example and limitations are available below.
Define one cohort first
Enter unique checkout starts and three mutually exclusive outcomes for the same surface, window and maturity cutoff. This local calculator cannot verify event identity, consent, data completeness or deduplication. Use the reconciliation worksheet to record those checks.
Formula and synthetic example
Known-outcome coverage = 100 × (confirmed orders + confirmed not completed) ÷ checkout starts. Confirmed-order share and unresolved share each use that same denominator. The three outcome counts must add exactly to the checkout starts; with zero starts, each percentage is undefined. For 100 starts, 70 orders, 10 confirmed not completed and 20 unresolved, coverage is 80%, confirmed-order share 70%, and unresolved share 20%.
What this can and cannot say
A high coverage percentage shows that outcomes were classified within the supplied cohort; it does not prove tracking is complete or that orders were caused by an agent. An unresolved attempt is not a failed purchase. Refunds, partial payments, multiple currencies, cohort selection and unobserved checkouts require separate analysis. Do not enter customer identifiers or confidential records.
Investigate the gaps
Compare event names and maturity cutoff, inspect transfer boundaries, resolve uncertain outcomes through authoritative merchant records, and assign each mismatch an owner. Read the implementation guide or discuss the workflow.
Sources and boundaries
Checked 29 October 2026: Google UCP analytics distinguishes native checkout from transfers and says its report does not track activity on the merchant site after a transfer. The Google Merchant Reports API UCP report is alpha; its documentation advises separating count-only queries from currency-valued measures to avoid missing or split rows. Shopify's 16 October buyer-consent update applies when the capability is negotiated; validate actual integration and applicable permissions. The framework and examples are original editorial synthesis, not an official specification.