GoHighLevel Thank You Page: Setup, Tracking & Stats

A GoHighLevel thank you page is the funnel step a visitor lands on after they opt in, book a call, or finish an order.

Most agencies build it last and think about it least, which is backwards. This is the step where a funnel either confirms the action cleanly or leaves someone wondering if anything actually happened.

Setting Up a GoHighLevel Thank You Page the Right Way

Inside the page builder, a thank you page is just another step in a sequence. An opt-in form or a checkout page comes first, and the thank you step follows it.

HighLevel's own guide to creating pages in the builder covers adding a new step, naming it plainly, like "Thank You Page," and giving it a short path such as /thank-you.

Steps can be dragged into a different order without changing their URLs.

Get the sequence wrong and the step before it breaks too. A sales funnel that routes to the wrong step after checkout still runs without erroring, but the visitor lands somewhere that doesn't match what they just did.

Tracking a Conversion Without Firing It Twice

GoHighLevel gives you two separate places to drop a tracking script, and mixing them up is the most common way this page ends up reporting double conversions.

The guide to adding tracking code to funnels and websites keeps these two separate on purpose. Page-level code is excluded when you duplicate a page, so a copy doesn't silently carry someone else's conversion event with it.

Meta draws the same line for its own Purchase event. Its pixel reference documentation specifies that Purchase should fire once a person lands on a thank you or confirmation page, not earlier in checkout, since firing it sooner inflates what the ad account thinks it sold.

Firing Automations Off the Step Itself

The Order Submitted trigger is how a workflow knows a purchase happened, firing separately for the primary product and for any upsell.

Left unfiltered, it fires wherever an order form sits in the funnel. The fix is the "Page Is" filter, paired with "In Funnel/Website," narrowing the trigger down to one named step.

Turning on "Allow Multiple" stops the primary purchase and an upsell from blocking each other when both happen in the same session. That's also where this step earns its place in a wider automated workflow, instead of sitting there as a dead end.

Reading the Stats This Step Produces

Once traffic is flowing, the stats panel breaks the thank you step down the same way it breaks down every other step: total page views against unique page views, with an opt-in rate dividing the two.

A sales-focused funnel adds a conversion rate from views to purchases, plus average cart value and earnings per page view. HighLevel's own funnel and website stats definitions flag declining unique traffic, and low opt-in or sales conversion, as the patterns worth acting on.

Strong unique views with a flat opt-in rate upstream usually isn't a thank you page problem at all. It's a sign the step before it isn't converting, and this step is just where that shows up first.

Once the sequencing, the tracking code and the triggers all match what the documentation describes, this step stops being a formality. It becomes the one place in the funnel where you can see whether the rest of it worked.

Getting that setup right the first time, through GHL setup and configuration, saves the trouble of untangling duplicate pixels and misfiring workflows after the funnel is already live.

Cover photo by Towfiqu barbhuiya on Pexels