Hi all, I am finally getting around to installing the Mailchimp Extended Plugin by Zeroqode on my app. I have a simple use case. When new users create an account, I just want add them to my Mailchimp audience (with their consent) for newsletters and other sales announcements. I will also give my users the ability to unsubscribe from the newsletter in my app’s account preferences. I will not be calling campaigns or anything else – that will be handled by Mailchimp.
For the Plugin’s Subscribe Member API call, I was able to find my audience/list ID in Mailchimp, so that problem is solved. But why is there is a field for calling the data center, and does anyone know where to find my data center? I don’t see that field being required in the Mailchimp documentation, but it is a required field in the plugin. Can I just leave it blank?
Also, someone here brought up that we may need an additional field for indicating subscriber consent, but this does not seem to be part of the plugin>subscribe member. Is it necessary to set up a work around for that or an additional API Connector?
Thanks for reaching out and sharing the details of your setup!
Regarding the Data Center field in the plugin:
You’re absolutely right—it’s not always clearly called out in Mailchimp’s general API docs, but it is required when you’re making API calls. Essentially, the data center is part of your Mailchimp API key and the URL you use in your Mailchimp dashboard. For example, if your API key ends in us7, or you see something like https://us7.admin.mailchimp.com in your dashboard URL, then your data centre is us7.
You’ll need to enter this value (just the usX portion, e.g. us7) in the plugin’s Data Center field so that it builds the correct API endpoint.
Here are some helpful links that explain how to find and why the data center is required:
As for subscriber consent:
There isn’t a dedicated “consent flag” field in the Mailchimp API itself for the Subscribe Member endpoint. Instead, you should ensure in your app that the user checks a box (or gives some form of opt‑in) before you call the plugin’s Subscribe Member API action. You can record that consent in your database for compliance, but you don’t have to send it to Mailchimp directly (via this plugin).
So you don’t need a separate API Connector just to capture consent unless you want more customised behaviour beyond what the plugin provides.
Just checking in to see if you had a chance to review our explanation about the Mailchimp data center and subscriber consent setup.
Let us know if everything is clear or if you’d like help testing the API call — happy to assist!
Really glad to hear everything is working now — happy we could help!
If you have a moment, we’d truly appreciate a quick review. It helps other Bubble users discover reliable tools and supports our team a lot. You can leave feedback here:
Zeroqode Reviews: 
Check if a third-party plugin exists:
Set up the Claude API manually via Bubble’s API Connector. This works fine as long as you follow Anthropic’s API documentation.