> ## Documentation Index
> Fetch the complete documentation index at: https://conductorone-docs-mcp-bridge-private-server.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up a Mailchimp connector

> C1 provides identity governance for Mailchimp. Integrate your Mailchimp account with C1 for unified visibility and governance over who owns the connection.

C1 provides identity governance for Mailchimp. Integrate your Mailchimp account
with C1 for unified visibility and governance over the account behind the
connection.

## Capabilities

| Resource | Sync                                                          | Provision |
| -------- | ------------------------------------------------------------- | --------- |
| Users    | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |           |

The connector syncs the authenticated Mailchimp account as a single user
identity — the account owner — carrying their account role (for example
**owner**), Mailchimp username, and contact email.

<Note>
  Mailchimp's Marketing API does not expose an endpoint for listing the people
  (team seats) who can sign in to a Mailchimp account — that surface is available
  only in the Mailchimp web app. This connector therefore syncs a single identity
  representing the authenticated account itself, populated from the Mailchimp API
  root (`GET /3.0/`). It is identities-only: it does not sync entitlements or
  grants, and it does not sync your audience subscribers (those are marketing
  contacts, not account users).
</Note>

## Gather Mailchimp credentials

<Warning>
  You need a Mailchimp **Marketing API key**. It grants API access as your
  account, so treat it as a secret. The key embeds your account's data center as
  a suffix after a hyphen (for example `...-us19`).
</Warning>

<Steps>
  <Step>
    Sign in to Mailchimp as the owner of the account you want to sync.
  </Step>

  <Step>
    Open **Account & billing**, then go to **Extras → API keys**.
  </Step>

  <Step>
    Click **Create A Key**, give it a descriptive name, and copy the generated
    key — you will not be able to see it again.
  </Step>

  <Step>
    Note your data center. It is the part of the API key that follows the
    hyphen (for example, in `0123...cdef-us19` the data center is `us19`). It
    also appears at the start of your Mailchimp app URL
    (`https://us19.admin.mailchimp.com/`).
  </Step>
</Steps>

## Configure the Mailchimp connector

<Tabs>
  <Tab title="Cloud-hosted">
    Follow these instructions to use a built-in, no-code connector hosted by C1.

    <Steps>
      <Step>
        In C1, navigate to **Integrations** > **Connectors** and click **Add connector**.
      </Step>

      <Step>
        Search for **Mailchimp** and click **Add**.
      </Step>

      <Step>
        Choose how to set up the new Mailchimp connector.
      </Step>

      <Step>
        Set the owner for this connector.
      </Step>

      <Step>
        Click **Next**.
      </Step>

      <Step>
        Find the **Settings** area of the page and click **Edit**.
      </Step>

      <Step>
        Enter the Mailchimp credentials:

        * **API key**: The Marketing API key you created.
        * **Data center**: The data center prefix from the key (for example `us19`).
      </Step>

      <Step>
        Click **Save**.
      </Step>

      <Step>
        The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing.
      </Step>
    </Steps>

    **Done.** Your Mailchimp connector is now pulling access data into C1.
  </Tab>

  <Tab title="Self-hosted">
    Follow these instructions to run the Mailchimp connector in your own
    environment.

    <Steps>
      <Step>
        Create a secret for the Mailchimp Marketing API key.
      </Step>

      <Step>
        Configure the connector environment variables:

        * **BATON\_MAILCHIMP\_API\_KEY**: The Mailchimp Marketing API key (store this as a secret).
        * **BATON\_MAILCHIMP\_DC**: The data center prefix from the key (for example `us19`).
      </Step>

      <Step>
        Deploy the connector using your standard self-hosted connector process.
      </Step>
    </Steps>

    **Done.** Your Mailchimp connector is now pulling access data into C1.
  </Tab>
</Tabs>