MailChimp is a cloud-based email marketing solution, that allows designing and sending marketing emails.
Data integration: Skyvia supports importing data to and from MailChimp, exporting MailChimp data to CSV files, replicating MailChimp data to relational databases, and synchronizing MailChimp data with other cloud apps and relational databases.
Backup: Skyvia Backup supports MailChimp backup except for objects with composite primary keys.
Query: Skyvia Query supports MailChimp.
MailChimp-Specific Features and Limitations
Skyvia supports MailChimp merge tags of the ListMembers table, except for cases when different lists have merge tags with the same name but different type, default value, required setting, etc. Skyvia also does not support MailChimp merge tags having double quotation marks in their name. See details of this support below.
Skyvia supports connecting via both MailChimp API 2.0 and 3.0. Please note that some tables and fields, like Automations, ListMemberNotes, ListMemberGoals, and others are available only via MailChimp API 3.0, and some - only via MailChimp API 2.0. By default, Skyvia uses MailChimp API 2.0. You can change this at any time in the connection editor.
When updating MailChimp subscribers (ListMembers) in an import package, you can improve performance of this operation if you specify emails of the subscribers to update. You need to specify them in mapping for the Email field. Note that subscriber emails are not actually updated in this case, this field is just used to find the subscribers for update faster.
Skyvia has the following limitations for MailChimp:
|•||Backup of objects with composite primary key, like InterestGroups, is not supported.|
|•||Synchronization and replication with Incremental Updates enabled are not supported for objects without CreatedDate or LastUpdate fields. Both fields must be present for this functionality. |
When creating a MailChimp connection you simply log in with MailChimp, and OAuth authentication token is stored on the Skyvia server. Your MailChimp account login and password are not stored on the Skyvia server.
To create a MailChimp connection, perform the following steps:
|1.||Open the Connections page by clicking Connections in the menu on the left side of the page.|
|3.||In the opened pane click MailChimp.|
|4.||In the opened New Connection dialog box, specify a connection Name that will be used to identify the connection.|
|5.||Click Log In with MailChimp.|
|6.||In the opened window enter your MailChimp credentials and click the Log In button.|
|7.||Optionally select values for the Merge Fields Behavior and Metadata Cache parameters. The parameters are described below. |
|8.||Optionally switch API Version from Ver2 to Ver3 if you want to use MailChimp API 3.0.|
|9.||Optionally, if you want to use merge tag values as names for MailChimp merge tags instead of merge tag labels, click Advanced and select the Merge Tag As Field Name check box.|
|10.||For MailChimp API Ver3, batch operations are used by default. This significantly improves performance of loading data to the ListMembers object (which stores subscribers). You may optionally turn off batch operations by clicking Advanced and clearing the Use Batch Operations check box. Note that this check box is completely ignored if MailChimp API Ver2 are used. |
Merge Fields Behavior - Determines how to present MailChimp merge tags when working with the ListMembers table. Merge tags are custom fields of the ListMembers table in MailChimp. It's own set of merge tags can be added for list members of each list; however, Skyvia presents all tables, including MailChimp ListMembers, so that all its rows have the same columns.
The following values are available for this setting:
|•||Without Merge Fields - all merge tags are not read from MailChimp and not added as ListMembers table fields.|
|•||Join Common Merge Fields - only merge tags that are defined for all the Lists are added as ListMembers table columns. Other tags are ignored.|
|•||Join All Merge Fields - all the merge tags are joined to other ListMembers table columns (except for the case described below). If a merge tag is not defined for the list, a list member belongs to, NULL value is returned for the corresponding column of this list member.|
If different lists have merge tags with the same name (field label) but different type, default value, required setting, tag, etc., these merge tags are ignored regardless of the Merge Fields Behavior parameter. Merge tags that have the same name for different lists must be the same in order to be available in Skyvia.
However, if only tag values (the values in the Put this tag in your content: column on the List fields and *|MERGE|* tags tab in MailChimp list settings) are different for different lists, and type, default value, and required settings are the same, you can select the Merge Tag As Field Name check box in your connection settings and have access to merge tags that have the same labels but different tags.
Skyvia displays MailChimp merge tags with the Required label in mapping and checks whether they are mapped only if both of the following conditions are met:
|•||The merge tag is present for all MailChimp lists. |
|•||The merge tag has the Required attribute for all MailChimp lists.|
Metadata Cache - Determines how often to update cached metadata for the connection. By default, Skyvia caches metadata of available objects for cloud sources. You can configure how often the cache is refreshed automatically or reset in manually on the Connection Details page of the corresponding connection by clicking the Clear link in the Metadata cache parameter in the Parameters pane. The following values are available for this setting:
|•||Disabled - the metadata cache is not created, and metadata are queried automatically whenever the connection is opened.|
|•||One Hour - the metadata cache expires after one hour since the previous refresh, and it is refreshed after this when the connection is opened.|
|•||One Day - the metadata cache expires after one day since the previous refresh, and it is refreshed after this when the connection is opened.|
|•||One Week - the metadata cache expires after one week since the previous refresh, and it is refreshed after this when the connection is opened.|
|•||One Month - the metadata cache expires after one month since the previous refresh, and it is refreshed after this when the connection is opened.|
|•||Infinite - the cache is never reset automatically. Default value.|