Send data to Mailchimp¶
Mailchimp is a cloud-based marketing automation platform and an email marketing service that provides an API for integrating with third-party systems and a web UI for managing email contacts, templates, and lists.
Note
This destination uses the Mailchimp REST API .
This topic describes the steps that are required to send audience lists to Mailchimp from Amperity:
Get details¶
Mailchimp requires the following configuration details:
The Mailchimp API key. |
|
The data center ID. This is appended to the API key after the hyphen. |
|
The audience ID to which Amperity will write. (This is sometimes referred to as the list ID.) |
|
The audience name. |
|
A Mailchimp tag to be applied to all audience list members. For example: “Added by Amperity”. If this tag does not exist in Mailchimp, it will be associated to all audience members added by Amperity. Important The tag name is configured as part of the orchestration from the Tag Name field. |
|
The list of audience fields and merge tags for the audience to which you want to send query results. |
|
A query that outputs the fields that must be mapped to the Mailchimp audience. |
How do I find Mailchimp account and audience information?
You can find all of this information after you log into Mailchimp.
The Mailchimp API key is associated with your account username. Click your username, then Account, then Extras, and then API Keys. Copy the API key, including after the hyphen.
The datacenter ID is the information after the hyphen in the API key.
There can be many audiences in Mailchimp. For each audience to which you want to send query results, click Audiences, then Manage Audience, then Settings. (A new page opens.)
Click Settings, and then Audience names and defaults. The audience ID is on the right side and the audience name is on the left side.
The audience fields and merge tags are available from the same list as audience names and defaults. Click Settings and then Audience fields and |MERGE| tags. You will need to define the data template in Amperity to match those fields, along with mapping a field in Amperity that can map “subscribed” or “unsubscribed” values to a field that can be mapped to Mailchimp.
Add destination¶
Configure Amperity to send audience lists directly to Mailchimp.
To add a destination
Open the Destinations tab to configure a destination for Mailchimp. Click the Add Destination button to open the Destination dialog box. Enter a name for the destination and provide a description. For example: “Mailchimp” and “This sends audience lists to Mailchimp”. From the Plugin drop-down, start typing “mail” to filter the list, and then select Mailchimp. |
|||||
Credentials allow Amperity to connect to Mailchimp. The credential type is set automatically. You may use an existing credential or you may add a new one. Select an existing credential from the Credential drop-down. – or – Select Create a new credential from the Credential drop-down. This opens the Credential dialog box. Enter the name for the credential, and then add a description. Mailchimp has the following settings:
When finished, click Save. |
|||||
Each destination has settings that define how Amperity will deliver data to Mailchimp. These settings are listed under the Settings section of the Destination dialog box. The following settings are specific to Mailchimp:
|
|||||
Business users are assigned to the Amp360 User and/or AmpIQ User policies. (Amp360 User allows access to queries and orchestrations and AmpIQ User allows access to segments and campaigns.) A business user cannot select a destination that is not visible to them. Business users – including users assigned to the DataGrid Operator policy – may have restricted access to PII. What is restricted access to PII? Restricted PII access is enabled when the Restrict PII access policy option that prevents users who are assigned to that option from viewing data that is marked as PII anywhere in Amperity and from sending that data to any downstream workflow. You can make this destination visible to orchestrations and allow users with restricted access to PII to use this destination by enabling one (or both) of the following options: Note To allow business users to use this destination with campaigns, you must enable the Available to campaigns option within the data template. This allows users to send campaign results from Amperity to Mailchimp. The other two settings may be configured within the data template instead of the destination. |
|||||
Review all settings, and then click Save. Important You must configure a data template for this destination before you can send data to Mailchimp. |
Add data template¶
A data template defines how columns in Amperity data structures are sent to downstream workflows. A data template is part of the configuration for sending query and segment results from Amperity to an external location.
To add a data template
From the Destinations tab, open the menu for a destination that is configured for Mailchimp, and then select Add data template. This opens the Add Data Template dialog box. Enter the name of the data template and a description. For example: “Mailchimp” and “Send audience lists to Mailchimp.”. |
|
Verify business user access to queries and orchestrations and access to segments and campaigns. A business user may also have restricted access to PII, which prevents them from viewing and sending customer profile data. If business user access was not configured as part of the destination, you may configure access from the data template. |
|
Verify all configuration settings. Note When the settings required by Mailchimp were are not configured as part of the destination, you must configure them as part of the data template before making this destination available to campaigns. |
|
Review all settings, and then click Save. After you have saved the data template, and depending on how you configured it, business users can send query results to Mailchimp. |