Flight log / Transmission 065

Thank you pages: the most ignored page in your paid funnel

Reaching the flagpole isn't the end of the level, and a form submit isn't the end of the funnel. Google's own setup guide tells you to put the conversion tag on the page people reach after they convert, which makes the thank you page the one page every paid lead sees.

Most B2B teams spend weeks on the landing page and five minutes on the page that comes after it. The thank you page usually says "Thanks, we'll be in touch," sits on a URL anyone can visit, and fires the Google Ads conversion tag every time it loads. That's two problems on one page: your conversion data is padded, and your hottest lead of the day gets a dead end.

This guide covers both jobs: the measurement side (where the tag goes, how phantom conversions get in, and how to keep them out) and the experience side (what a paid lead should be asked to do in the 30 seconds after they hit submit). For the form itself, see our form optimization guide; this post starts where that one ends.

What is a thank you page?

A thank you page, also called a confirmation page, is the page a visitor lands on after completing a conversion: submitting a demo request, downloading a guide, starting a trial. It can be a separate URL (/demo/thanks/) or an in-page message that replaces the form.

The distinction matters for tracking. Google Ads Help's guide to adding a Google tag tells you to open the HTML for "the page your customers reach on your website after they've completed a conversion" and paste the Google tag and event snippet between the head tags. That's the page-load method. If your form shows an inline message without a new page load, Google points you to a separate method for tracking clicks or events instead. Either way, the moment of conversion is defined by what happens right after the submit, which is why this page deserves more attention than it gets.

Where should the Google Ads conversion tag go?

On the thank you page, and only on the thank you page. Google gives you two ways to do it for a page load:

• Event snippet on the page. Google tag first, then the event snippet, in the head of the confirmation page, per Google Ads Help.
• URL-based conversion. Google Ads Help's conversion setup page says you can create an event your Google tag detects "without adding any code to your website," using a rule such as URL is, URL contains (Google's example is "thank-you") or URL starts with.

The URL-based route is convenient and easy to get wrong. "URL contains thank-you" also matches a blog post called /blog/thank-you-email-templates/, a webinar replay page, and every other confirmation page on the site. Use "URL is" with the exact confirmation URL when you can, and give each offer its own confirmation URL so a newsletter signup and a demo request don't count as the same conversion.

If you also use Google Analytics, the same page can drive a key event. Google's migration guide for old destination goals shows how: create a new event triggered when page_view fires with page_location equal to the thank you page URL, then mark that event as a key event. Name it something your team will recognize, such as generate_lead.

Why do Google Ads conversions not match leads in the CRM?

Some gap is normal: attribution windows, people who submit twice, leads the CRM deduplicates. But a thank you page that fires on every load adds a gap of its own. Here's what that looks like in a hypothetical B2B account spending about $15,000 a month, comparing weekly conversions reported in Google Ads with new leads created in the CRM from paid search.

In this illustrative account, Google Ads reported about 50% more conversions than the CRM for four weeks. After the fix in week 5, the lines sit within a lead or two of each other. Nothing about lead flow changed. The account simply stopped counting things that weren't leads. That matters for more than reporting: if you use Smart Bidding, the bid strategy has been learning from those phantom conversions, so it was optimizing toward whatever traffic happened to reload a confirmation page.

Where did the extra conversions come from? Continuing the same hypothetical audit, here's an illustrative breakdown of the phantom conversions by cause.

Each of those has a specific fix:

• Refreshes and repeat visits. Set the conversion action's count setting to One. Google Ads Help says this option "counts only one conversion per ad click" and recommends it for leads, where you care that a lead was generated rather than how many times. Every is for sales, where each purchase adds value.
• Organic search landings. Add <meta name="robots" content="noindex"> to the thank you page. Google Search Central says a noindex rule drops the page from Google Search results "regardless of whether other sites link to it." Don't also block the page in robots.txt: Google warns that if robots.txt blocks the page, the crawler never sees the noindex rule.
• Loose URL rules. Switch "URL contains" to "URL is," or move to an event snippet that fires only on a successful submit.
• Internal tests. Give your team a test path that doesn't hit the production confirmation URL, or filter internal traffic in analytics.

If you want the conversion to carry more than a page load, enhanced conversions for leads lets the tag send hashed lead details from the form, so you can later import which leads became opportunities. Google Ads Help describes the flow: your site sends hashed lead information such as a hashed email, and when the lead converts offline you import the same hashed data so Google can match it to the ad. Our enhanced conversions guide covers the setup.

What should a B2B thank you page include?

Start with what the lead is thinking. They just gave you their work email. Their questions are: did it work, what happens next, how long will it take, and is there anything I can do now? A thank you page that answers all four, in that order, is already better than most.

1. Confirmation. One line that says the request went through and names it: "Your demo request is in."
2. What happens next, with a time. "A solutions engineer will email you within 1 business day." Only promise what your team actually does.
3. One next step. For a demo request, that's booking the meeting now. For a content download, it's the content plus one relevant follow-on, not a menu of ten.
4. Something to read while they wait. A short customer story from their segment or a 2-minute product tour. This is also the right moment for the security or pricing detail they'd otherwise ask about on the first call.
5. Nothing that leaks. No main nav mega menu, no blog feed, no exit to the careers page. The visitor is still in your funnel.

Harvard Business Review's 2011 article "The Short Life of Online Sales Leads" summed up its research bluntly: most companies are not responding nearly fast enough. The thank you page is the one place where response time can be zero, because the lead can book the meeting before anyone on your team has seen the notification.

Should you put a calendar on the thank you page?

For demo and consultation requests, usually yes. The gap between "submitted a form" and "attended a meeting" is where B2B paid search quietly loses pipeline, and every email round trip to find a time widens it. Here's an illustrative comparison of thank you page treatments in a hypothetical demo funnel, measured by the share of form submitters who booked a meeting within 7 days.

In this hypothetical funnel, the generic page converts 22% of submitters into booked meetings, mostly through sales follow-up emails. Adding a clear timeline nudges that to 27%. Putting the calendar in front of the lead moves it to 46%. On 100 demo requests a month, that's 24 more meetings from the same ad spend and the same landing page. Treat that as the shape of the effect, not a forecast.

Two cautions. If your team needs to route or qualify before a meeting, show the calendar only to leads that pass routing, and give everyone else a clear timeline. And if the calendar asks for the same details the form just collected, you've rebuilt the form on a second page. Pass the form values through.

How do you audit a thank you page?

Run this once per conversion action. It takes about 20 minutes and it's the cheapest data quality fix in most paid search accounts.

The reconciliation row is the one that catches everything else. If the gap between Google Ads and the CRM jumps, something on the thank you page changed.

Thank you page or inline confirmation message?

A separate page is easier to track, noindex and give a next step. An inline message is fine for a newsletter signup but wastes the moment on a demo request, so a dedicated confirmation URL per offer is the safer default for paid lead gen. If you're stuck with inline messages, track the successful submit as an event and test that an invalid submit doesn't fire it.

The same page also matters for message match. If the ad promised "a pricing walkthrough in 20 minutes," the thank you page should confirm a pricing walkthrough, not a generic "demo." Pricing pages have their own set of choices; see our post on pricing pages for paid traffic.

Where thank you page advice breaks down

• Low volume hides problems. An account with 15 leads a month can't see a 20% phantom rate in the weekly numbers. Reconcile monthly against named leads instead.
• Counting One isn't deduplication across actions. Google counts one per click per conversion action. A person who requests a demo and downloads a guide from the same click still counts twice if both are primary actions.
• A booked meeting isn't a qualified meeting. Embedding a calendar can raise bookings and no-shows together. Judge it on meetings held and opportunities created.
• Privacy settings change what you see. Consent choices and browser restrictions mean some real conversions never reach Google Ads. A small gap in the other direction can be normal.

FAQ