With the GoHighLevel integration, quiz takers who leave their email or phone number are added to GoHighLevel as contacts. Their answers go into custom fields, a link to their results is saved with them, and each quiz adds its own tag, so a workflow can start as soon as someone completes the quiz.

Before you start: Lantern connects to one GoHighLevel sub-account, the one your quiz takers should go to. If you're an agency with several sub-accounts, pick the one that belongs to this store.

1.1 Log in to GoHighLevel and open the sub-account for this store. If you land in the agency view, use the account switcher at the top left to open the sub-account.

1.2 Open Settings at the bottom of the menu on the left, then Private Integrations, and click Create new integration.

1.3 Give it a name you'll recognize, like Lantern, and give it these scopes:

1.4 Create the integration and copy the token right away: GoHighLevel shows it only once. It starts with pit-.

1.5 Copy the sub-account's Location ID too. You'll find it under Settings, then Business Profile, and it's also in your browser's address bar, right after /location/.

2.1 In Lantern, open Integrations, find GoHighLevel under Marketing and click Connect.

2.2 Paste your token into Private Integration Token and your Location ID into Location ID.

2.3 Click Connect. Lantern checks the token and the Location ID with GoHighLevel, and the card shows Connected.

That's all the setup there is. Once connected, every active quiz in your store sends quiz takers to GoHighLevel, with no settings to change per quiz.

When a customer completes a quiz and leaves their email or phone number, either on the Optin Page or in the Email sign-up on the Results page, Lantern creates a contact in GoHighLevel, or updates it if it's already there, with:

If the customer is already in GoHighLevel, for example because they took the quiz before, Lantern updates these fields and adds the tag. Their other fields and tags stay as they are. Whether GoHighLevel treats a matching email or phone number as the same person follows the Allow Duplicate Contact setting in your sub-account.

Every question can have a Question Property ID, a short name for its answer that you set in the question's right-hand panel in the quiz editor. Lantern saves each answer in the GoHighLevel custom field with the same name. You can read more about Property IDs in How to use customer answers in Lantern quizzes.

If your sub-account already has a contact custom field with that name, in any mix of capital and small letters, Lantern uses it. If it doesn't, Lantern creates a text field named after the Property ID. GoHighLevel gives the field a key in small letters, with spaces turned into underscores and other characters dropped: skin_type gets the key contact.skin_type, and skin-type gets contact.skintype. You'll use that key in your emails, texts and filters.

Choice questions don't have a Property ID by default, so give one to every question you want in GoHighLevel. Each answer is saved as text. GoHighLevel doesn't allow a custom field with the name of one of its standard fields, so an answer whose Property ID is, for example, First Name or Phone isn't saved: pick a different Property ID for it.

GoHighLevel workflows start when something happens to a contact. The quiz's tag being added is the trigger to use with Lantern:

Inside the workflow, add If/Else conditions on the answer fields to send each customer the email or text that fits their answers. A customer who takes the quiz again already has the tag, so the workflow may not start a second time.

Contacts in GoHighLevel can receive your workflows' emails and texts, so Lantern only sends what the customer agreed to:

Both switches are on the Optin Page: open Integration Settings on the right-hand side. They're on by default, and the section appears once GoHighLevel is connected. Lantern never changes a contact's DND settings in GoHighLevel. To set up the Optin Page and its consent checkbox, see Collect customer emails.

Once quiz takers arrive in GoHighLevel, you can:

To disconnect, open Integrations, click Edit on the GoHighLevel card and click Disconnect. Lantern stops sending customers. Your contacts, fields and tags stay in GoHighLevel.

If Lantern won't save, the token was copied incompletely, was deleted in GoHighLevel, or belongs to a different sub-account than the Location ID. Create the token inside the same sub-account as in step 1 and paste both again. If the token is missing one of the scopes in step 1.3, edit the integration in GoHighLevel and add it.

If customers stop arriving in GoHighLevel, the most likely reason is that the token no longer works, for example because it was deleted or rotated. Create a new token, click Edit on the GoHighLevel card in Lantern, paste it into Private Integration Token and click Update.