The page after the conversion
Most conversion work happens before the confirmation page, and most measurement treats it as the end of the journey. The key events guide and the guide to a purchase event that is not tracking both treat it as the place a conversion is counted, which is true and important. But the page also has a person on it, and for that person the journey has just changed from deciding to waiting. They want to know that it worked, what happens now and what to do if something goes wrong. The funnel and checkout section adds a warning from the other side: the last transition, from payment to confirmation, leaks for technical reasons that stay invisible unless someone looks, such as declined cards, failed redirects and timeouts.
That makes the confirmation page the first moment of the customer relationship rather than the last moment of the funnel. The AARRR framework follows a customer past the first conversion into activation, retention, referral and revenue, and the confirmation page is the first place the business can help each of those stages along. It is also the only page every customer sees, which makes small improvements reach everyone.
Three things usually go wrong. The page confirms too little, so customers write in to check. It tries to do too much, with banners, cross-sells, a survey, an app download and a newsletter box competing for the same screen. Or it reports the conversion badly, counting reloads twice or leaking personal data into analytics. Each has a straightforward fix. Accessibility belongs on the list too: the accessibility guide notes that a success message shown only visually leaves a screen readerSoftware that announces a page's text, headings, labels and messages to people who cannot see the screen, and reports what the page provides. user with nothing announced after the final click.
Confirm and set expectations
The first job is to say clearly that the conversion happened and what it was. For an order, that means the items, the order reference, the total paid, the delivery address and where the confirmation email has gone. For a lead, it means what was sent and to whom. For a booking, it means the service, the date and time, the place and any deposit taken.
The second job is to answer the question every customer has next: what happens now, and when. The checkout optimisation guide notes that a delivery date answers the shopper's actual question where a duration does not, and the same holds after payment. As general practice, the page states when the order will be dispatched or arrive, how the customer will be kept informed, how to change or cancel, and how to get help. Saying these things on the page tends to reduce the anxious "did my order go through" contacts that support otherwise receives, and it sets an expectation the business then has to meet.
| Conversion | Confirm | Set expectations |
|---|---|---|
| Online order | Items, order reference, total paid, delivery address, email sent | Dispatch or delivery date, tracking, how to change or return |
| Lead or enquiry | What was sent, to which team | Who will respond, by what route, by when |
| Booking or appointment | Service, date, time, place, deposit | Reminder, how to change or cancel, what to bring |
| Account or trial | The account exists, the plan chosen | What to do first, when the trial ends, what it will cost |
| Subscription | Plan, price, billing date | The renewal date and how to cancel |
The confirmation email mirrors the page and outlasts it. The page can be closed in a second; the email is what the customer will search for later, so the two should say the same things in the same words. The emails that follow the order belong to the email marketing root and are not designed here.
One next step, chosen for the business
A customer who has just converted is, briefly, more willing than usual to do one more thing. The temptation is to ask for several, and the result is that the confirmation is buried and none of the requests is noticed. Choose one next step, the one that matters most to the business at this point, and put it after the confirmation, not above it.
| Next step | When it fits | Where it is covered |
|---|---|---|
| Create an account after guest checkout | The email and address are already captured, so the account is a single click | Checkout optimisation |
| Refer a friend | The customer has already had the result they came for, such as a repeat order or an instant service | Referral programme |
| A related item | Something the buyer will need to use the purchase, offered without interrupting the order | Average order value levers |
| Marketing email sign-up | The customer has not already been asked at checkout, and the choice is separate and unticked | List building and consent |
| Book a call or slot | A lead has been sent and the business offers self-booking | Booking flows |
Each option has a condition. The checkout guide recommends offering the account afterwards, on the confirmation page, when it costs the customer a click rather than a form. The referral programme tutorial asks for referrals just after a success point, when the customer has had the result they came for, and warns against asking when the customer has nothing to recommend yet, so a first order that has not arrived is often too early. The average order value levers guide calls post-purchase offers on the confirmation page the safe place for anything that might otherwise distract from the checkout; a cross-sellOffering a customer a related product alongside the one they are buying; upselling offers a higher-value version instead. here should still be something the buyer would thank the business for, offered rather than pre-selected, as the guide to honest persuasion recommends for every paid extra. And the list building and consent guide treats the moment after a good experience as a strong placement for an email sign-up, provided marketing consent is a separate choice and not folded into a transactional message.
Choose by what the business most needs from new customers. A shop whose growth depends on repeat orders may want the account; a service with satisfied customers and a referral programmeA scheme that rewards existing customers, and often the friends they invite, when a recommendation brings in a new customer. may want the referral; a business whose customers buy once and need a consumable later may want the related item. Whatever is chosen, measure it, and change it if it does not earn its place.
One question worth asking
The confirmation page is also the cheapest place to learn something, because the conversion is already safe and a short question costs nothing in completed orders. Ask one question, optional, with a single click or a short answer, and choose it for the decision it will inform.
Two questions earn their place most often, and they serve different purposes. "What nearly stopped you from buying today?" is a research question; the conversion research methods guide calls the nearly-stopped answers the most direct source of friction findings, while warning that buyers rationalise, so the answers give themes rather than proportions, and the tutorial on on-page polls and post-purchase surveys sets out how to word the question and code the answers. "How did you hear about us?" is an attribution question; the self-reported attribution guide lists the confirmation page as a placement that adds no friction to the purchase, notes that fewer people answer and that those who do are not a random sample, and requires the answer to land on the same record as the order.
Ask one or the other, not both. Two questions on a confirmation page halve the attention each receives and double the reading the customer has to do. Rotate them over time if both are needed, and keep the wording fixed within a period so the answers can be compared.
Counting each conversion once
The confirmation page is where most purchase and lead events are sent, so it is where most counting errors start. The principle, from the key events guide, is that a Key EventA GA4 event marked as important to the business, the property's measure of success. fires once per real occurrence and does not fire on refresh, on back navigation or on a test order. A conversion counted twice inflates the conversion rate (CVRShare of visits or clicks that convert.), misleads every report built on it and, once imported into an advertising platform, teaches bidding to chase conversions that never happened.
Several defences work together:
- Fire from the order, not the page view. The purchase troubleshooting guide recommends pushing the order to the data layer with a purchase event and triggering the analytics tag on that event, not on page view, and testing with a real checkout rather than a page reload.
- Pass the transaction identifier. The GA4 e-commerce developer guide gives the purchase event a
transaction_idthat identifies the order, which the site's guide to average order value in GA4 describes as stopping the same purchase being recorded twice. The Google Ads conversion clean-up tutorial notes that a transaction ID passed with each order lets Google Ads ignore a repeat of the same order, which is how a reloaded confirmation page is kept from counting twice. The glossary covers DeduplicationRemoving double counts when one conversion is reported by more than one source. in general. - Choose the counting method. The key events guide counts purchases once per event, because two orders in one visit are two outcomes, and leads and sign-ups once per session, because a refreshed thank-you page or a double-clicked button is one enquiry.
- Keep one source for each conversion. The clean-up tutorial finds the same sale counted twice when a native advertising tag and an analytics import are both treated as primary.
Google documents events as the unit analytics uses to measure interactions, and marking one as a key event changes how it is used, not how it is collected; the counting is only as good as the event. When a conversion rate steps up with no change anyone can name, this page counting twice is one of the first things to check, and the diagnosis for a conversion rate that jumped overnight sets it beside the other causes of a false rise. Two further points matter on this page. Some buyers never reach it, because they pay on a provider's page and close the tab, and the purchase troubleshooting guide covers sending those orders from the order system with the same transaction identifier. And the page address must not carry personal data: the guide to keeping personal data out of analytics names confirmation addresses built with an email address or a name as a common route for personal data into reports, and recommends an opaque reference instead. The same applies to event parameters.
Thank-you pages for leads and bookings
A lead form's thank-you page has a harder job than an order confirmation, because nothing has been bought and the person does not yet know what the business will do with their enquiry. Set the expectation precisely: who will be in touch, by what route and by when, and what the person can do in the meantime, such as read a relevant guide or prepare the information the call will need. Then meet the expectation. The lead response time test keeps the confirmation page identical in both arms while it tests how quickly sales follows up, which is a reminder that the promise on this page and the speed behind it are separate decisions.
Where the business takes bookings, a thank-you page can offer to book the call or the visit straight away rather than waiting for a callback; the demo scheduling test sets out how to test a booking calendar on the confirmation step against the standard callback. The guide to booking and appointment flows covers what the booking itself should ask and confirm.
Lead events follow the same counting rules as purchases. The recommended generate_lead event, counted once per
session, records the enquiry once; the events and parameters guide warns that deriving a lead event from a thank-you page view in
the interface and also marking the original event double-counts, and that such rules are a stopgap rather than a
substitute for a clean tag.
A plant nursery rebuilds its order confirmation (illustrative)
Mossquibble Plants rebuilds its order confirmation
Mossquibble Plants, an invented online plant nursery, takes about 2,400 orders a month. Its confirmation page
says "Thank you for your order" above three promotional banners, for a seasonal sale, gift cards and a new
houseplant range, and gives the order number in small print at the bottom. There is no dispatch date. Support
receives around 280 "has my order gone through" and "when will it arrive" messages a month. GA4 records 2,710
purchases against 2,400 shop orders, because the purchase tag fires on page view and buyers who refresh the page
or return to it are counted again. The team rebuilds the page: the order summary, reference and total at the top;
the dispatch date and the expected delivery window; three first-week care steps for the plants in the order; and
one unticked option to receive monthly care tips by email, replacing the three banners. A developer moves the
purchase tag onto the data layer push and passes the order number as transaction_id. In the following month,
order and delivery questions fall to about 150, 23% of buyers choose the care tips, and GA4 records 2,330
purchases against 2,450 orders, a gap the team traces to buyers who decline analytics cookies rather than to
duplicates. Reported conversion rate falls as a result, which the team explains to the people who read the
dashboard before anyone mistakes the correction for a loss.
Common mistakes
- Treating the page as the end of the funnel. It is the first moment of the customer relationship.
- Confirmation in small print. The order, the reference and the total belong at the top.
- No date. Say when the order ships or arrives, or when someone will be in touch.
- Several next steps at once. Choose one, put it after the confirmation, and measure it.
- Asking for a referral too early. Wait for a success point the customer has actually experienced.
- Two questions at once. Ask what nearly stopped them or how they heard about the business, not both.
- Firing the purchase on page view. Fire it from the order data, once, with the transaction identifier.
- Personal data in the address. Use an opaque reference, not an email address or a name.
- Marking both a derived and an original lead event. One conversion, one key event.
- Reading a lower count as a loss. Removing duplicates lowers reported conversions; say so before the report goes out.
