Connecting Mailchimp to StudioOps — StudioOps Help

If you use Mailchimp to send a newsletter or occasional updates to your customers, you probably know the pain: every new customer you take in StudioOps is a customer who isn't on your Mailchimp list until you remember to add them. StudioOps fixes that — opt-in customers sync automatically.

The connection is one-way: StudioOps → Mailchimp. Unsubscribes the customer makes inside Mailchimp don't flow back into StudioOps (that's on the post-launch roadmap).

You need a Mailchimp account already. If you don't have one, sign up at mailchimp.com first. The free tier handles up to 500 contacts and 1,000 sends per month, which covers a lot of solo studios.

1. Get your Mailchimp API key

In Mailchimp:

Click your profile picture (top right) → Profile.
Extras → API keys.
Create A Key. Give it a label like "StudioOps" so you can recognise it later.
Copy the key Mailchimp shows you. It looks something like abc123def456-us5 — that trailing bit after the dash (us5 here) is your datacenter.

Keep this tab open while you go to StudioOps. Mailchimp shows the full key once; if you lose it, you have to generate a new one.

2. Connect in StudioOps

Go to Settings → Marketing in StudioOps and click into the Mailchimp panel.

Paste your API key into the input field.
Test connection. StudioOps pings Mailchimp to confirm the key works. If it doesn't, you'll see a clear error — usually "the key format isn't right" (check you copied the whole thing including the -us5 part) or "Mailchimp rejected the key" (the key was revoked or never valid).
If the test succeeds, StudioOps shows your audiences in a dropdown. Pick the one customers should sync into. Most studios have one main audience; pick that.
Connect. The key is encrypted at rest before being stored.

You're connected. The green status panel confirms which audience and datacenter you're using, plus the last four characters of your key for sanity.

3. What gets pushed automatically

Three triggers cause an opt-in customer to be pushed to Mailchimp:

Customer creates an account with consent at booking. When the public booking form is open on a Mailchimp-connected studio, customers see a Subscribe to our newsletter checkbox under the booking notes. If they tick it, their record goes to your Mailchimp audience the moment the booking confirms.

You tick the consent box on a new customer in the dashboard. When you add a customer manually from Customers → New, you'll see the same Subscribe checkbox if Mailchimp is connected. Tick it to push immediately on save.

You toggle the consent box on an existing customer. Edit any customer record; ticking the box pushes them to Mailchimp, unticking it sends an unsubscribe request to Mailchimp for that customer.

What gets pushed: email, first name + last name (split from the customer's name field), phone number, and a tag matching your studio's vertical (nail-salon, alterations, hair-salon, etc.) so you can segment by source in Mailchimp.

4. The Sync now button — bringing existing customers across

If you already have a list of customers in StudioOps from before you connected Mailchimp, you can push the opted-in ones across in one click.

In Settings → Marketing, click Sync opted-in customers now.

StudioOps walks the list of customers with marketing_opt_in = true and pushes each one to Mailchimp. You'll see a confirmation like "Pushed 12 customers · 0 failed."

What if a customer hasn't opted in? They won't be in the sync. The Sync-now button only ever pushes opted-in customers — it never overrides consent. To get a pre-existing customer into Mailchimp, edit their record and tick the Subscribe box.

5. The booking-link merge tag

A common pattern: studios use Mailchimp to send "Time for your next visit?" emails and want a one-click booking link in the template.

Your booking URL is at the bottom of the Mailchimp Settings page in StudioOps:

https://studioops.uk/your-slug/book

Drop this URL into any Mailchimp template as a button or text link. It's the same URL for every customer, so no per-customer merge field magic is needed — just paste it in.

For a more personalised CTA, use a Mailchimp merge tag like *|FNAME|* to greet the customer by name (Mailchimp populates it from the FNAME merge field StudioOps already pushes):

Hi |FNAME|, time for your next appointment? Book online here.

6. Errors and how to fix them

If a sync fails, StudioOps records the error and shows it on the Settings → Marketing page in an amber notice. Common errors:

API key revoked. You (or someone with access to your Mailchimp account) deleted the key. Generate a new one in Mailchimp, paste it into StudioOps, click Connect again.
Audience deleted. You deleted the audience that StudioOps was syncing into. Pick a different one from the dropdown by reconnecting.
Rate limit hit. Mailchimp throttles API calls — usually fine for normal studio volumes, but a Sync-now of 5,000+ customers all at once can trip it. StudioOps retries automatically; if it keeps failing, wait an hour and try again.
Customer doesn't have an email. Customers without an email address can't be pushed (Mailchimp keys on email). Add an email to the customer record, save — StudioOps re-syncs.

The error message you see is whatever Mailchimp reported, copied through verbatim so it's easier to search for if you need help.

7. Disconnecting Mailchimp

You can disconnect from Settings → Marketing at any time. New customer sync stops immediately. Customers already in your Mailchimp audience stay where they are — disconnecting StudioOps doesn't delete them from Mailchimp.

If you reconnect later (same audience), the existing subscribers are still there; new opt-ins sync from that point forward. If you reconnect to a different audience, the previously-synced customers stay in the old audience; new opt-ins go to the new one.

8. GDPR and consent

A note on consent: under UK / EU rules, you need to record where each subscriber's consent came from. StudioOps captures the consent moment per customer — what wording they saw, when they ticked the box, on which surface (booking form vs dashboard).

Two practical implications:

The Subscribe-to-newsletter checkbox is opt-in (unticked by default). Customers have to actively tick. We won't pre-tick it for them.
The Sync-now button respects existing consent. It only pushes customers where marketing_opt_in = true. If you bulk-ticked your customers without their consent, you'd be the data controller breaching the rules — Mailchimp's terms put that obligation on the list owner, not on StudioOps.

If you're switching from another tool and your existing customers consented there, the safest move is to email them once asking them to re-confirm — then tick the box in StudioOps for the ones who reply yes.