How to Use Custom Fields in GoHighLevel Quizzes
The Misconception About Quiz Fields
Most people open the quiz question settings, look for a field connection option, and cannot find it. They check the Categories tab. Nothing. They search the question configuration panel. Still nothing. The field connection does not work that way in GoHighLevel, because GHL handles it automatically.
Every multiple choice question in a GHL quiz creates its own custom field in the CRM backend the moment the question is set up. There is no manual field creation step. The field exists before a single quiz is submitted.
Where the Auto-Created Fields Actually Are
To see the field for any individual question, click the gear icon on that question inside the quiz editor. Scroll to Advanced Settings. The custom field name and its unique key are shown there. That is the field GHL created automatically for that question.
To see all fields from a quiz at once, go to Settings, then Custom Fields, then Folders. GHL groups every field from a quiz into a single folder named after that quiz. A 16-question quiz produces 16 fields in that folder, one per question.
The folder view defaults to showing 10 fields per page. Change the page size to 50 to see all fields from a longer quiz in one view. This matters when you are auditing a full niche quiz and need to confirm every question has a corresponding field before wiring automations to them.
When to Add Fields Manually
The quiz creates fields for raw quiz responses. That covers most cases. But some automation logic needs values that do not come directly from a single answer.
A priority tier field, for example, might be assigned by a workflow that reads the combination of several quiz answers and calculates a tier level. An estimated deal value might be inferred from the respondent's answers about budget and timeline. A follow-up flag might be set by a separate automation after the quiz is processed and additional context is available.
These calculated or inferred values require manually created fields. They are not produced by the quiz itself. Creating them in the same Custom Fields folder as the quiz fields keeps everything organized and accessible from the same location when building downstream automations.
Submissions Tab vs the Contact Record
GHL stores every quiz submission under the Submissions tab at the top of the quiz editor. You can export submissions as a CSV from there. For occasional data pulls, the CSV works. For running a business, it is the wrong approach.
The better method connects each submission to a GHL contact via automation. When that connection is in place, every quiz response lives on the contact record in the CRM, searchable and filterable alongside every other piece of contact data. That is where the data needs to be to drive pipeline stages, trigger workflows, and feed agent conversations.
Setting Up the Contact Creation Workflow
The trigger is quiz submission. When the quiz is submitted, the workflow fires a create contact action. Map the respondent's name, email, and phone number to the corresponding contact fields. That is all the manual mapping required.
The quiz response fields populate on the contact automatically. GHL already created those custom fields from the quiz. When the contact is created, the response data attaches to the contact record because the fields exist and the quiz submission populates them. No additional mapping step is needed beyond the basic contact info.
Once this workflow is live, every quiz submission produces a searchable GHL contact with all quiz answers stored on the record. That contact feeds directly into the GoHighLevel quiz automation layer. Scoring, tagging, and routing all operate on the data now attached to that contact.
Using Custom Fields in Automations
Once quiz response fields exist on contact records, they are available as conditions in every GHL workflow. A workflow can branch based on the value of any quiz answer field. A contact who answered "Ready to buy now" on a timeline question can enter a different pipeline stage than one who answered "Still researching." The field value drives the branch without any manual sorting.
Smart lists use the same fields. You can build a filtered contact list showing every lead who selected a specific answer to a specific question. That list can trigger a broadcast email, a pipeline stage move, or a manual outreach campaign. The quiz responses are not isolated data. They are live CRM fields that the entire GHL system can read and act on.
This also means the fields persist. A quiz submitted six months ago is still queryable today. The contact record holds every answer the lead gave at the time they took the quiz, alongside every other interaction since. That is the difference between a CSV export and a proper CRM integration.
What This Enables
Every quiz response is now a contact record with structured data attached. Agents can filter by any quiz answer field. Workflows can branch on any field value. Pipeline stages reflect what respondents actually said, not just that they submitted something.
The scored quiz UI that generates these submissions, with image cards, multiple question types, and native GHL code output, is what the GoHighLevel quiz code tool builds. The custom fields are what connect that front-end experience to everything downstream in the CRM.
Build your GoHighLevel quiz and have every response stored automatically on your GHL contact records.