Skip to content

How to send quiz leads to MailerLite with Make

Send quiz leads to MailerLite with Make: catch Quizably's webhook, add each subscriber to a result group, save the result in a field, avoid two opt-ins.

By . 8 min read. .

To send quiz leads to MailerLite, point Quizably’s webhook at a Make scenario that starts with a custom webhook, then use MailerLite’s “Create/Update a Subscriber” module to add the person, write their quiz result into a custom field, and drop them into a group named after that result. The group starts the right welcome automation. The field keeps the latest result on the subscriber’s profile so you can filter on it later.

Quizably has no MailerLite button, so the webhook is the route. The wiring is quick. The decisions that matter come first: groups or segments, who sends the confirmation email, and what a retake should do.

Make and MailerLite both redesign their screens now and then, so I describe each step by what it does. If a label differs from what you see, follow the tool’s current help pages.

The hypothetical setup used in this guide

Juniper Lane Yoga is a hypothetical studio. Its quiz, “Which class should you start with?”, has three results: Slow Flow, Power Vinyasa and Restorative. Each result should start a different three-email welcome series in MailerLite, and the studio owner wants to see at a glance which class a subscriber was matched to.

The lead form is set to show at the end of the quiz. That placement matters later, in the double opt-in section.

Groups or segments for quiz results?

According to MailerLite’s explanation of groups and segments, a group has no rules. Subscribers are put into it by hand, by an automation step, or by another app through the API, which is what Make does. A segment is a saved filter: people move in and out automatically as they start or stop matching its conditions, and those conditions can include fields and groups.

So which do you want for quiz leads?

  • Groups are the right home for the result when it should trigger something. MailerLite automations can start when a subscriber joins a group, so “joined Quiz: Restorative” is a clean starting point for the Restorative welcome series.
  • Segments are better for looking back. A segment built on the result field (“quiz result is Power Vinyasa”) stays current without any extra work in Make, which suits a one-off campaign or a count.

My advice: do both, and let each do its own job. The scenario writes the result into a field and adds a group. Automations listen to the groups. Segments read the field.

Prepare MailerLite first

  1. Create one group per result. Use a prefix so quiz groups sort together: “Quiz: Slow Flow”, “Quiz: Power Vinyasa”, “Quiz: Restorative”. If you run more than one quiz, put the quiz name in too.
  2. Create a text field for the result. Call it something plain like “Quiz result”. A second field, “Quiz name”, is worth adding if several quizzes feed the same account.
  3. Decide on double opt-in. Read the section below before you touch the setting.

Group names don’t have to match the result titles exactly. The router in Make does the matching.

Build the Make scenario for quiz leads to MailerLite

1. Start with a custom webhook

Create a scenario and add Make’s webhook module that receives a custom webhook. Make gives you an address. Copy it, and keep it out of screenshots, because anyone holding it can push fake subscribers into your account.

2. Paste the address into Quizably

In the quiz builder’s Integrations tab, switch on the webhook, paste the address and save. If every quiz on the site should feed MailerLite, you can set it once as the default webhook URL on the Integrations screen instead. A quiz with its own URL keeps it, and a quiz whose webhook you’ve switched off stays off. The Quizably webhook documentation lists every field and the retry rules.

3. Send a real test so Make learns the fields

Take the quiz yourself with an address you control. Make should show the payload fields: event, quiz_title, result (with id and title), score, breakdown, lead (with email, name, phone and double_optin_verified) and timestamp.

Expect two messages for every visitor who fills in the form. The first has event set to lead_captured, the second submission_completed, and only the second is sure to carry the result. If the payload format is new to you, what a webhook is explains it in plain terms.

4. Filter on the event

Add a filter after the webhook that only passes bundles where event equals submission_completed, and where the lead email exists. A visitor who skips the form arrives with lead empty, and MailerLite can’t do anything without an email.

5. Create or update the subscriber

Add MailerLite’s “Create/Update a Subscriber” module. Use the MailerLite app in Make, not “MailerLite Classic”, which is for the older version of MailerLite. Connect your account, then map:

MailerLiteFrom the Quizably payload
Emaillead email
Namelead name
Quiz result (custom field)result title
Quiz name (custom field)quiz_title

Leave phone alone. The free lead form collects name and email only, so lead.phone is always empty.

Quizably’s single name field goes into MailerLite’s name field as typed. If someone enters “Priya Shah”, your greeting says “Hi Priya Shah”. That’s fine for most studios.

6. Route each result to its group

Add a router after the subscriber module, with one route per result. Give each route a filter where the result title equals “Slow Flow” (and so on), and end it with “Add Subscriber to a Group” set to the matching group.

Three results means three routes, which is easy to read in a month’s time. With ten or more results, mapping the title to a group inside one module is tidier, but harder to debug.

Double opt-in: Quizably’s or MailerLite’s, not both

Both tools can ask people to confirm their address, and if you leave both on, a new lead gets two confirmation emails a minute apart. Choose one.

Option A: let MailerLite confirm. Turn Quizably’s double opt-in off for the quiz. In MailerLite, the setting “Double opt-in for API and integrations” lives under Account settings, Subscribe settings, per MailerLite’s double opt-in help page. Switched on, it sends a confirmation email to people added through the API, which includes your Make scenario. The scenario above works unchanged.

Option B: let Quizably confirm. Turn on double opt-in for the quiz in Quizably and leave MailerLite’s API setting off. The catch: the submission_completed message is sent before the person clicks, with double_optin_verified set to false, and it is not sent again after they confirm. So change the filter in step 4 to act on lead_captured instead, which Quizably sends only after the click.

That message includes the result only if the visitor had finished the quiz by then. With the form at the end of the quiz, as at Juniper Lane, they always have, so the router still works. With the form before the quiz, someone who confirms mid-quiz arrives with no result. Quizably’s confirmation email is plain text and can only be changed with a code filter, which is a fair reason to prefer Option A.

Rules on consent vary by country, and I can’t give legal advice. Note that the webhook carries no consent flag, so if you use the consent checkbox, MailerLite won’t know it was ticked.

What happens when someone takes the quiz twice?

MailerLite’s create-or-update matches on email, so a retake updates the same subscriber instead of creating a duplicate. Two details from MailerLite’s subscriber API reference shape what you see next:

  • Fields are overwritten. The Quiz result field now shows the newest result. Your segments follow it.
  • Groups pile up. The create-or-update call is non-destructive: groups can be added this way but are never removed by leaving them out. Someone who got Slow Flow and then Power Vinyasa ends up in both groups and may get both welcome series.

If that bothers you, add a “Remove Subscriber from a Group” step to each route for the other result groups. For a small list, I’d skip it and accept the overlap.

Also keep in mind that the API won’t reactivate someone who unsubscribed, bounced or was marked as junk; MailerLite reserves that for its own forms and landing pages. A retake from an old unsubscriber won’t put them back on your list.

Test every result, then keep a backup

Take the quiz three times with three test addresses, once per result. For each, check:

  1. Did Make’s run history show every module succeeding?
  2. Is the subscriber in MailerLite with the right name?
  3. Does the Quiz result field show the expected title?
  4. Are they in exactly one quiz group?
  5. Did the matching welcome automation start?

Then retake with one address and a different result, and check the field and groups.

Delivery runs in the background on WP-Cron, and a failed send is tried again up to three times, roughly 1, 2 and 4 minutes apart. If your host disables WP-Cron and nothing else runs it, no message leaves the site. There’s no delivery log in Quizably, so turn on “Email me on new leads” under Settings, Notifications as a second signal. If the scenario stops for a day, export those leads as CSV from the Leads screen and import them into MailerLite by hand.

Where to go from here

The subscribers are in. Now the welcome series has to earn its place: quiz follow-up emails shows a five-email sequence you can adapt per group. If you’d also like a running log of every submission next to MailerLite, the Google Sheets version of this Make scenario can sit on the same webhook with a second route.

And to see where list building fits in the bigger picture, the quiz marketing guide puts it in context. If you’re still picking a plugin, how to choose a WordPress quiz plugin explains why a webhook belongs on the checklist.

Frequently asked questions

Does Quizably have a MailerLite integration?

Not a built-in one. Quizably posts every submission to a webhook address, and a Make scenario turns that message into a MailerLite subscriber. You build it once and it runs for every quiz that uses the address.

Should I use MailerLite groups or segments for quiz results?

Groups, if you want an automation to start the moment someone arrives, because a group is something a subscriber is put into. Segments are rules MailerLite keeps up to date for you, so they suit reporting and one-off campaigns built on the result field.

Will subscribers get two confirmation emails?

They can, if double opt-in is on in Quizably and MailerLite's double opt-in for API and integrations is on as well. Pick one of the two and switch the other off.

What happens when someone retakes the quiz with the same email?

MailerLite updates the existing subscriber instead of creating a second one. The result field takes the newest value, but group memberships are only added, never removed by omission, so the person can end up in two result groups unless your scenario removes the old one.

Can I send the quiz answers or UTM tags to MailerLite?

Not through the webhook. Its payload carries the quiz, the result, the score, a breakdown and the lead's name and email, but no individual answers, UTM values or consent flag. Those are in the Leads CSV export.

Keep reading