GoHighLevel Forms & Surveys: Lead Capture Guide (2026)

By Dr Priya Jaganathan, GoHighLevel Certified Admin · HL Growth Partner, Australia · Updated 3 August 2026 · 10 min read

On this page: Forms vs surveys · Building forms · Custom fields, hidden fields & UTMs · Conditional logic surveys · Embedding options · Workflow automation recipes · Spam prevention & Australian privacy · Reporting on submissions · Common mistakes · FAQ

GoHighLevel forms are the front door of your lead-capture system, and most sub-accounts I audit use perhaps a third of what they can do. A form in HighLevel is not just a box that collects an email address — it maps every field to a contact record, carries UTM attribution invisibly, and triggers automation the second the submit button is clicked.

This guide covers the full stack: forms versus surveys, building and styling, custom and hidden fields, conditional logic, embedding, and the Workflow recipes I deploy in almost every Australian client build — plus the privacy obligations that come with Australian lead capture.

Forms vs surveys: when to use which

GoHighLevel gives you two lead-capture builders under Sites: Forms and Surveys. They share most field types and both write to contact records, but they suit different jobs.

A form is single-page: every field on one screen, one submit. Forms are right for lead magnets, contact pages and newsletter opt-ins — anywhere friction must be minimal.

A survey is multi-step. Questions split across slides, and — critically — surveys support conditional logic, so the next question can change based on the previous answer. Surveys also capture partial submissions: if someone enters their email on slide one and abandons on slide four, you still get the contact. That makes surveys the tool for qualification, quizzes, intake questionnaires and application funnels.

My rule of thumb: three fields or fewer, use a form. Anything that qualifies, scores or segments a lead, use a survey.

Building forms: fields, styling and settings

The form builder is drag-and-drop. Standard fields — full name, email, phone — map automatically to the core contact record; beyond those you can add text, dropdowns, radio buttons, checkboxes, date pickers, numbers and file uploads.

Field choices that affect data quality

Use the dedicated phone field for numbers — it validates format and supports SMS automation later. Use dropdowns or radio buttons wherever answers are predictable: "How did you hear about us?" as a dropdown gives you clean, reportable data; as a text box it gives you forty spellings of "Instagram".

File uploads

The file upload field lets leads attach documents — job applications, design briefs, supporting paperwork — which land against the contact record. Set expectations on the form itself ("PDF only, max 10 MB") to reduce failed submissions.

Styling and behaviour

The Styles panel controls fonts, colours, spacing, border radius and button design, so an embedded form can match the host site's branding without custom CSS. In Options you choose the post-submission behaviour: a thank-you message or a redirect. Redirect to a dedicated thank-you page when you can — it gives ad platforms a clean conversion event and a natural spot for the next call to action, such as a booking link built on GoHighLevel calendars with round-robin routing.

Custom fields, hidden fields and UTM capture

This is where HighLevel forms pull ahead of generic form tools. Every non-standard field should map to a custom field on the contact record, created under Settings > Custom Fields in the sub-account. Once mapped, the answer is stored permanently against the contact, is available as merge tags in emails and SMS, and can drive Workflow conditions ("If Budget field is greater than $5,000, assign to senior closer").

Name custom fields deliberately and consistently. If you deploy the same build across multiple sub-accounts via snapshots, the fields travel with the snapshot — a clean naming convention in the template account saves cleanup later.

Hidden fields

Hidden fields are fields the lead never sees but that still write data to the contact. Two main uses:

Static values. Set a hidden field to a fixed value per form — a "Lead Source" field set to "Ebook Funnel" on one form and "Homepage Contact" on another. Every submission arrives pre-labelled.

URL parameters. Hidden fields can populate from query strings: if your ad sends traffic to yourpage.com?utm_campaign=winter-offer, a hidden field keyed to that parameter captures "winter-offer" automatically. GoHighLevel also captures standard UTM parameters (source, medium, campaign, term, content) on submissions, so attribution reaches contact records without the lead typing a thing — when a sale closes months later, you can still see which campaign started the conversation.

Conditional logic surveys: branching that qualifies leads

Conditional logic (logic branches) is the survey builder's superpower. You define rules on a slide: if the answer equals X, jump to slide 4; if Y, jump to slide 6; otherwise continue. You can also branch to different thank-you pages or disqualification messages.

From a mortgage-broker client build: slide one asks "Are you purchasing or refinancing?" Purchasers branch to deposit and pre-approval questions; refinancers to current rate and loan size. Both paths converge on contact details at the end — one survey, two tailored experiences, every answer in custom fields the Workflow reads to route the lead.

Design tips that lift completion rates: put engaging questions first and contact details last — momentum matters. Keep each slide to one decision. Use a polite disqualification branch ("We only service Queensland at this stage") rather than wasting your team's time. And enable partial submissions so an abandoned survey still gives you an email to remarket to.

Embedding options: funnels, websites and third-party sites

You have three placement options, and choosing correctly avoids most tracking headaches.

1. Native placement in funnels and websites

Inside the GoHighLevel funnel and website builder, drag the Form or Survey element onto the page and select your form. Cleanest option: no embed code, full styling control, attribution tracked natively.

2. Embed code on third-party sites

Every form and survey has an embed code — an iframe snippet you paste into WordPress, Shopify, Squarespace, Webflow or any site that accepts HTML. The form runs on GoHighLevel's infrastructure, so submissions, field mapping and Workflow triggers work exactly as they do natively. Test on mobile after publishing — iframe heights sometimes need adjusting.

3. Direct link

Each form and survey also has its own hosted URL — handy for SMS campaigns, email signatures and QR codes on print material.

Workflow automation: what happens after submit

A form that does not trigger automation is a spreadsheet with better fonts. In Workflows, the Form Submitted and Survey Submitted triggers fire the instant a lead submits, with filters to scope the Workflow to one specific form. From there you chain actions: add tags, update custom fields, create opportunities, notify staff, start nurture sequences. If Workflows are new to you, start with my guide to GoHighLevel Workflow triggers and actions.

Recipe 1: Lead magnet form → tag → nurture

Trigger: Form Submitted, filtered to your lead magnet form. Actions: add tag lead-magnet-ebook, send the download email immediately, wait 1 day, then start a five-email nurture sequence. Add an If/Else branch checking for a customer tag first, so existing clients skip the sales pitch. This recipe is the backbone of most small-business lead gen.

Recipe 2: Survey qualifier → opportunity stage

Trigger: Survey Submitted on your qualification survey. Use If/Else conditions on the custom fields the survey populated — budget, timeframe, location. Qualified path: create an Opportunity at the "Qualified Lead" stage, assign an owner, fire an internal notification to the rep. Unqualified path: tag not-qualified-2026 and drop into a low-touch newsletter list. See my walkthrough on setting up pipelines and opportunities if yours is not built yet.

Recipe 3: Quiz-style survey for segmentation

Run a "What's your biggest marketing bottleneck?" quiz as a survey. Each answer maps to a custom field value, and the Workflow branches on that value to apply a segment tag — segment-traffic, segment-conversion, segment-retention — and start a nurture sequence written for that exact pain point. Segmented sequences outperform generic ones because the emails speak to the problem the lead just told you they have.

Spam prevention and the Australian privacy angle

Stopping junk submissions

Bot submissions pollute your contact database and fire your Workflows at rubbish leads. Defences worth enabling: the built-in CAPTCHA option in form settings, proper phone validation, and a required dropdown that bots typically fail. If a form is being hammered, add a Workflow condition that checks for junk values before any human is notified.

Privacy obligations when capturing personal information in Australia

Names, emails, phone numbers and survey answers are personal information. If the Privacy Act 1988 covers your business — most businesses with annual turnover above $3 million, plus some smaller ones such as private health service providers — the Australian Privacy Principles govern how you collect, store and use that data. Even under the threshold, the same practices are sensible risk management.

Practically, that means three things on every form or survey. First, a collection notice: a short statement at the point of collection explaining who you are, why you are collecting the information and how it will be used, linking to your full privacy policy. Second, collect only what you need — every extra field is a conversion cost and a privacy liability. Third, if you intend to send ongoing marketing, say so at capture and honour unsubscribes promptly (the Spam Act applies to follow-up emails and SMS). The OAIC publishes plain-English guidance at oaic.gov.au/privacy.

Reporting on submissions

Each form and survey has a Submissions tab showing every entry with its answers, timestamps and the contact it created — your first stop when a client says "the form isn't working" (it almost always is; the notification email went to a stale address).

For performance, look at three layers: submission volume per form over time, source attribution via captured UTM data, and downstream conversion — because submissions create opportunities via your Workflows, the pipeline view shows which forms produce leads that actually close. A form with half the volume but triple the close rate is your winner. For deeper documentation, the knowledge base at help.gohighlevel.com is kept current with each release.

Common mistakes to avoid

• Free-text fields for structured data. Dropdowns and radios keep answers clean; text boxes make segmentation nearly impossible later.
• No custom field mapping. Unmapped answers live only in the submission record, so Workflows and merge tags cannot use them.
• Skipping UTM capture on paid campaigns. Without attribution, you cannot tell which ad spend produced booked revenue.
• Forms with no Workflow attached. Every form should trigger at least a confirmation and an internal notification — unanswered leads go cold in minutes.
• Asking for contact details on the first survey slide. Lead with engaging questions; ask for details at the end, with partial capture on as a safety net.
• No collection notice. A one-line privacy statement with a policy link costs nothing and keeps Australian businesses on the right side of the Privacy Act.

If you want high-converting forms wired into automated follow-up, book a strategy call with the HL Growth Partner team.

Book Your Strategy Call →

Frequently asked questions

What is the difference between a form and a survey in GoHighLevel?

A form is single-page and suits quick opt-ins and contact pages. A survey is multi-step, supports conditional logic and partial submissions, and is the better choice for qualification, quizzes and intake questionnaires.

Can I embed a GoHighLevel form on a WordPress or Shopify site?

Yes. Every form and survey generates an iframe embed code you can paste into WordPress, Shopify, Squarespace, Webflow or any platform that accepts HTML. Submissions, custom field mapping and Workflow triggers all function exactly as they do on native GoHighLevel funnels.

How do I capture UTM parameters with GoHighLevel forms?

GoHighLevel captures standard UTM parameters (source, medium, campaign, term, content) on form and survey submissions automatically, and you can add hidden fields to pull additional query-string values onto the contact record — campaign-level attribution without the lead entering anything.

Do GoHighLevel forms support conditional logic?

Forms themselves do not branch. Conditional logic lives in the survey builder, where rules jump leads to different slides, disqualification messages or thank-you pages based on their answers. If you need branching, build a survey rather than a form.

What privacy rules apply when collecting leads from Australian visitors?

If the Privacy Act 1988 covers your business, the Australian Privacy Principles govern collection and use of personal information: provide a collection notice at capture, link to your privacy policy, and collect only what you need. The Spam Act separately requires consent and a working unsubscribe for follow-up email and SMS marketing.