A confirmation page, also called a thank you page, is the page people see right after they submit a form, sign up or buy.
It does three jobs: it confirms the action worked, it tells people exactly what happens next, and it offers one relevant next step while their attention is highest.
In our database, the best results on this page come from that third job: a single fitting offer, a booking calendar or a one-question survey.
Most thank you pages do only the first job.
The tests below show what the page can do when you treat it as the start of the next conversion rather than the end of the last one.
Thank you page examples from real tests
Few teams publish tests run on the thank you page itself, so the evidence is thinner than for landing pages or forms.
What exists is consistent, though: the page converts when it offers one thing that fits what the person just did.
The one-click complementary upsell
Dave Diederen added a 1-click post-purchase upsell to a client store's thank you page.
It reached a 16.64% offer acceptance rate at $16.50 per accepted offer, with no extra ad spend.
Dave Diederen's explanation was about the offer, not the tool: someone who bought a face serum gets the moisturizer that goes with it, someone who bought a shirt gets pants. One product, one click.
Same item, new color
The clearest example of offer fit comes from The Perfect Jean, published by Visually.
The post-purchase offer went from a hoodie at 33% off to the item the customer had just bought, in another color, at 40% off. Offer conversion rose from 1.8% to 18.6%.
Treat that number with care. It is a before-and-after comparison across tools and several iterations, not one split test, and the sample size isn't stated.
The direction still matches the Dave Diederen result: the closer the offer is to the purchase, the more people take it.
Measuring the upsell in revenue
Vasta tested a post-purchase upsell against no upsell for a Shopify store and reported $5,282 in extra revenue in the first week.
The case study gives little detail about the offer, and its monthly figure looks extrapolated, so use the week-one number.
The booking page as the next step
For lead-gen and B2B, the most useful next step after a form is usually a calendar.
Convert Better redesigned High Voltage SEO's booking page: the headline changed from "Book Your Call" to "Free SEO Strategy Session", the calendar moved fully above the fold, and testimonials were added.
Time-slot clicks rose 119% in a 30-day split URL test.
Because the whole page changed at once, you can't credit any single element.
The pattern to copy is that a visible calendar with a reason to book beats a half-hidden one.
The welcome email that follows the page
The thank you page and the first email work as one step.
CNET simplified its welcome email from four content sections to a short intro with one call to action and a "Thanks for joining!" subject line.
Opens went from 32% to 46% and clicks from 12% to 21%, across five treatments tested in series.
Thank you page best practices
These practices come from the tests above and from what the page needs to do technically.
Each one is a hypothesis to test on your own traffic, not a guaranteed lift.
1. Confirm the action in the headline
Say what just happened in plain words: "Your quote request is in" or "Order #1042 confirmed".
People who aren't sure their form went through submit it again or call support.
2. Say exactly what happens next
Give a time frame and a channel: "A specialist will call you within one business day from a 1-800 number."
Vague lines like "We'll be in touch" leave people guessing.
Setting expectations also works before the submit. HomEquity Bank added a tracker to its inquiry form that explained what happens after submitting and saw a 20% higher conversion rate.
Once you've made that promise on the lead form, the thank you page has to deliver the same steps in the same words.
3. Offer one next step, and make it fit
Pick a single action that follows naturally from what the person just did.
For a store, that is a complementary or same-item offer (see our upsell tests and the upselling guide).
For a lead-gen form, it is booking a call.
For a lead magnet, it is the download plus one related resource.
For a webinar registration, it is "add to calendar".
Several competing offers on the same page dilute attention.
The one-product, one-click approach Dave Diederen described is a good default.
4. Ask one survey question
The thank you page is where you can ask buyers why they bought, or what nearly stopped them, while the answer is fresh.
Keep it to one question with an optional text field (our guide to survey questions covers wording).
Those answers feed tests elsewhere. Oliver Kenyon put three reassurance lines taken from post-purchase surveys above a collection page grid for a bird food brand, worth $44,890 a month, or $0.66 per session.
Kasper Dolk turned survey objections into hero benefit bullets for a gain of $763,679.14 profit per year.
More examples are on our post-purchase survey page.
5. Keep it out of search and protect your tracking
Many teams count a conversion when the thank you page loads.
In Google Analytics 4, you can create a new event from page_view with a URL condition, such as a thank-you URL, and mark it as a key event.
Because of that, anyone who bookmarks or finds the page directly inflates your numbers.
Add a noindex tag, block repeat loads where you can, and if possible fire the conversion on the form submission itself.
If you run A/B tests with the thank you page as the goal, a broken page or tag will quietly break the test.
6. On Shopify, rebuild old scripts
Shopify set August 26, 2026 as the deadline to upgrade the Thank you and Order status pages on non-Plus plans (Plus stores had until August 28, 2025), and stores that hadn't upgraded were moved over automatically.
If your post-purchase upsell, survey or tracking relied on additional scripts, check that it still runs, and use the replacement steps in that help article if it doesn't.
What a thank you page is, and how to test one
A thank you page is any page shown after a completed action.
Ecommerce stores call it the order confirmation page, lead-gen sites call it the form confirmation page, and SaaS products often replace it with the first onboarding screen.
| Site type | What the page confirms | Best next step to test | Metric to watch |
|---|---|---|---|
| Ecommerce | Order and delivery estimate | One-click complementary or same-item offer | Offer acceptance rate, revenue per order |
| Lead-gen | Form received, who calls and when | Booking calendar | Booked calls, show rate |
| Content and lead magnets | Download link, email on its way | One related resource or newsletter opt-in | Email opens, second conversion |
| Events and webinars | Seat reserved, date and time | Add to calendar | Attendance rate |
| Any | Action completed | One-question survey | Response rate, answers you can act on |
Why it matters even when you don't test it
The thank you page is often the conversion goal in tests run on other pages.
ArchiveSocial's pricing page redesign, run with VWO, was measured by thank-you page visits and lifted them 64.76% over seven weeks.
ConvertPolo's one-step cart for AnotherSole reported a 51% increase in thank-you page visits alongside a 131% revenue gain.
If the page or its tag misfires, results like these become unreliable.
Check it before every test that uses it as a goal.
How to test the page itself
Traffic here is limited to people who already converted, so a store with 1,000 orders a month gets only 1,000 visitors to split.
Test big changes, such as adding an offer versus none, rather than button colors, and expect tests to run for weeks.
Pick the metric before you start. For upsells, use revenue per order or offer acceptance, and also watch refunds and cancellations, since an aggressive offer can raise one while hurting the other.
For lead-gen, booked calls matter more than clicks on the calendar.
When the thank you page isn't the bottleneck, your time is better spent upstream.
Start with form optimization and the follow-up email, or browse every lead-gen test and the full test database.