With the Flodesk integration, quiz takers who leave their email and agree to email marketing are added to Flodesk as subscribers. Their answers go into custom fields, a link to their results is saved with them, and they're added to segments that start your workflows: one segment you pick for the whole store, and one segment for each quiz.
Before you start: Flodesk gives out API keys on paid plans only, so you'll need a paid Flodesk plan. The free plan and the free trial can't create one.
Step 1: Create an API key in Flodesk
1.1 Log in to Flodesk and go to My Account, then Integrations, then API keys.
1.2 Click Create API key and give it a label you'll recognize, like Lantern.
1.3 Click Create API key, then Copy API key. Copy it right away: Flodesk shows the full key only once.
Step 2: Connect Flodesk in Lantern
2.1 In Lantern, open Integrations, find Flodesk under Marketing and click Connect.
2.2 Paste your key into API Key.
2.3 Optionally, enter a segment in Segment. Every quiz taker who's sent to Flodesk is added to this segment, whichever quiz they took. Type the segment's name as it appears in Flodesk, or its ID. The segment has to exist in Flodesk already. Leave the field empty if you only want the segments for each quiz (see below).
2.4 Click Connect. Lantern checks the key and the segment with Flodesk, and the card shows Connected.
That's all the setup there is. Once connected, every active quiz in your store sends quiz takers to Flodesk, with no settings to change per quiz.
What Flodesk receives
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 Flodesk, or updates them if they're already there, with:
Name: Flodesk's own First name and Last name, when the Optin Page asks for them.
Answers: one custom field for each question with a Question Property ID (see the next section).
lantern_results_url: a link to their results page, so your emails can send them back to their recommendations.lantern_quiz: the URL handle of the quiz they took, for exampleskin-care-finder.Your store's segment, when you entered one on the Flodesk card.
The quiz's own segment:
lantern-quiz-followed by the quiz's URL handle, for examplelantern-quiz-skin-care-finder. Lantern creates this segment the first time someone completes the quiz.
If the customer is already in Flodesk, for example because they took the quiz before, Lantern updates these fields and adds the segments. Their other custom fields and segments stay as they are. Flodesk is for email only, so a phone number from the quiz isn't sent.
How answers become custom fields
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 Flodesk custom field with the same name. You can read more about Property IDs in How to use customer answers in Lantern quizzes.
If your Flodesk account already has a custom field with that name, in any mix of capital and small letters, Lantern uses it. If it doesn't, Lantern creates a custom field named after the Property ID, for example skin_type. Choice questions don't have a Property ID by default, so give one to every question you want in Flodesk. Each answer is saved as text, up to 1,024 characters.
Starting workflows
Flodesk workflows start when a subscriber is added to a segment, so the segments are what you use with Lantern:
For every quiz: create a workflow whose trigger is the segment you entered on the Flodesk card.
For one quiz: pick that quiz's
lantern-quiz-segment instead. It appears in Flodesk after the quiz's first completion, so take the quiz once yourself with your own email first, or create a segment with exactly that name in Flodesk.
A customer who takes the quiz again is already in the segment, so the workflow doesn't start a second time for them. Flodesk also doesn't start a workflow for people who were in its trigger segment before the workflow was published.
Marketing consent
A new subscriber in Flodesk can receive your emails right away, so Lantern only sends customers who may be emailed. A customer is sent when both of these are true:
Email marketing is on for the quiz. On the Optin Page, open Integration Settings on the right-hand side and check Subscribe to email marketing. It's on by default, and the section appears once Flodesk is connected.
The customer didn't decline marketing. If your Optin Page shows an optional consent checkbox and the customer leaves it unticked, they aren't sent.
Lantern never unsubscribes anyone from Flodesk. If someone is unsubscribed, bounced, marked your emails as spam, or was cleaned or archived in Flodesk, Lantern leaves them as they are and sends nothing when they take a quiz again. To set up the Optin Page and its consent checkbox, see Collect customer emails.
Using quiz data in Flodesk
Once quiz takers arrive in Flodesk, you can:
Start a workflow when someone is added to your store's segment or a quiz's segment.
Show a customer's answers in an email: in a text block, type @ and pick the custom field, with a fallback for customers who didn't answer.
Show the link to the customer's recommendations the same way, with the
lantern_results_urlcustom field.See every answer on the subscriber's profile in Flodesk.
Disconnecting and troubleshooting
To disconnect, open Integrations, click Edit on the Flodesk card and click Disconnect. Lantern stops sending customers. Your subscribers, custom fields and segments stay in Flodesk.
If Lantern won't save and says Invalid API key, the key was copied incompletely or was deleted in Flodesk. Create a new one as in step 1 and paste it again.
If Lantern says there's no segment with this name or ID, check the segment's name in Flodesk, or leave the field empty.
If customers stop arriving in Flodesk, the most likely reason is that the key no longer works, for example because it was deleted or the Flodesk plan was canceled. Create a new key, click Edit on the Flodesk card in Lantern, paste it into API Key and click Update.
Good to know
Sensitive answers are not shared. Answers to questions set to Don't share or Don't store are never sent to Flodesk. See How Sensitive Data Controls Work.
Test submissions are included. Completing the quiz in Preview with an email adds that person to Flodesk too.
Changing a quiz's URL handle changes its segment name and its
lantern_quizvalue, so workflows that use the old segment stop getting new customers from that quiz.Zapier still works. If you'd rather build your own automation, the Zapier integration can also send quiz takers to Flodesk.