Skip to main content

​
Pre-Built Tooling

CategoryDetails
AuthenticationOAuth 2.0 (Authorization Code with refresh tokens)
Two-Way SyncNo
Events SupportedNo
RealtimePolling
Supports Rate LimitingYes
Authentication Scopes SupportedNo granular scopes (full account access)

​
Objects Supported

Alloy Automation supports syncing the following objects from Mailchimp: Based on the Mailchimp Marketing API, typical objects include:
  • Campaigns
  • Lists (Audiences)
  • List Members (Subscribers)
  • Templates
  • Reports
  • Automations

​
Set Up Guide

​
Trial Access

QuestionAnswer
Offers free trial?Yes. Mailchimp offers a free tier with up to 500 subscribers and 1,000 monthly email sends. Sign up for free
Requires paid sandboxNo. The free tier can be used for testing.
Requires partnership to obtain authentication?No. However, apps using OAuth must be registered in Mailchimp’s developer portal.

​
Authentication (OAuth 2.0)

For customers who want to completely whitelabel their OAuth experience, you can provide your own developer keys instead of using Alloy Automation’s.

​
Create your OAuth app (Mailchimp Developer Portal)

  1. Go to Mailchimp Developer Portal (https://mailchimp.com/developer/) and sign in.
  2. Navigate to Registered Apps and click Register An App.
  3. Fill in your application details:
    • App Name: Your application’s name
    • App Description: Brief description of what your app does
    • Company/Organization: Your company name
    • App Website: Your application’s website URL
  4. Add the redirect URI: https://api.runalloy.com/api/strategy/connector/mailchimp/callback
  5. Complete any additional required fields and agree to Mailchimp’s API Use Policy.
  6. Click Create to register your app.
  7. Once created, you’ll receive your Client ID and Client Secret.
  8. Copy these credentials into Alloy Automation.

​
Important Notes

  • Mailchimp uses datacenter-specific API endpoints (e.g., us4.api.mailchimp.com). The datacenter is determined from the OAuth token metadata.
  • OAuth tokens do not expire but can be revoked by users at any time.
  • Mailchimp does not use traditional scopes; OAuth apps get full account access.

​
Use Cases

​
1) Automated subscriber management

Sync customer data from your CRM or e-commerce platform to Mailchimp audiences, automatically adding new customers as subscribers and updating their profile information, tags, and segments based on purchase behavior.

​
2) Campaign performance tracking

Pull campaign reports and analytics from Mailchimp into your data warehouse or business intelligence tools to track email marketing performance, open rates, click-through rates, and ROI alongside other marketing channels.

​
3) Multi-platform newsletter signups

Capture newsletter signups from multiple touchpoints (website, mobile app, in-store kiosks) and centralize them through Alloy Automation to create unified Mailchimp subscribers with proper source attribution.

​
4) Audience segmentation automation

Automatically create and update Mailchimp segments based on user behavior tracked in your application, such as trial users, paying customers, or users who haven’t logged in recently.

​
5) Transactional email compliance

Synchronize unsubscribe requests and email preferences from Mailchimp back to your application’s user database to maintain compliance with email marketing regulations across all communication channels.

​
API Gotchas

  • The Mailchimp API uses datacenter-specific URLs. After OAuth authentication, you must extract the datacenter prefix from the token metadata and construct the correct API base URL (e.g., https://us4.api.mailchimp.com/3.0). Failing to use the correct datacenter will result in authentication errors.
  • List member (subscriber) email addresses are case-sensitive in the API. Mailchimp uses an MD5 hash of the lowercase email address as the subscriber ID. Always lowercase and hash emails when making updates to avoid creating duplicate subscribers.
  • Rate limiting is aggressive and varies by endpoint. Most endpoints allow 10 requests per second, but batch operations have different limits. Always implement exponential backoff and respect the X-RateLimit-* headers in responses.
  • The merge_fields object for subscriber data has a quirky structure. Field names are uppercase and limited to 10 characters (e.g., FNAME, LNAME). Custom merge fields must be created in Mailchimp before they can be populated via the API.
For questions or troubleshooting, contact support@runalloy.com.
⌘I