> For the complete documentation index, see [llms.txt](https://docs.samita.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.samita.io/sa-request-a-quote/integrations/mailchimp.md).

# Mailchimp

Add everyone who requests a quote to a Mailchimp audience, so you can follow up with campaigns.

Connecting Mailchimp means every quote request also becomes a contact you can follow up with, without anyone copying details by hand.

{% hint style="info" %}
Mailchimp is one of the integrations listed under the **FREE** plan, along with Klaviyo and Shopify. See [Plan comparison](/sa-request-a-quote/reference/plan-comparison.md).
{% endhint %}

## Step 1 — Get your API key

In your Mailchimp account, generate an API key. Mailchimp's own guide walks through it: [About API keys](https://mailchimp.com/help/about-api-keys/).

Keep the key somewhere safe while you finish the setup.

{% hint style="info" %}
Mailchimp calls its contact lists audiences. Pick the one you actually send campaigns from — contacts added to an unused audience never get contacted.
{% endhint %}

## Step 2 — Connect it in the app

{% stepper %}
{% step %}

### Open the Integrations tab

In your Shopify admin, open **SA Request a Quote**, select **Advanced settings**, then open the **Integrations** tab.
{% endstep %}

{% step %}

### Select Mailchimp

Under **Third-party integration**, select **Mailchimp** — described in the app as "Automatically create new audiences".

The Mailchimp page opens, with a **Third-party** breadcrumb to take you back to the list.

<figure><img src="https://2993310686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIvNtDAMNVIdy5nl9kiOU%2Fuploads%2Fgit-blob-55e958acb442f0ce92149fef0c5578e7829e5d43%2FScreenshot%202026-09-30%20at%2000-34-01.png?alt=media" alt="The Integrations tab of Advanced settings with Mailchimp outlined in red"><figcaption><p>Pick the service, then open its settings.</p></figcaption></figure>
{% endstep %}

{% step %}

### Turn on Enable

Switch on **Enable**. Nothing is sent to Mailchimp until you do.
{% endstep %}

{% step %}

### Paste your API key

Paste the key from Step 1 into the **API key** field. If you need to go and fetch it, the **Find or generate your API key** help text takes you to Mailchimp's own instructions.
{% endstep %}

{% step %}

### Choose your audience

Open **Select a Mailchimp list to integrate** and pick the audience new contacts should join. Until you choose, it reads "Please select a Mailchimp list".

Create the audience in Mailchimp first. The dropdown can only offer audiences that already exist.
{% endstep %}

{% step %}

### Match your form fields

Select **Merge fields**. This is where you line up the fields on your quote form — the **Contact information** fields such as Email address, First name and Last name — with the matching fields in Mailchimp.

Email address is the one you cannot skip: without it Mailchimp has no contact to create. The rest are optional — match the ones you will actually use.

<figure><img src="https://2993310686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIvNtDAMNVIdy5nl9kiOU%2Fuploads%2Fgit-blob-ce134bdeb1378acba8ca726fb2b3d147d15ac3f0%2FScreenshot%202026-09-29%20at%2016-59-34.png?alt=media" alt="The Mailchimp integration pane in the app with the API key field outlined in red"><figcaption><p>One key connects the app to your Mailchimp audience.</p></figcaption></figure>
{% endstep %}

{% step %}

### Save

Select **Save**. Nothing is stored until you do, and an unsaved page sends nothing.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Once your key is saved the app shows it masked rather than displaying it again. Keep your own copy in case you need it elsewhere.
{% endhint %}

## Step 3 — Test it

Submit a real quote request from your storefront, then check Mailchimp for the new contact. Confirm the fields you matched actually arrived — not just the email address.

{% hint style="warning" %}
Do not skip the test. A connection can look active and still deliver nothing useful if the merge fields are matched wrongly, and you will not notice until you try to use the data.
{% endhint %}

## Is this the right tool?

Good when you already run newsletters in Mailchimp and want quote leads in the same place.

If you do not already use Mailchimp, do not adopt it just for this — [Zapier](/sa-request-a-quote/integrations/zapier.md) connects quote data to almost anything, and [Create a Shopify customer after submit](/sa-request-a-quote/integrations/create-shopify-customer.md) keeps everything inside Shopify.

## If contacts are not arriving

* **Check Enable is still on.** Nothing is sent while it is off.
* **Check the key is still valid.** Regenerating a key in Mailchimp breaks the connection until you paste the new one in.
* **Check you picked the right audience.** Contacts may be arriving somewhere you are not looking.
* **Check the email field is matched in Merge fields.** Without it there is no contact to create.

Still stuck? Email <support@samita.io>.

## Next steps

* [Integrations overview](/sa-request-a-quote/integrations/overview.md) — the other tools you can connect
* [Klaviyo](/sa-request-a-quote/integrations/klaviyo.md) — the other marketing tool on the FREE plan
* [Build a standard form](/sa-request-a-quote/quote-form/build-standard-form.md) — make sure your form collects what you are matching


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.samita.io/sa-request-a-quote/integrations/mailchimp.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
