Only an observation your own tools actually record for one named step, inside a window you can state, with the denominator, duplicates, and exclusions written down. Google's ecommerce guide says begin_checkout, add_payment_info, and purchase are events you send. WooCommerce's order-status guide describes store records such as Pending payment, Processing, On hold, and Failed. Those are different observations. A missing browser event can mean the event was not sent. Google's consent-mode guide says tags adjust their behavior where consent banners are required, so consent is an exclusion to record, not proof that the step failed. The missing event is not, by itself, a provider decline. You can decide whether the records you have define one step. Your provider decides whether a payment failed. A rate stays unknown until both counts are the same kind of observation. Describe the work you need. Prism will confirm scope, responsibilities, fees, and terms before work begins.
For: An owner or authorized representative of a business that sells peptides for laboratory research use only and wants to test a belief that one checkout step is failing.
Updated 2026-09-21
Name one step before you count anything
A belief that checkout is failing is not yet a measurement. Name the action: the buyer opened checkout, submitted payment details, or the store recorded a paid order. Google's measurement guide says you measure the first checkout step by sending begin_checkout, and you send add_payment_info when payment information is submitted. Its purchase section says you measure a purchase by sending a purchase event. If your implementation does not send the event, that event cannot support the belief.
Keep this page on the quality of the observation. It does not decide which control the checkout should show, and it does not explain why an authorization, a capture, and a bank deposit can disagree. Those are separate questions. A support complaint can suggest where to look. It is not the count.
A browser event and a store order are not one count
WooCommerce's order-status document describes records the store keeps. Pending payment means the order was received and payment has not been made. Processing means the store has recorded payment as received and the order is awaiting fulfillment. On hold can mean confirmation is still outstanding, including a delayed-notification payment method or a gateway that separates authorization from capture. Failed means the store recorded the payment as failed or declined, and the same document says that status may not appear immediately when confirmation is delayed.
None of those statuses is a Google Analytics event. A purchase event is not a WooCommerce Processing order unless you have checked that your implementation sends the event when that order is created. Do not add the two numbers together, and do not use one as the denominator of the other, unless you have shown they count the same action.
A missing event can be a measurement gap
Google's recommended-events article says you should send those events, with their prescribed parameters, to get the detail in your reports. Sending is an implementation choice. The consent-mode guide says consent mode lets you control data collection based on consent, and that Google tags adjust their behavior where consent banners are required. It also describes avoiding a loss of measurement where banners do not apply. A report that excludes events for either reason is not a count of buyers who failed a step.
Write the exclusions you know: consent not granted, a filter on the report, a checkout path that does not send the event, or an order status your export left out. If you do not know whether the tag ran, the cause of the gap is unknown. Do not fill that unknown with a code change or a processor rule.
Calculate a rate only when the two counts match
A count of purchase events over a week is a count. It becomes a completion rate only if you also have a count of the prior step, for the same days, in the same tool, after the same exclusions. The refund example's comment says transaction_id is required for purchases and refunds. That comment does not say your property drops a repeated identifier. Until you verify the duplicate rule, you can report the count and you cannot report a rate of distinct orders.
If the numerator is a browser event and the denominator is a store export, leave the rate blank. The worksheet is where that incompatibility is recorded. It is not a place to borrow a benchmark.
What you can decide, and what stays unknown
You can decide that the evidence is strong enough to describe one step, or that it is not. You can take a completed definition to a consultation: the step, the event or status, the window, and what the count cannot prove. Prism's solutions page offers a review of website content, preparation for a card-processing discussion, or help with a provider's website questions. Confirm any requested measurement or investigation scope separately. The contact page says the team follows up by email and that the request does not submit a processing application.
Your provider decides whether a payment was declined and what, if anything, should change in the account. Whether a particular tag is installed on your theme, and how your analytics property treats duplicates, are unknown until someone with access to that property checks them. Do not send card numbers, passwords, or customer lists with the question.
Checkout measurement definition
Define one suspected step from records you already have. Leave a row blank when you do not know it. Do not write a rate in the count row unless the denominator row uses a compatible count from the same window. Worksheet entries are not submitted by this worksheet or saved by this site. Use only non-sensitive summaries; do not enter credentials, government identifiers, card or bank-account numbers, private receipt links, or customer details.
Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.
Checkout measurement definition. The last column is for temporary notes.
Part
What must be true before you use it
Where the figure has to come from
Your record
The step you believe is failing
What must be true before you use itName one action, such as opening checkout, submitting payment details, or the store recording payment. A general complaint about checkout is not a step.
Where the figure has to come fromThe screen, button, or order status your staff can point to.
The observation that represents it
What must be true before you use itGoogle's guide treats begin_checkout, add_payment_info, and purchase as events you send. WooCommerce's status guide treats Pending payment, Processing, On hold, and Failed as store records. Use the one your system actually keeps.
Where the figure has to come fromThe event name or order status, and the tool that stores it.
Time window
What must be true before you use itA count needs a start and an end before it can be compared with any other count.
Where the figure has to come fromThe report's date range and the timezone that report uses.
Denominator
What must be true before you use itA rate needs a second count of the same kind of observation, for the prior step, over the same window. A browser event and a store export are not automatically compatible.
Where the figure has to come fromThe earlier event or order count. Leave the rate uncalculated if this row is unknown.
Duplicates
What must be true before you use itThe refund example comments that transaction_id is required for purchases and refunds. It does not state that your property suppresses a repeated identifier.
Where the figure has to come fromThe property setting or export rule you verified. Write unknown if you did not verify it.
Known exclusions
What must be true before you use itConsent settings, report filters, and a path that never sends the event remove observations. Google's consent-mode guide says tags adjust their behavior where a consent banner is required.
Where the figure has to come fromThe consent state, filters, and steps your implementation does not send.
Observed count
What must be true before you use itRecord the figure the tool displayed. Do not replace it with a percentage unless the denominator row is a compatible count.
Where the figure has to come fromThe report or order export, and the time you read it.
What cannot be inferred
What must be true before you use itA missing event can mean it was not sent. A Failed status means the store recorded a failed or declined payment, which may appear only after a delayed confirmation. Neither one identifies the repair.
Where the figure has to come fromThe conclusion you will not draw. Write unknown where the records stop.
These are temporary notes. Leaving or reloading this page may clear them. The consultation form does not include these entries.
Limits
A Prism consultation can help you organize the facts and discuss the website or processing question. The payment provider decides eligibility, pricing, reserves, and whether an account is opened or closed.
Do not put sample transactions, card data, or a customer list in the notes or the contact form.
Google Analytics ecommerce measurement — checked 2026-09-21. begin_checkout, add_payment_info, and purchase are events the implementation sends. The refund example comments that transaction_id is required for purchases and refunds.
Google consent mode — checked 2026-09-21. Consent mode controls data collection based on consent, and Google tags adjust their behavior where consent banners are required.
WooCommerce order statuses — checked 2026-09-21. Pending payment, Processing, On hold, and Failed are store statuses with different meanings, and Failed may not appear immediately for a delayed-notification payment.
Prism solutions — checked 2026-09-21. Public support is a website-content review, preparation for a card-processing review, or help with a provider's website questions. The provider decides account terms. Scope, fees, and terms are discussed before work.
Prism contact — checked 2026-09-21. The inquiry is reviewed and followed up by email. It does not book an appointment, purchase a service, or submit a processing application.
Request a consultation
Describe the business and this specific question. Prism follows up by email to discuss fit and scope. An inquiry is not a processing application or an approval.