QSM MailChimp Integration - WordPress Plugin

Guide to Setting Up QSM MailChimp Integration for Quiz Funnels in WordPress

QSM MailChimp Integration is not just for pushing addresses from a form into an email list. In a real working setup, it connects a quiz or survey in Quiz and Survey Master to a Mailchimp audience, helps pass contact fields, subscribe the participant manually or automatically, add tags based on the result, and verify that the contact actually appears in the right list.

This guide focuses on the practical side: what to prepare before installation, where to find the settings after activation, how to choose a Mailchimp list for a specific quiz, when to show a consent checkbox, how to work with double opt-in, how to use a minimum score and score-based tags, and how to troubleshoot cases where a contact does not make it into Mailchimp.

This material is written for a site owner, marketer, webmaster, or developer who already understands why they need a quiz form but wants to configure the integration without guesswork. It does not cover purchasing, license bypassing, or manual work with other people's data. The focus is safe setup of a product you already have, result verification, and careful day-to-day use.

If the product page already has a short description above this section, treat this guide as the continuation: it shows how to turn the integration from an installed add-on into a clear, working lead generation flow.

What problem the QSM and Mailchimp integration solves

Quiz and Survey Master itself handles questions, answers, results, scores, contact fields, result pages, and displaying the quiz on the site. Mailchimp handles audiences, contacts, subscription statuses, tags, merge fields, and follow-up email communication. QSM MailChimp Integration sits between them: it takes the data a user submits while completing a quiz or survey and sends it to the selected Mailchimp audience.

The real value shows up when the quiz stops being a standalone interactive block and becomes the entry point to segmented communication. For example, a visitor takes a quiz about their level of readiness, enters an email address, sees the result on the site, and lands in Mailchimp with a tag based on their score range. After that, you can send something more targeted than a generic newsletter, such as a message matched to that person's interest level or skill level.

The official product page confirms several key capabilities: adding quiz or survey participants to Mailchimp lists, selecting a list for each quiz, passing name, business, phone, and score-related data when those fields exist, showing a checkbox or subscribing automatically, double opt-in, a minimum score required for subscription, and mapping tags to quiz scores. The documentation also shows that once the API key is accepted, a separate MailChimp Integration tab appears when editing a quiz.

Where the product is useful in practice

The integration is most valuable in scenarios where the quiz or survey already collects meaningful responses. For example:

• A lead magnet with a personalized result, where an email address is needed to continue the conversation after the quiz is completed.
• An educational quiz where a high score moves the participant into a "ready for the next level" segment, while a low score moves them into a segment with foundational materials.
• A post-purchase or post-event customer survey, where the responses help identify interested groups in Mailchimp.
• A pre-launch marketing survey, where tags reflect interest in specific directions or offers.
• A content funnel where the final score or contact fields are used for later personalization.

One important nuance: the plugin does not replace your email strategy and it does not build Mailchimp automation for you. It passes the input data. What you do with the audience, tags, and segments afterward still needs to be planned inside Mailchimp.

When the add-on may be unnecessary

QSM MailChimp Integration is not needed if your quiz does not collect email addresses, if you do not use Mailchimp, if all responses only need to be stored in WordPress, or if subscription should happen through a different automation system. It can also be too limited when you need complex data delivery to several services at once. In that case, QSM Webhooks or Zapier Integration may be a better fit because they are designed for broader event exchange.

Practical rule of thumb: use QSM MailChimp Integration when you already have a specific Mailchimp audience, a clear reason to collect email addresses through a quiz, and at least one follow-up communication scenario. If you do not know what email, segment, or automation should happen after the contact is sent, design the funnel first.

What to check before installation and first launch

Before you install the add-on, do not start with the Upload Plugin button. For Mailchimp integration, what matters is not just the WordPress plugin files, but also whether the quiz, contact fields, Mailchimp audience, and consent policy are ready. The earlier you verify those pieces, the fewer false errors you will see after turning it on.

Basic WordPress and QSM readiness

The main Quiz and Survey Master plugin must already be installed and working on the site. QSM on WordPress.org is described as a plugin for building quizzes, surveys, and forms, and it also shows that a quiz can be displayed through a shortcode, widget, or Gutenberg block. That matters for Mailchimp integration: a contact only reaches the audience after someone actually completes the quiz or survey, not simply because the add-on is installed.

Check that:

• The core QSM plugin is updated to a version suitable for your site.
• The quiz or survey has already been created, opens on the public side of the site, and submits results without errors.
• The quiz includes an email field or contact form, because Mailchimp cannot subscribe a contact without an address.
• You know where the quiz is displayed: on a page, in a post, through a widget, or through a QSM block.
• You can safely send several test submissions on a staging site or test copy.

The official QSM documentation separately warns that the same quiz shortcode should not be displayed twice on the same page. That is also a useful check for Mailchimp integration: if the same form appears twice on the page, submission or result-tracking issues may look like a Mailchimp problem even though the real cause is how the quiz is embedded.

Mailchimp audience and API key readiness

In Mailchimp, prepare the audience ahead of time that participants should be added to. In Mailchimp documentation, an audience is effectively the list of contacts, and a contact or member exists within a specific audience. Because of that, a "subscribe everyone somewhere" setup is a bad idea: each quiz should have a clearly defined destination list.

Use a dedicated API key for this integration. Mailchimp explicitly warns that API keys provide full account access and should be protected like a password. In practical terms, that means:

• Create a separate API key with a clear name, such as one tied to the site and QSM.
• Do not expose the API key in screenshots, training videos, public documents, or tickets unless it is fully masked.
• Do not pass the key into Codex, to contractors who do not need it, into public chats, or into theme source code.
• If the key is exposed or a staff member should no longer have access, revoke the key in Mailchimp and create a new one.

The QSM Mailchimp documentation says the API key is entered in the add-on settings, after which a MailChimp Integration tab appears when editing a quiz. If that tab does not appear, check the key save and add-on activation first, not the Mailchimp audience.

The legal and user-facing logic of consent

The integration can show a subscription checkbox or hide it and subscribe participants automatically. That is not just a UX preference. It affects user expectations, list quality, and the risk of complaints. If the quiz is a lead magnet with an explicit email offer, a checkbox with clear wording is usually the safer option. If the quiz is restricted to already registered participants and the subscription terms are explained in advance, automatic subscription may be acceptable, but it should still align with your data handling policy.

Double opt-in adds a second step: the user enters a waiting state and must confirm the subscription through a Mailchimp email. In the Mailchimp API, the pending status corresponds to a confirmation-based subscription, while subscribed means the subscription is already active. If you enable double opt-in, do not promise that the contact will immediately start receiving emails, because confirmation may still be pending.

Pre-launch check: submit a test quiz using your own address and then check the status separately in Mailchimp. If double opt-in is enabled, do not assume the integration is broken until you have checked the confirmation email and the contact status.

Installing the add-on and doing the initial admin check

The official QSM documentation describes two ways to install add-ons: through QSM Addon Installer and manually by uploading the ZIP file like a regular WordPress plugin. For this guide, the key point is not the purchase flow, but the safe technical sequence after you already have the file or access to the add-on.

Installation through QSM Addon Installer

If the site uses QSM Installer, open QSM > Extensions > Addon Installer. According to the documentation, this area lets you manage activated add-ons and their installed settings. Find MailChimp Integration among the available extensions and enable it using the method available under your license. After activation, check the Installed tab, because that is usually where you will find the link to the activated add-on settings.

This path is convenient on sites that use bundle licenses and multiple add-ons. It reduces the risk of uploading the wrong ZIP file or forgetting to activate the installed extension. But if you have a standalone add-on file, manual installation is still a perfectly valid option.

Manual ZIP upload

The manual method is similar to installing any WordPress plugin:

1. Open Plugins > Add New in the WordPress admin.
2. Click Upload Plugin and select the add-on ZIP file.
3. Click Install Now and wait for the installation to finish.
4. Activate the plugin when WordPress shows that the installation succeeded.
5. Find the activated QSM - MailChimp Integration in the plugin list or in the QSM extensions area.

After activation, do not jump straight to the public quiz page. First make sure the add-on appears in the QSM admin area and that the global Mailchimp settings are available. If the tab is missing, open the Plugins list and confirm that the MailChimp Integration add-on itself is active, not just the core QSM plugin.

Your first controlled test submission with as few variables as possible

Before using a live quiz, create or use a test quiz with minimal logic: a few questions, a required email field, and a clear result page. Do not turn on complex conditions, score tags, multiple email templates, or aggressive caching right away. Your first job is to prove that the basic chain of "QSM contact field -> Mailchimp audience" works.

Minimum test:

• Create an audience in Mailchimp or choose an existing test audience.
• Generate a separate API key and save it in the global QSM Mailchimp settings.
• Open the edit screen for the target quiz and enable MailChimp Integration only for that quiz.
• Select one audience and turn on the checkbox display so consent is visible in the form.
• Complete the quiz like a regular visitor in a private browser window.
• Check the contact in Mailchimp: it should appear in the selected audience, or show a pending confirmation status if double opt-in is enabled.

This test matters because most later issues are easier to diagnose once the basic channel is already confirmed. If the contact does not appear even in a simple setup, adding score mapping will only make troubleshooting harder.

Global API key setup and access security

The global API key is the bridge between your WordPress site and Mailchimp. QSM documentation explicitly says that to use the add-on, you need a Mailchimp account and an API key entered in the add-on settings. Once the key is saved, the add-on should unlock quiz-level settings where you choose the list and subscription behavior.

How to get and save the key without exposing it

In Mailchimp, the API key is created in the account settings: profile, Extras, API keys, then create a new key. Mailchimp emphasizes that the full key is visible only immediately after generation. If you do not save it in a secure place right away, you cannot simply reopen it and copy it later - you will need to create a new one.

A practical process looks like this:

1. Create the key with a descriptive name tied to the site and QSM.
2. Immediately copy it into a secure location accessible to the site administrator.
3. Paste the key into the add-on settings in WordPress.
4. Save the settings and refresh the admin page.
5. Confirm that the MailChimp Integration tab appears when editing a quiz.

Do not place the key in client notes, public documentation, task descriptions, or screenshots. If you need to show a problem to support, remove the key from the image completely instead of only blurring a few characters.

Why one key for every integration is a bad habit

Mailchimp recommends giving each integration its own API key. That is not just a formality. If one shared key is used for QSM, a CRM, a custom script, and an external service, then when it leaks you will not know which channel caused the problem, and you will be forced to break all integrations at once. A dedicated key for QSM MailChimp Integration lets you revoke only that access and then update the setting in WordPress.

For a small site, a simple access table is enough: the name of the integration, where the key is used, who is responsible for it, and when it was last rotated. You do not need a complex system, but you do need to understand that the API key is equivalent to access to Mailchimp data.

What to check after saving the key

After saving the API key, verify three things:

• The tab appears in quiz settings. QSM documentation describes a separate MailChimp Integration tab appearing after the key is accepted.
• The audience list loads. In the quiz settings, you should be able to select a list tied to the Mailchimp account.
• There is no save error message. The add-on changelog previously mentioned a fix for the success message while saving add-on settings, so always evaluate not just the message itself, but whether the tab and list are actually available.

If the list does not appear, do not rush to change the quiz. First check the key, the Mailchimp user permissions, the presence of an audience, the site's ability to reach Mailchimp over the network, and whether a security plugin or hosting layer is blocking the request.

Configuring subscription settings inside a specific quiz

QSM MailChimp Integration is not enabled globally for every quiz at once. It is configured per quiz, and that is the right model: different forms can send to different audiences, use different checkbox wording, and apply different score-based subscription rules. One quiz may act as a lead magnet, another may be an internal assessment for existing customers, and a third may be a research survey with no subscription at all.

Enabling the integration and choosing an audience

Open the target quiz in QSM and go to the MailChimp Integration tab. The documentation says you will see the question Enable mailchimp integration for this quiz?. For a working quiz, set it to Yes. Then choose the list or audience where participants should be added.

Choosing the audience is not a minor technical detail. In Mailchimp, a contact exists inside an audience, and the same email address can have different statuses in different audiences. So define the rule in advance:

• One product-specific quiz - one dedicated audience, if you run independent communication around it.
• One shared audience plus tags - if you want to keep the database in one place and handle segmentation with tags.
• A test audience - for initial validation before launch on real traffic.

In many projects, one main audience plus separate tags is easier to manage because it simplifies subscriber and campaign management. But if you already have a strict Mailchimp structure in place, do not change it just to fit the add-on. The integration should fit into your data model, not replace it.

Subscription checkbox or automatic add

The setting Display checkbox for optional subscribing or hide checkbox for automatic subscribing? determines whether the participant sees an explicit subscription checkbox. The Show option works best for most public quizzes where the user should make an active choice. The Hide option subscribes them automatically after quiz submission, if that aligns with your legal and user-facing rules.

For a public site, it is usually safer to start with a checkbox. The text beside it should be specific, not vague. For example, instead of "Subscribe," it is better to say what the user will receive: "Receive an email with your result and follow-up materials related to the quiz topic." Do not promise anything your Mailchimp flow does not actually send.

If you hide the checkbox, add a clear explanation near the form or in the text before the quiz. Automatic subscription without context lowers list quality: people are more likely to complain, skip double opt-in confirmation, or ignore your emails.

Double opt-in: when to enable it and how to test it

The setting Keep double opt-in for this subscription? controls email confirmation for the subscription. When double opt-in is enabled, the contact does not become an active subscriber immediately. They must confirm through a Mailchimp email. From a troubleshooting standpoint, this is critical: the participant may have been created, but still may not be receiving campaigns.

Double opt-in is worth enabling when:

• You want higher list quality and a lower risk of accidental or invalid email addresses.
• Your traffic comes from colder sources where mistyped addresses are more likely.
• Your subscription policy requires explicit confirmation.
• You send ongoing marketing emails, not just a single service message.

Turning off double opt-in may make sense for controlled forms where consent has already been explicitly collected and you need the contact to move quickly into an active segment. But do not treat it as a setting you disable just to reduce clicks. Evaluate the legal and reputational side first.

Minimum score required for subscription

One of the product-specific features in QSM MailChimp Integration is subscribing only when a minimum score is reached. The official product page and documentation describe this as a way to subscribe quiz takers only when they pass the quiz or achieve a defined score.

This is useful in educational and qualification quiz scenarios. For example, you can subscribe only people who reached a passing score into the main audience, while leaving others unsubscribed or routing them through a different follow-up path. But use this filter carefully. If the purpose of the quiz is lead generation and follow-up education, excluding people with a low score may remove the very participants who most need introductory material.

A practical rule: enable minimum score when subscription acts as a reward, access gate, or step into the next level. Do not enable it if the quiz is meant to segment all participants.

Result-based tags and score mapping

Mailchimp tags help organize contacts and build segments. Mailchimp documentation describes tags as labels for organizing contacts, and the QSM MailChimp Integration page mentions Mailchimp Tags and Quiz Score Mapping. In QSM, that becomes a simple marketing mechanic: you can assign a tag to a participant based on the score they achieved.

A good tag structure should be short and readable. Do not create dozens of nearly identical tags for every percentage point. In most cases, 3 to 5 ranges are enough:

Example tag logic for a quiz funnel

Result range	Possible tag	Follow-up action
Low score	qsm-beginner	Send foundational material and explain the first steps.
Mid-range score	qsm-intermediate	Offer a practical checklist or a series of exercises.
High score	qsm-advanced	Send advanced content, an invitation to a consultation, or the next assessment.

After saving the mapping, make sure to complete the quiz several times with different test addresses and different score outcomes. Do not just verify that the person was subscribed. Also check that the correct tag appears in the contact profile. If tags do not show up, review the score ranges, subscription status, whether the integration is enabled for that specific quiz, and whether the API key is still valid.

Passing name, phone, business, and score into Mailchimp

Sending only the email address is the bare minimum. The integration becomes more useful when Mailchimp also receives the participant's name, last name, phone, business, and final score, assuming you actually collect that information. The official QSM Mailchimp documentation explains that to pass user information, you need to configure Mailchimp merge fields, and that the FNAME tag is used for the first name. The product page also mentions passing name, business, and phone when that data is collected.

Why merge fields need to be prepared in advance

Mailchimp does not automatically know what your fields in QSM are called. If you want to pass a first name or business value, the corresponding merge fields must exist in the audience. The QSM documentation shows the path through Mailchimp list settings and List fields and *|MERGE|* tags. That is where you can add a field and define the tag Mailchimp will expect.

In practice, the setup looks like this:

1. Open the target audience in Mailchimp.
2. Go to the field settings and merge tags.
3. Check whether the standard first name and last name fields exist, if you need them.
4. Add separate fields for phone, company, or score if those values need to be stored in the profile.
5. Save the audience structure before testing QSM.

Do not create fields "just in case." Every extra field makes the form, data storage, and later segmentation more complex. If the data is not used in emails, segments, or analytics, it is better not to collect it.

Contact fields in QSM and data quality

QSM has to actually collect the data before it can send it to Mailchimp. If your quiz does not include a phone field, the integration cannot pass a phone number. If the user leaves the name blank, it will also be blank in Mailchimp. That sounds obvious, but this is where expectations often break: the administrator configures a merge field in Mailchimp but forgets to add the corresponding field to the contact section of the quiz.

For lead generation, email and first name are usually enough. Phone and business should only be requested when they are needed for the next step. The more fields you place before the quiz result, the higher the risk of incomplete submissions and abandonment.

Score as useful data, not a decorative number

The QSM Mailchimp documentation mentions the TOTAL SCORE merge tag, which allows the final score to be sent to Mailchimp along with other data. That is useful when the score is not only used for tagging, but also as a variable in personalization or internal analytics. For example, you can see in Mailchimp that a contact earned a high score, while QSM keeps the detailed answers.

But score should not replace tags. Tags are more convenient for segmentation and campaign triggers, while score is better for storing the exact value. In many cases, the best model is this: store the score in a separate merge field, and convert the score range into a tag. That way the marketer sees both the precise number and the working segment.

Quick takeaway: first create the fields in Mailchimp, then make sure QSM is actually collecting the matching data, and only then test the transfer. If you start testing before the merge fields are prepared, the error will look like an add-on problem even though the real cause is the audience structure.

Practical scenario: a lead quiz with segmentation by readiness level

Let's walk through a scenario that clearly shows the value of QSM MailChimp Integration. Suppose the site has an educational quiz called "Check Your Readiness to Launch an Email Funnel." The goal is to collect an email address, show the result on the site, and send the participant into Mailchimp with a tag based on their readiness level.

Goal and preparation

We need three outcomes:

• The participant completes the quiz and leaves an email address.
• A contact is created or updated in the selected Mailchimp audience.
• The contact receives a score-based tag: beginner, intermediate, or advanced.

Before configuration, you need a working QSM quiz, an email field in the contact form, a separate Mailchimp audience, an API key, several test email addresses, and a clear understanding of which score ranges map to which tags. If you use double opt-in, prepare the confirmation email wording in Mailchimp ahead of time so the user understands why they need to confirm the subscription.

Configuration steps

1. In QSM, create a quiz with questions that produce a total score. Do not make the first test too long: 5 to 7 questions are enough for validation.
2. Add a required email field. If you want to personalize the email, add a first name field too.
3. Save the quiz and place it on a test page using a QSM block or shortcode.
4. Save the API key in the global QSM MailChimp Integration settings.
5. Open the MailChimp Integration tab inside the quiz and enable the integration.
6. Select the audience where the participant should be added.
7. Set the checkbox to Show if you want explicit consent, and write clear text next to it.
8. Decide whether to enable double opt-in. For a public lead quiz, it usually makes sense to test both options on staging and choose the one that matches your subscription policy.
9. Configure score mapping: the low range gets quiz-beginner, the middle range gets quiz-intermediate, and the high range gets quiz-advanced.
10. Save the quiz settings.

Verifying the result

Now complete the quiz at least three times with different test addresses, each time aiming for a different score range. After every submission, check:

• Whether the quiz submitted successfully on the site.
• Whether the contact appeared in the correct Mailchimp audience.
• What status the contact has: subscribed, pending, or something else.
• Whether the first name was passed, if you collect it.
• Whether the correct result-based tag was added.
• Whether the contact was accidentally created in another audience because the wrong list was selected.

If double opt-in is enabled, do not expect an immediate active subscription. Check the inbox for the test address, confirm the subscription, and then refresh the contact profile in Mailchimp.

A detail that often gets in the way of testing

The most common false conclusion is "the integration does not work" when the real issue is that the user did not check the subscription box, did not confirm the double opt-in, or did not reach the minimum score. So test the settings one at a time. First enable the checkbox and check it manually. Then test automatic mode. Then enable the minimum score rule. Only after that should you add tag mapping.

That order may feel slower, but it saves time. You always know which new setting changed the behavior.

How to verify the result without guessing

Result validation should be just as strict as the setup itself. It is not enough to stop at a "quiz submitted" message on the site. QSM and Mailchimp are two separate systems, and a successful quiz submission does not prove that the subscription succeeded.

Checking in WordPress

In WordPress, make sure the quiz saves the entry or shows the expected result. If the quiz itself does not complete correctly, the Mailchimp integration may never receive data to send. Check the result page, the email field, required fields, and the absence of JavaScript errors in the form.

If the quiz is embedded through a shortcode, confirm that the shortcode is not duplicated on the same page. QSM documentation warns that placing the same quiz shortcode twice on a page can create problems. For a clean test, keep a single instance of the quiz on a dedicated page.

Checking in Mailchimp

In Mailchimp, do not just search by email. Open the contact record and check:

• Which audience the contact belongs to.
• What the subscription status is.
• Which merge fields are filled in.
• Which tags are assigned.
• Whether the email address had previously been unsubscribed or cleaned.

Mailchimp API documentation lists several contact statuses: subscribed, unsubscribed, pending, cleaned. If the contact has a problematic status, that is not always a QSM error. Mailchimp may be refusing to send campaigns to that contact or may still be waiting for confirmation.

Checking the data path

For more complex cases, it helps to write out the data path in a short sequence:

1. The user opened a page with one instance of the quiz.
2. They entered an email address and, if needed, checked the consent box.
3. QSM saved the submission and calculated the score.
4. MailChimp Integration detected that the setting was enabled for this quiz.
5. The add-on selected the correct audience and sent the email, merge fields, score, and tags.
6. Mailchimp accepted the contact or placed it into the appropriate status.

Once you know the route, troubleshooting becomes concrete. An issue at step 2 is about the form and consent. An issue at step 3 is the quiz itself. An issue at step 4 is add-on configuration. An issue at step 5 is mapping, the API key, or the audience. An issue at step 6 is contact status, Mailchimp policy, or the state of that specific email address.

Tags, score, and updating existing subscribers

In recent add-on changes, the developer added features that matter especially for repeat submissions and segmentation. The product page changelog mentions an option to enable or disable updating existing subscribers, and earlier changes related to updating subscriber details, updating tags for existing subscribers, score-based tags, and total points in Mailchimp. You do not need to tie those features to specific dates in the article, but you should take their presence into account when configuring the add-on.

What changes when someone retakes the quiz

A user may complete the quiz again using the same email address. In that case, several strategies are possible:

• Leave the existing contact unchanged if repeat attempts should not affect the segment.
• Update details if the name, business, phone, or score may have changed.
• Update tags if the latest result matters more than the previous one.
• Add new tags if you want to preserve a history of interests through accumulated labels.

The right choice depends on the scenario. For a qualification test, the latest result is often the important one: the person may have completed training and scored higher. For a marketing survey, it may be more important not to lose older tags because they reflect different interests.

How not to turn tags into chaos

Score-based tags are only useful if your naming stays disciplined. Do not mix tags like Passed, passed_quiz, Quiz Passed, and quiz-pass for the same meaning. Pick one consistent format. For example:

• qsm-lead-beginner
• qsm-lead-intermediate
• qsm-lead-advanced
• qsm-survey-product-feedback

The qsm prefix helps distinguish tags that came from a quiz from tags created manually or by other integrations. The middle part identifies the campaign or scenario. The final part reflects the result level or segment.

What to do with outdated tags

The Mailchimp API supports adding and removing tags through explicit status changes, but QSM add-on settings should be used according to the documented UI, not through custom API workarounds. If you do not see an option in the add-on settings to remove old tags, do not invent a workaround by editing the plugin. Instead:

• Configure tags so they do not conflict with each other.
• Use a separate timestamp or score field if you need to know how current the result is.
• Clean up segments in Mailchimp periodically using its native tools.
• Review the add-on documentation after updates in case a new option for existing subscribers has been added.

In a setup guide, it is important not to promise something the plugin cannot do. If your version of the add-on does not include a specific option, work within the available settings and record any uncertain behavior in the project team's notes.

Compatibility, performance, and keeping data tidy

QSM MailChimp Integration works in a standard chain of WordPress plugin, QSM quiz, public page, and the external Mailchimp API. That means the behavior can be affected not only by the add-on settings, but also by the theme, cache, JavaScript optimization, blocked external requests, security settings, and the state of the Mailchimp account.

Caching and script optimization

If the quiz is placed on a public page, a caching plugin or JavaScript optimizer can interfere with the form. You do not need to disable all caching across the site ahead of time, but for the quiz page, it is worth checking:

• Whether scripts are being combined in a way that breaks the submit button.
• Whether important QSM JavaScript is delayed until after the form is already trying to submit.
• Whether the result page is being cached with someone else's data.
• Whether the same quiz is inserted twice on the page.

If the issue only appears on the public page, but not in preview or with optimization disabled, first exclude the quiz page from aggressive script optimization. That is safer than randomly changing Mailchimp settings.

Conflicts with the theme and page builders

WordPress.org support threads for QSM show a range of user issues: UI, compatibility, submit button behavior, email delivery, and result page problems. Those topics do not prove a specific conflict with the Mailchimp add-on, but they do show the typical attention areas on QSM-based sites: quiz rendering, form submission, email logic, result pages, and environment compatibility.

If the quiz is embedded inside Elementor, Site Editor, a custom widget area, or a complex landing page, run a control test on a plain WordPress page with a single QSM block or shortcode. If everything works there, the problem is more likely in the layout, builder, or scripts than in the Mailchimp API key.

Data you should not collect

The integration can pass more than an email address, but that does not mean you should ask for everything. For a public quiz, keep fields to a minimum:

• Email - required for subscription.
• First name - useful for personalization if it is actually used in emails.
• Phone - only if there will be a real call or consultation afterward.
• Business - only for a B2B scenario where the company affects segmentation.
• Score - if you use it for tags, segmentation, or personalization.

Collecting unnecessary data lowers conversion and increases your responsibility for storage. If a field is not part of the actual workflow, do not add it just because it "might be useful later."

Launch plan: from a test audience to a live quiz funnel

After configuring the API key, audience, checkbox, double opt-in, and score mapping, the most risky phase remains: moving the setup from testing to live traffic. This step is often skipped. An administrator sees a contact appear in Mailchimp once and immediately publishes the quiz on a paid traffic page. That sometimes works for simple forms, but for QSM MailChimp Integration it is better to go through a short launch cycle.

The reason is that the integration depends on several layers. WordPress must render the quiz without a theme conflict, QSM must accept the submission and calculate the score correctly, the add-on must apply the settings for the current quiz, Mailchimp must accept the contact, and your follow-up campaign must catch the right status or tag. A failure at any level can look exactly the same to the user: "I finished the quiz, but I did not get anything."

Test matrix before publishing

Before launch, create a small test matrix. It does not need to be bureaucratic. Six to eight rows are enough, as long as they cover the real behavior branches:

Minimum launch matrix for a QSM Mailchimp quiz

Scenario	What to submit	What should appear in Mailchimp	When to count the test as passed
New participant with consent	New email, checkbox checked	Contact in the correct audience, correct status, base tag	The email is found, and the tag and merge fields match expectations.
New participant without consent	New email, checkbox not checked	The contact should not be subscribed if optional mode is selected	The behavior matches the text shown next to the checkbox.
Double opt-in	Email with confirmation enabled	Status pending before confirmation, then an active subscription	The confirmation email arrives and the status changes after the click.
Low score	Answers that produce the minimum range	A low-level tag, or no subscription if minimum score is enabled	The result matches the configured score mapping logic.
Returning participant	The same email with a different score	Data is updated or left unchanged according to the existing subscriber setting	The team understands which behavior is chosen and why.

This table is especially helpful when more than one person is involved in the setup. The marketer can see which segments are needed in Mailchimp, the webmaster can verify the form and on-page rendering, and the WordPress administrator can see which settings should not be changed without retesting.

Moving from a test audience to the live audience

If you tested on a separate audience, do not forget to change the list in the settings of the specific quiz before publishing. After switching audiences, repeat at least two tests: one new email with the expected tag and one submission with double opt-in, if it is enabled. Do not move only the API key - the audience selection is stored at the quiz level, so this is exactly the step people forget most often.

Before launch, also make sure test tags do not remain in the live setup. If you used tags like test-beginner or draft-score-low, replace them with production names and run the quiz again. In Mailchimp, tags quickly become part of filters, automations, and manual segments, so sloppy test names are harder to clean up later.

Rollback without losing data

Your rollback plan should be clear before publishing. For QSM MailChimp Integration, a safe rollback usually does not mean removing the add-on or cleaning Mailchimp. It usually means temporarily disabling the integration for a specific quiz or returning the checkbox or double opt-in setting to the previous mode. That way you do not break the quiz itself and you do not lose the results stored in QSM.

If you discover a problem after launch, respond based on the impact:

• If the quiz works but tags are not being assigned, keep the form live and fix the mapping on staging or in a limited test.
• If subscriptions are going to the wrong audience, temporarily disable integration for this quiz and correct the list selection.
• If the form does not submit, roll the page back to a simpler version without aggressive optimization and test QSM independently of Mailchimp.
• If the API key is compromised, revoke it in Mailchimp, create a new one, and update the global add-on settings.

After the fix, do not blindly clean the production database. First export or mark the affected contacts in Mailchimp, estimate the scope, and only then decide whether you need to remove test contacts, change tags, or send a clarification email. For a small tag mapping issue, it is often enough to correct the segment and leave the subscribers themselves untouched.

Launch principle: any change to the audience, checkbox mode, double opt-in, minimum score, tag ranges, or existing subscriber update behavior requires at least one new control submission. That is faster than cleaning up incorrect contacts after paid traffic hits the page.

Video on setting up the Mailchimp add-on

The official product page includes a link to the video MailChimp Integration Addon in action. You can use it as a visual companion to the sections on installation, API key setup, and enabling the integration inside a quiz. The video does not replace actual testing, but it helps you see the overall path through the interface.

Even after watching it, run your own test quiz and check the contact in Mailchimp. The add-on and Mailchimp interface may differ from the video, and real verification always depends on your audience, checkbox setting, double opt-in, and score mapping.

Why a contact does not appear in Mailchimp and how to find the cause

Troubleshooting works best when you follow the chain instead of going by instinct. The integration has several required conditions: an active add-on, a saved API key, quiz-level activation, an email field, a selected audience, valid consent, a sufficient score if that filter is enabled, and a successful response from Mailchimp.

The MailChimp Integration tab does not appear in the quiz

Symptom: the add-on is installed, but there is no separate MailChimp Integration tab when editing the quiz.

Possible causes: the add-on is not activated, the wrong plugin is activated, the API key was not saved or accepted, there is an admin UI conflict, or the QSM core or add-on version is outdated.

What to check: the WordPress plugins list, the QSM extensions section, the global add-on settings, whether the API key was saved, and whether any admin errors appear after saving. If the tab appeared after saving the key again, the problem was at the global level.

How to fix it: activate the add-on, save the key again, update the QSM core and add-on using the standard process, then reopen the quiz edit screen in a new window. If the site uses admin optimizers or security plugins, test temporarily without them on staging.

The contact is not created after quiz submission

Symptom: the user completed the quiz, but the email address cannot be found in the selected Mailchimp audience.

Possible causes: the integration is not enabled for that specific quiz, the email field is empty or not required, the user did not check the checkbox, the wrong list was selected, the API key lacks access, Mailchimp rejected the contact, or page scripts broke submission.

What to check: the quiz submission itself, whether the email is present in the QSM submission, the checkbox state, the audience selected in the quiz settings, the API key, a test on a separate page without a complex builder, and a search for the contact across all possible audiences.

How to fix it: enable the integration in the correct quiz, make the email field required, temporarily use a test audience, verify a submission with the checkbox checked, and then return to the original mode. If the contact only appears with caching disabled, exclude the quiz page from aggressive optimization.

The contact exists, but emails are not being sent

Symptom: the email address is present in Mailchimp, but the participant does not receive campaigns or automations.

Possible causes: the contact is in pending status because of double opt-in, it was previously unsubscribed or cleaned, the Mailchimp automation is not configured, the segment expects a different tag, or the campaign has not launched yet.

What to check: the status in the contact profile, the confirmation email, tags, merge fields, automation conditions, and segment rules in Mailchimp.

How to fix it: confirm the subscription in the test mailbox, verify the segment rule, add the correct tag through QSM mapping, and do not try to manually change a cleaned status if Mailchimp flagged the address because of a bounce.

Score-based tags are not being assigned

Symptom: the contact reaches the audience, but the result-based tag is missing or does not match the expected range.

Possible causes: the score range is configured incorrectly, the quiz calculates points differently than expected, the user did not reach the required score, the tag mapping was saved in the wrong quiz, or an existing subscriber is not being updated because of the selected update existing subscribers mode.

What to check: the actual score in the QSM result, the mapping ranges, whether integration is enabled in the current quiz, the existing subscriber update mode, and test email addresses that have not completed the quiz before.

How to fix it: start with a new email address, use obvious ranges such as low, medium, and high, complete the quiz with predictable answers, and check the tag in Mailchimp. Once the setup is confirmed, make the ranges more detailed if needed.

Email and name were passed, but business or phone is empty

Symptom: the contact was created, but some additional fields are blank.

Possible causes: QSM is not collecting that field, the field is not required, the corresponding merge field was not created in Mailchimp, the tag or field name does not match, or the user left the field blank.

What to check: the contact form in QSM, the stored submission, the Mailchimp merge fields, exact tags such as FNAME for the first name, and your custom fields for business or phone.

How to fix it: add the field in QSM, create the merge field in Mailchimp, make the field required only if it is truly needed, and then repeat the test with a new email address.

The form became unstable after enabling the integration

Symptom: the submit button does not respond, the result page does not open, or the quiz behaves differently across browsers.

Possible causes: a script conflict, JavaScript optimization, page caching, duplicated shortcode, or a conflict with the theme or page builder. WordPress.org support threads for QSM show that users do encounter these kinds of issues with the core plugin, so not every problem should be blamed on the Mailchimp add-on.

What to check: a separate page with only one quiz, script optimization disabled on staging, the browser console, output through a QSM block instead of a complex layout, and behavior without caching for a test user.

How to fix it: isolate the quiz on a simple page, exclude that page from the problematic optimization, remove the second shortcode instance, and only then return to the complex layout. If the problem disappears, there is no need to change the Mailchimp settings.

Safe improvements without editing plugin files

For QSM MailChimp Integration, do not invent PHP hooks or internal classes unless they are confirmed in the documentation. The safe area for improvements is QSM settings, Mailchimp settings, tag structure, clear checkbox wording, and light CSS adjustments to the public form if the theme displays the consent area poorly.

CSS to make the subscription checkbox stand out visually

If the subscription checkbox gets visually lost next to the quiz questions, you can add a small CSS snippet in Appearance > Customize > Additional CSS or in a child theme. The selector below is intentionally generic: check it in the browser inspector and narrow it if needed for your site's actual markup. Do not edit QSM or add-on files.

.qsm-mailchimp-consent,
.qsm-mailchimp-checkbox,
.quiz_section .mlw_qmn_question_comment {
  margin-top: 16px;
  padding: 14px 16px;
  border: 1px solid #d8e2ee;
  border-radius: 8px;
  background: #f7fbff;
}

.qsm-mailchimp-consent label,
.qsm-mailchimp-checkbox label {
  font-weight: 600;
  line-height: 1.45;
}

After adding the CSS, open the quiz page in a private window, check both desktop and mobile widths, submit a test form, and make sure the styles do not interfere with clicking the checkbox. If the selector affects an unrelated block, remove the rule or refine the class based on the actual markup.

Checkbox wording as part of conversion

Technically, you can write anything next to the checkbox, but the best label answers the question "what will I get after subscribing?" For example:

• "Receive an email with your result and practical materials related to this quiz."
• "Subscribe to tips for improving your quiz result."
• "Get an email series matched to the readiness level identified in the quiz."

Do not make broad promises like "receive useful updates" if Mailchimp is actually sending a specific result-based sequence. The more precise the expectation, the fewer complaints and unsubscribes you will get.

A lightweight process for the team

For a site with multiple quizzes, create a simple internal process: which audience is used, how tags are named, where the API key is stored, who verifies double opt-in, and which test emails are used before launch. That is not code, but it is exactly the kind of discipline that prevents most integration errors.

Questions that come up when setting up the Mailchimp integration

Can QSM MailChimp Integration work without an email field in the quiz?

There is very little practical value in that. A Mailchimp contact requires an email address. If the quiz does not collect email, the add-on cannot subscribe the participant to the audience. Add an email contact field in QSM first and confirm that it is saved in the submission.

Do I need to enable double opt-in?

That depends on your subscription policy, traffic source, and user expectations. Double opt-in improves list quality, but it adds a confirmation step. If it is enabled, the contact may remain in pending status until confirmation and may not receive campaigns right away.

Why was an existing subscriber's tag not updated?

Check the update existing subscribers settings, the score mapping ranges, and the actual quiz result. The add-on changelog indicates that handling for existing subscribers and tags has changed across versions, so behavior may depend on your version and the selected settings.

Can quiz answers be passed into Mailchimp?

For QSM MailChimp Integration, official sources emphasize passing email, name, business, phone, score or points, and tags. If you need to send detailed answers to other systems, evaluate Webhooks or Zapier Integration. Do not promise that every answer can be sent to Mailchimp unless that is confirmed by your add-on version and documentation.

What should I do if the Mailchimp audience does not appear in the quiz settings?

Check the API key, the Mailchimp user permissions, the presence of an audience in the account, whether the global add-on settings were saved correctly, and whether there are any connection errors. Then refresh the quiz edit screen. If the list is still empty, test with a new API key and refer to QSM documentation or support.

Does the integration affect site performance?

The main load happens when the quiz is submitted and data is sent to an external service. On a normal page view without submission, the impact should be limited, but actual behavior depends on the theme, scripts, cache, and hosting. For important pages, always test the submission flow after enabling optimization.

Can one Mailchimp audience be used for several quizzes?

Yes, if you use tags and a clear segment structure. That is often more practical than creating a separate audience for every quiz. But if you are dealing with different brands, languages, or legally separate databases, separate audiences may be necessary.

Where is the best place to store the API key?

Keep it only in the integration settings and in the team's secure secrets manager. Do not publish the key in screenshots, articles, tasks, email threads, or theme files. If the key is compromised, revoke it in Mailchimp and save a new one in QSM.

When QSM MailChimp Integration is the right choice

QSM MailChimp Integration is a strong fit when you already use Quiz and Survey Master, already have a Mailchimp audience, and already know what follow-up communication should happen next. The product is especially useful for lead quizzes, educational assessments, survey funnels, and score-based segmentation where email, name, score, and tags need to move from WordPress into Mailchimp without manual export.

Before launch, validate the basic chain on a test audience: the API key is saved, the quiz tab appears, the integration is enabled, the email field is required, the checkbox or automatic mode was chosen intentionally, double opt-in is understood, and tags are assigned according to the expected ranges. Once that is confirmed, you can move the settings to the live quiz and gradually connect real Mailchimp campaigns.

If your scenario is limited to Mailchimp, this add-on is simpler and more direct than a universal automation layer. If the data needs to go to multiple services, a CRM, spreadsheets, or more complex workflows, compare it against Zapier or Webhooks. If the site runs on a different email platform, look at the matching QSM integrations instead.

Once the basic test is complete and you know exactly which data you want to send, you can download the ZIP file and configure the integration on your site. Start on a test page or staging copy, then repeat the control submission on the live quiz page.