With the GetResponse integration, quiz takers who leave their email and agree to email marketing are added to a GetResponse list. Their answers go into custom fields, a link to their results is saved on the contact, and a tag tells you which quiz they took, so you can start autoresponders and automations from it.

Before you start: GetResponse's API is available on paid plans. On the Free plan, API keys stop working 14 days after you sign up. GetResponse MAX accounts aren't supported.

1.1 Log in to GetResponse and go to Tools, then Integrations and API, then API. You can also open app.getresponse.com/api directly.

1.2 Click Generate API key, give it a name like Lantern, and copy the key.

Note: GetResponse deletes an API key that hasn't been used for 90 days. Lantern uses the key every time a quiz taker is added, so this only happens if your quizzes add nobody to GetResponse for three months. If it does, generate a new key and paste it into Lantern, as described under Troubleshooting below.

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

2.2 Paste your key into API Key.

2.3 In List, enter the name of the GetResponse list quiz takers should join, exactly as it appears under Lists in GetResponse, or the list's ID. Capital letters don't matter. Leave it empty to use your default list: GetResponse puts every contact on a list, so Lantern needs one.

2.4 Click Connect. Lantern checks the key and the list with GetResponse, and the card shows Connected.

That's all the setup there is. Once connected, every active quiz in your store sends quiz takers to GetResponse, 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 your list with:

A new contact starts at day 0 of the list's autoresponder cycle, so your welcome autoresponders go out just like they do for a GetResponse sign-up form.

If the customer is already on the list, for example because they took the quiz before, Lantern updates their name, adds the tag and updates the answer fields. 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 sends each answer to the GetResponse custom field with the same name. You can read more about Property IDs in How to use customer answers in Lantern quizzes.

GetResponse field names only use lowercase letters, numbers and underscores, so Lantern converts the Property ID: skin_type stays skin_type, Skin-Type becomes skin_type and skinType becomes skintype. We recommend short, lowercase Property IDs with underscores, so the names match exactly.

If your GetResponse account doesn't have a field with that name yet, Lantern creates it as a text field the first time someone answers. To use another field type, create the field yourself in GetResponse first, under Contacts, then Custom fields, with the same name:

Choice questions don't have a Property ID by default, so give one to every question you want in GetResponse. A few names are reserved by GetResponse, like name, email and campaign, and answers under those names are skipped.

Every contact on a GetResponse list can receive your emails, so Lantern only adds customers who may be emailed. A customer is added when both of these are true:

Lantern never unsubscribes anyone from GetResponse. To set up the Optin Page and its consent checkbox, see Collect customer emails.

Once quiz takers arrive in GetResponse, you can:

GetResponse doesn't receive the list of recommended products itself. The results link is the way to show customers their recommendations from an email.

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

If customers stop arriving in GetResponse, the most likely reason is that the API key no longer works: it went unused for 90 days, it was deleted in GetResponse, or the account moved to the Free plan. Generate a new key in GetResponse, click Edit on the GetResponse card in Lantern, paste the new key into API Key and click Update.

If Lantern won't save, check that the key was copied in full and that the list name matches a list in your GetResponse account. You can always leave List empty to use your default list.