By Mehdi HassanWhat is a thank you page?
A thank you page is the page or screen a visitor sees right after completing a form, signup or purchase. It confirms the action worked and tells them what happens next. Most sites treat it as an afterthought, a plain "Thanks, we'll be in touch", even though it's the point in the funnel where the visitor is most engaged.
That makes it the last part of the call to action, not a separate page. The button, the form and the confirmation form one flow, as our call to action guide describes. A strong thank-you page doesn't sell again; it turns the commitment the visitor just made into the next concrete step.
What should a thank-you page include after a form submission?
A thank-you page should include three things: a clear confirmation, specific expectations about what happens next, and one useful next step. Everything else is optional. If the page only does the first, it's a dead end. If it tries to do ten things, the visitor does none of them.
Confirm it worked
Say plainly that the form was received, and repeat what they asked for: "Your demo request is in" or "Your checklist is on its way to your inbox".
Set expectations
Say who will contact them, how and when: "A product specialist will email you within one business day". Only promise a time you'll meet.
Offer one next step
Pick the single most useful action for this offer: book a time, open the product, download the file, or share it with a colleague.
Give a fallback
Add a line for problems: "Didn't get the email? Check spam or write to us at this address."
Keep the exits quiet
Show minimal navigation and no competing offers. A short link back to the blog or docs is fine.
What thank you page ideas work for each offer type?
The best thank you page ideas depend on what the visitor just asked for. A demo request needs a booking step, a trial signup needs a first action in the product, and a download needs the file itself plus a relevant next resource.
Offer | Best next step | Example line |
|---|---|---|
Demo request | Embedded scheduler to book a slot now | Pick a time that suits you, and we'll send the invite |
Free trial signup | Open the product at the first useful action | Your workspace is ready. Connect your first data source. |
Content download | Direct download link plus a related resource | Download now. It's also in your inbox. |
Waitlist | Share link to move up the list or tell a colleague | Know someone who'd use this? Share your link. |
Newsletter | Best past issue or a short welcome | While you wait for Friday, here's our most-read issue |
Quote or services enquiry | What happens next, with a booking option | We'll reply within one business day, or book a call now |
Purchase | Order details, onboarding, support contact | Your order is confirmed. Here's how to get started. |
For developer products, the next step is usually the docs or an API key, not a sales call. Our collection of developer tool landing page examples shows how strong pages hand engineers straight to the first technical step.
Should you embed a booking calendar on the thank-you page?
Yes. For demo requests and sales enquiries, embedding a booking calendar on the thank-you page is usually the single most valuable change you can make. The visitor has just said they want to talk. Asking them to wait for an email, reply with availability and then confirm adds days and drop-off between the request and the meeting.
Pre-fill the scheduler with the name and email from the form so they don't type them twice. Route to the right person based on the form answers, such as company size or region, if your scheduling tool supports it. And keep a fallback for visitors who don't book: "Prefer we email you? We'll be in touch within one business day." Our guide to landing page form design covers the form side of this flow, including which fields help routing.
Hypothetical example: from contact form to booked meeting
For example, suppose a B2B SaaS demo form sends visitors to a page reading "Thanks, our team will reach out soon". Sales then emails each lead, and many never reply to propose a time.
The new thank-you page says "Your demo request is in" in the headline, embeds a scheduler pre-filled with the visitor's name and email, and routes larger companies to the enterprise rep. Under the calendar: "30 minutes with a product specialist. Not ready to pick a time? We'll email you within one business day." A short recorded demo sits below for anyone who wants a preview. The team tracks requests and booked meetings as separate events. This is illustrative, not a client result.
What are confirmation page best practices for tracking?
Confirmation page best practices for tracking come down to counting each conversion once, from a reliable signal. A dedicated thank-you URL is the simplest signal, but it breaks when people refresh, bookmark it or share it. A conversion event fired when the form submits successfully is more reliable, and many teams use both.
- Fire the conversion on successful submit, not on button click, so failed submissions don't count.
- Exclude the thank-you page from search with a noindex tag, so people don't land on it from Google.
- Pass non-personal details like the form type or plan as event parameters, never the visitor's email in the URL.
- Track the next step separately, such as booked meeting or file downloaded, so you can see how many leads take it.
- Test it on every form after any site or platform change.
Our guide to landing page conversion tracking covers the GA4 setup. Thank-you page tracking is one of the most common things to break during a platform move, which is why our guide to analytics continuity in a migration lists it as a launch check.
Should a thank-you page ask visitors to share or refer?
A thank-you page should ask visitors to share when sharing helps them too, as with waitlists, free tools, community invites or content they'd naturally forward to a colleague. It works poorly after a demo request or a sensitive enquiry, where a share button feels out of place.
Make sharing specific. "Share with your team" with a pre-written message and a copy-link button is more useful than a row of social icons. For waitlists, a referral link that moves the visitor up the list gives them a reason. For B2B content downloads, "Forward this to the person who owns your pricing page" often makes more sense than social sharing. If your audience spans several languages, check the confirmation page is translated too; our guide to language switcher UX covers keeping the language consistent through the flow.
How do you know if your thank-you page is working?
You know your thank-you page is working when a healthy share of visitors take the next step it offers: booking a slot, opening the product, downloading the file. Track that step as its own event and compare it with the number of conversions. If almost nobody takes it, the step is either the wrong one or isn't visible enough.
Compare against your own history rather than an external benchmark, the same approach our guide to landing page conversion rate benchmarks recommends. Watch a handful of session recordings on the thank-you page too: if people scroll looking for something, add it. And check the emails that follow, because the confirmation email is the thank-you page's second half and often gets forgotten in the same way.
