Mailchimp Connector

Connect your Mailchimp account to Brevo via Tajo for seamless audience migration, campaign data synchronization, and unified marketing automation across both platforms.

Overview

Features

• Audience sync - Migrate and sync Mailchimp audiences with Brevo contact lists
• Campaign data - Sync campaign performance data for unified reporting
• Automation migration - Map Mailchimp automations to Brevo workflows
• Engagement metrics - Sync opens, clicks, and bounce data to Brevo attributes
• Segment mapping - Replicate Mailchimp segments as Brevo lists or segments
• E-commerce data - Sync store, product, and order data from Mailchimp e-commerce
• Tag sync - Map Mailchimp tags to Brevo contact attributes or lists
• Template migration - Export Mailchimp templates for use in Brevo campaigns

Prerequisites

Before you begin, ensure you have:

1. A Mailchimp account (Free, Essentials, Standard, or Premium)
2. A Mailchimp API key or OAuth app
3. A Brevo account with API access
4. A Tajo account

Authentication

API Key Authentication

Generate an API key from Mailchimp Account > Extras > API Keys.

curl https://{dc}.api.mailchimp.com/3.0/ping \
  --user "anystring:{api_key}" \
  -H "Content-Type: application/json"

The {dc} data center prefix is the last part of your API key (e.g., us21).

OAuth 2.0

For multi-account integrations:

# Authorization URL
https://login.mailchimp.com/oauth2/authorize?
  response_type=code&
  client_id={client_id}&
  redirect_uri={redirect_uri}

# Token exchange
curl -X POST https://login.mailchimp.com/oauth2/token \
  -d "grant_type=authorization_code" \
  -d "client_id={client_id}" \
  -d "client_secret={client_secret}" \
  -d "redirect_uri={redirect_uri}" \
  -d "code={auth_code}"

Configuration

Basic Setup

connectors:
  mailchimp:
    enabled: true
    api_key: "${MAILCHIMP_API_KEY}"
    data_center: "us21"

    # Data sync options
    sync:
      audiences: true
      campaigns: true
      automations: true
      ecommerce: true

    # Audience to Brevo list mapping
    audience_mapping:
      "Main Audience": 40
      "Newsletter": 41
      "Customers": 42

Field Mapping

Map Mailchimp merge fields to Brevo contact attributes:

Custom Merge Field Mapping

field_mapping:
  # Standard fields
  email_address: email
  FNAME: FIRSTNAME
  LNAME: LASTNAME
  PHONE: SMS

  # Engagement metrics
  stats.avg_open_rate: AVG_OPEN_RATE
  stats.avg_click_rate: AVG_CLICK_RATE
  member_rating: ENGAGEMENT_SCORE

  # E-commerce fields
  ecommerce_data.total_revenue: TOTAL_REVENUE
  ecommerce_data.number_of_orders: ORDER_COUNT

  # Custom merge fields
  MMERGE5: COMPANY_NAME
  MMERGE6: CUSTOMER_TYPE

API Endpoints

Audiences (Lists)

Campaigns

Automations

E-commerce

Events

Campaign Events

Subscriber Events

E-commerce Events

Code Examples

Initialize Connector

import { TajoClient } from '@tajo/sdk';

const tajo = new TajoClient({
  apiKey: process.env.TAJO_API_KEY,
  brevoApiKey: process.env.BREVO_API_KEY
});

// Connect Mailchimp
await tajo.connectors.connect('mailchimp', {
  apiKey: process.env.MAILCHIMP_API_KEY
});

Migrate Audiences to Brevo

// Full audience migration from Mailchimp to Brevo
await tajo.connectors.sync('mailchimp', {
  type: 'full',
  resources: ['audiences', 'campaigns', 'ecommerce'],
  options: {
    preserveTags: true,
    migrateSegments: true,
    includeUnsubscribed: false
  }
});

// Check migration status
const status = await tajo.connectors.status('mailchimp');
console.log(status);
// {
//   connected: true,
//   lastSync: '2024-01-15T10:30:00Z',
//   contactsMigrated: 52000,
//   campaignsSynced: 245,
//   segmentsMapped: 18
// }

Sync Campaign Engagement Data

// Sync campaign performance to Brevo attributes
await tajo.connectors.sync('mailchimp', {
  type: 'incremental',
  resources: ['campaigns'],
  options: {
    syncEngagement: true,
    updateContactMetrics: true,
    since: '2024-01-01'
  }
});

Rate Limits

Mailchimp Marketing API rate limits:

Troubleshooting

Common Issues

Debug Mode

Enable verbose logging:

connectors:
  mailchimp:
    debug: true
    log_level: verbose
    log_api_calls: true

Test Connection

tajo connectors test mailchimp
# ✓ API connection successful
# ✓ Audiences readable
# ✓ Campaigns readable
# ✓ E-commerce data accessible
# ✓ Webhook configured

Best Practices

1. Use batch operations - Use batch subscribe/unsubscribe for bulk updates
2. Preserve subscriber status - Respect subscription consent during migration
3. Map merge fields first - Create corresponding Brevo attributes before syncing
4. Sync engagement data - Import open/click rates for historical segmentation
5. Handle compliance states - Respect GDPR and permanent deletion states
6. Use incremental sync - Sync only changes since last sync to reduce API usage

Security

• API Key Authentication - Secret key passed as HTTP Basic Auth password
• OAuth 2.0 - Token-based authorization for multi-account access
• TLS encryption - All API communication encrypted via HTTPS
• Webhook verification - Validate webhook source with shared secret
• Data center isolation - Data stored in region-specific data centers

Related Resources

• Mailchimp Marketing API Reference
• Mailchimp API Guides
• Brevo Connector
• ActiveCampaign Connector
• Customer Sync Skill

Open-Source Implementation Map

This section is derived from official or public repository material discovered for the Mailchimp connector. Use it as the engineering companion to the setup guide above: it shows where the API surface lives, what implementation assets exist, and how Tajo should translate them into reliable Brevo sync behavior.

Repository Snapshot

Integration Shape

graph LR
  Source["Mailchimp API / repository"] --> Auth["Auth and scopes"]
  Source --> Objects["Objects, events, and schemas"]
  Auth --> Tajo["Tajo connector runtime"]
  Objects --> Tajo
  Tajo --> Brevo["Brevo contacts, attributes, lists, campaigns"]
  Tajo --> Ops["Backfill, cursor, retries, logs"]

What To Reuse

• mailchimp-client-lib-codegen
• This tool is used to auto-generate and publish both Mailchimp Marketing and Transactional client libraries.
• Quick start
• Generate clients
• Published clients — Internal

Tajo Revamp Checklist

• Keep authentication setup aligned with the vendor docs and the public repository’s current API shape.
• Map primary resources into explicit Tajo sync objects with stable external IDs.
• Prefer cursor-based or updated-at incremental sync where the API exposes it; otherwise document the fallback.
• Treat webhook handlers as idempotent and replay-safe, especially for order, contact, ticket, and campaign events.
• Capture pagination, rate limits, retry headers, and partial-failure behavior in connector smoke tests.
• Keep examples small and runnable against sandbox or test-mode accounts.

Sources

• mailchimp/mailchimp-client-lib-codegen
• Vendor documentation