> For the complete documentation index, see [llms.txt](https://docs.bloop.plus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bloop.plus/referral-program/integrations/mailchimp.md).

# Mailchimp

Connecting Mailchimp lets your referral program work with the audience you already have. Bloop labels each contact as a referrer or referee, fills in their link, code, revenue, and referral count, and marks each milestone as it happens. Set it up under **Integrations → Mailchimp**.

Mailchimp expresses this in three building blocks: **tags** for instant segmentation, **merge fields** for standing details, and **events** for point-in-time triggers.

> **Best practice:** Segment with the **BLOOP Referrer** / **BLOOP Referee** tags, and use **events** for automations that fire at a specific moment. Run the batch sync once after connecting so existing contacts carry tags and fields from day one.

### Connecting Mailchimp

1. In Mailchimp, create an API key.
2. In Bloop, open **Integrations → Mailchimp**, paste the key, choose the audience, and enable the toggle.

Bloop reads the Mailchimp data centre from your key automatically. Live events require the Scale plan; lower plans can still connect and batch-sync.

### Events Bloop sends

| Mailchimp event                  | Fires when                                                                         |
| -------------------------------- | ---------------------------------------------------------------------------------- |
| `BLOOP_Join_Program`             | A customer joins your referral program                                             |
| `BLOOP_Referral_Sharing`         | A referrer shares with a friend                                                    |
| `BLOOP_Successful_Referral`      | A referral converts (carries `BLOOP_Reward_Type`: `DISCOUNT`, `CREDIT`, or `CASH`) |
| `BLOOP_Referee_Receive_Discount` | A referee receives their discount                                                  |

### Tags and merge fields

Bloop tags each contact **BLOOP Referrer** and/or **BLOOP Referee**, and fills in merge fields for referrers: `JOINDATE`, `BLOOPCODE`, `BLOOPLINK`, `REVENUE`, `SUCCESSREF` (successful referral count), and `BLOOPHUB` — a **permanent** link to the [referral hub](/referral-program/referral-hub.md), safe to use in a journey email that sends long after a referral (unlike Bloop's own 2-hour magic link).

### Three high-value plays

* **A referrer-only campaign.** Segment on the **BLOOP Referrer** tag — never send a "join the program" invite to someone already in it.
* **A top-referrer VIP segment.** Segment on `SUCCESSREF` ≥ your threshold; it stays current as merge fields update.
* **An instant thank-you automation.** Start it from the `BLOOP_Successful_Referral` **event**, using `BLOOP_Reward_Type` to match the wording.

### A worked example

Sync first so tags and merge fields exist for everyone. Build a segment (**BLOOP Referrer** tag *and* `SUCCESSREF` ≥ 3) for a standing VIP campaign personalised with `BLOOPLINK`, paired with a *separate* automation off the `BLOOP_Successful_Referral` **event** for an instant thank-you on each new conversion. The segment handles "who is a VIP today"; the event handles "a referral just landed."

### Syncing your audience

Run the batch sync once, right after connecting — otherwise only customers who hit a milestone after connection get tagged, and a "BLOOP Referrer" segment misses your existing base. A referrer-and-referee contact is merged into one entry. Bloop reports batch progress (`pending` → `finished`, or `errored` if something failed — usually a merge-field type conflict in Mailchimp).

### Common mistakes to avoid

* **Triggering an automation off a tag instead of an event.** A tag is a standing state, not a moment — use the *event* to fire at the right instant.
* **Segmenting off an event instead of a tag or merge field.** Events only capture recent activity — build durable segments from tags and merge fields.
* **Skipping the initial batch sync.** Without it, existing referrers carry no tags for weeks.

### Related

* [Klaviyo integration](/referral-program/integrations/klaviyo.md) — the equivalent integration for Klaviyo.
* [Referral analytics](/referral-program/analytics/analytics.md) — the in-app view of the same performance.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bloop.plus/referral-program/integrations/mailchimp.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.