You can spend hours building a funnel, checking the pages, refining the copy, and getting the offer ready, only to find out it’s not really ready. When traffic arrives, it reveals that a button links to the wrong page, a payment connection doesn’t work, or a follow-up workflow never triggers.
The following funnel launch checklist can help you cover all your bases before sending traffic through. In GoHighLevel, some of the settings that make a funnel work aren’t obvious when you’re looking at the finished pages. A few tests before launch can catch issues before visitors discover them.
Run This Funnel Launch Checklist Before Publishing
Before you send traffic to a new funnel:
- Connect the custom domain or subdomain and load the correct funnel pages.
- Connect the payment processor and complete a test purchase.
- Install conversion tracking and pixels on the appropriate pages.
- Turn on follow-up workflows and verify their triggers and actions.
- Add appropriate SMS consent language to forms that collect phone numbers.
- Test the funnel on both desktop and mobile devices.
- Click every button and link to confirm it goes to the right step.
This is a starting point, not a complete checklist for every funnel. A funnel with upsells, memberships, appointments, multiple offers, or more complicated workflows will need additional testing. But these checks cover several settings that are most likely to cause difficulties when overlooked.
Check Domain and Payment Connections
Start with the basics. Make sure your custom domain or subdomain is connected and loads the funnel you expect.
Don’t assume that a domain working somewhere in your account means the correct funnel is connected to it. Open the published URL yourself and click through the pages as a visitor would.
If the funnel collects money, run a test purchase through the checkout and confirm that the transaction is processed as expected. If you’re using a real payment method for the test, follow your normal process for refunding the charge afterward.
Next, check what happens after the purchase. Does the customer reach the right confirmation page? Does the purchase trigger the expected workflow? Does the order appear where you expect it to?
Testing the checkout should cover the entire transaction, not just the payment form.
Confirm Tracking Is Capturing the Funnel
Tracking can be easy to overlook because it doesn’t change what the visitor sees. A page can look perfect while your analytics or advertising platform isn’t receiving the conversion data you expect.
Check that your tracking code or pixel is installed on the appropriate pages. If you’ve duplicated, rebuilt, or significantly edited a page during development, check it again rather than assuming the tracking carried over correctly.
Then test the funnel with a real visit. You or a team member should go through the relevant steps and confirm that the visit or conversion appears in your reporting system.
This is a better way to test than simply checking whether a tracking ID has been entered somewhere in the account. The goal is to confirm that activity from the funnel reaches the reporting platform.
Check Your Follow-Up Workflows Before They Go Live
GoHighLevel can automatically send email and text messages when someone submits a form, makes a purchase, books an appointment, or takes another action in the funnel.
Before turning those workflows loose on real leads, test the triggers and the actions that follow them. For example, submit the opt-in form yourself and confirm that:
- The contact is created or updated correctly.
- The contact enters the intended workflow.
- The right email or text message is sent.
- Any tags, pipeline stages, or other actions are applied correctly.
- The next step happens when it’s supposed to.
SMS deserves an additional check because consent requirements can apply to automated text messaging. In the United States, businesses using application-to-person (A2P) messaging may also need to complete the applicable registration requirements for their sending number and messaging use case.
Your form should clearly communicate what someone is agreeing to receive. If you’re sending automated texts, don’t assume that a generic statement saying someone agrees to be contacted covers every requirement that may apply to your campaign.
Check the current requirements for your messaging setup before launch, and test the workflow before a real lead receives the first message.
Test the Funnel on Mobile
A funnel that looks good on a desktop can still have problems on a phone.
Open the published funnel on a mobile device and go through it from beginning to end. Check the page layout, forms, buttons, checkout, calendars, and anything else a visitor may interact with.
Pay particular attention to buttons and links. They should be easy to tap and take you to the intended step.
It’s also worth testing the funnel the way a new visitor would experience it, rather than jumping directly to individual pages. Start with the first page, click the call to action, submit the form, and continue through the funnel.
Check Every Button and Link
Don’t assume a button works. Click every important button and link one page at a time. Confirm that each one goes to the right destination and that you’re not sending visitors to an old page, an unfinished step, or the wrong offer.
This is especially important after making changes to a funnel. A button that worked before a page was duplicated or rearranged may no longer point where you expect it to.
If the funnel has several paths, test each one. An opt-in followed by a sales page may work correctly, while an alternate CTA sends visitors somewhere else.
A Simple Pre-Launch Check Can Prevent Bigger Issues
Catch configuration problems before a visitor or customer finds them.
Check the domain, payment process, tracking, workflows, mobile experience, and links. If your funnel includes additional steps such as appointments, memberships, or upsells, test those as well.
Before sending paid traffic or a large audience to a new funnel, take the time to test the parts visitors can’t see.