With the Drip integration, quiz takers who leave their email and agree to email marketing are added to Drip. Their answers go into custom fields, a link to their results and the content block variants they saw are saved on the person, a tag tells you which quiz they took, and a Completed Lantern Quiz event starts your workflows.

Before you start: Drip doesn't have a free plan. Its 14-day trial includes the API, so you can connect Lantern during the trial.

1.1 Log in to Drip and open User Settings from the menu in the top right corner, or open getdrip.com/user/edit directly.

1.2 Under API Token, copy the token.

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

2.2 Paste your token into API Token.

2.3 Leave Account ID empty unless you have access to more than one Drip account. In that case, enter the number of the account to use: it's the number right after getdrip.com/ in your browser's address bar when you're signed in to that account.

2.4 Click Connect. Lantern checks the token with Drip, and the card shows Connected.

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

When a customer completes a quiz and leaves their email, either on the Optin Page or in the Email sign-up on the Results page, Lantern adds them to Drip, or updates them if they're already there, with:

If the customer is already in Drip, for example because they took the quiz before, Lantern updates these fields and adds the tag. Their other tags and custom fields stay as they are.

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 Drip custom field with the same name, and Drip creates the field the first time it receives it. You can read more about Property IDs in How to use customer answers in Lantern quizzes.

Drip field names only use letters, numbers and underscores, so Lantern replaces any other character with an underscore: skin_type stays skin_type, skin-type becomes skin_type, and skinType stays skinType. Capital letters are kept. Choice questions don't have a Property ID by default, so give one to every question you want in Drip.

If Drip refuses one of the values, Lantern still adds the customer with their name, phone, tag and results link, without the answer fields.

If your results page uses Dynamic Content Blocks, each block shows the customer one of its variants. Lantern sends the variants each customer saw in the lantern_winner_variants custom field and in the event, separated by commas. Each variant is sent by its Variant Nice Name, or by its Variant ID when it has no Nice Name, so give your variants readable names, like Beginner program.

In a Drip workflow, add a decision that checks whether lantern_winner_variants contains a variant's name, and send each branch the email about that program or product.

Each completed quiz records a Completed Lantern Quiz event on the person, with these properties:

Every person in Drip can receive your emails, so Lantern only sends customers who may be emailed. A customer is sent when both of these are true:

Lantern never unsubscribes anyone from Drip, and someone who unsubscribed in Drip stays unsubscribed when they take a quiz again. To set up the Optin Page and its consent checkbox, see Collect customer emails.

Once quiz takers arrive in Drip, you can:

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

If customers stop arriving in Drip, the most likely reason is that the token no longer works, for example because the Drip user it belongs to was removed or the trial ended. Copy the token again from User Settings, click Edit on the Drip card in Lantern, paste it into API Token and click Update.

If Lantern won't save and says the token reaches several Drip accounts, enter the Account ID of the account to use, as described in step 2.3.