Configure destination for Mailchimp

Note

This topic contains information about configuring a destination that sends query results to Mailchimp using orchestrations. To configure a destination that sends audiences to Mailchimp using campaigns see this topic .

Mailchimp is an automation platform for email marketing. Use the Mailchimp API to manage audiences in Mailchimp.

Note

This destination uses the Mailchimp Marketing API .

Get details

Review the following details before configuring credentials for Mailchimp and before configuring Amperity to send email lists to Mailchimp.

	Credential settings API key Required Required. The API key for your Mailchimp account.
	Required configuration settings Data center Required The data center ID appends to the API key after the hyphen.

Configure credentials

Configure credentials for Mailchimp before adding a destination.

An individual with access to Mailchimp should use SnapPass to securely share “API key” details with the individual who configures Amperity.

To configure credentials for Mailchimp

	From the Settings page, select the Credentials tab, and then click the Add credential button.
	In the Credentials settings dialog box, do the following: From the Plugin dropdown, select Mailchimp. Assign the credential a name and description that ensures other users of Amperity can recognize when to use this destination.
	The settings that are available for a credential vary by credential type. For the “mailchimp” credential type, configure settings, and then click Save. API key Required Required. The API key for your Mailchimp account.

Add destination

Use a sandbox to configure a destination for Mailchimp. Before promoting your changes, send a test audience, and then verify the results in Mailchimp. After verifying the end-to-end workflow, push the destination from the sandbox to production.

To add a destination for Mailchimp

	Open the Destinations page, and then click the Add destination button. To configure a destination for Mailchimp, do one of the following: Click the row in which Mailchimp is located. Destinations list alphabetically and you can scroll up and down the list. Search for Mailchimp. Start typing “mail”. The list filters to show only matching destinations. Select “Mailchimp”.
	Select the credential for Mailchimp from the Credential dropdown, and then click Continue. Tip Click the “Test connection” link on the “Configure destination” page to verify that Amperity can connect to Mailchimp.
	In the “Destination settings” dialog box, assign the destination a name and description that ensures other users of Amperity can recognize when to use this destination. Configure business user access By default a destination is available to all users who have permission to view personally identifiable information (PII). Enable the Admin only checkbox to restrict access to only users assigned to the Datagrid Operator and Datagrid Administrator policies. Enable the PII setting checkbox to allow limited access to PII for this destination. Use the Restrict PII access policy option to prevent users from viewing data marked as PII anywhere in Amperity and from sending data to downstream workflows.
	Configure the following settings, and then click “Save”. Data center Required The data center ID appends to the API key after the hyphen. List ID (Required at orchestration) The audience ID to which Amperity writes data. This is sometimes referred to as the list ID. List name (Required at orchestration) The name of an email list in Mailchimp managed by Amperity. Tag name (Required at orchestration) A Mailchimp tag to apply to all audience list members. For example: “Added by Amperity”. If this tag does not exist in Mailchimp, it applies to all audience members added by Amperity.
	After configuring this destination users may use: Orchestrations to send query results Orchestrations and campaigns to send audiences Orchestrations and campaigns to send offline events