Mailchimp

ExpandedToggleIcon        Connection Dialog

To connect to Mailchimp, you need to perform the following steps:

1.Select the required API Version.
2.Click Sign In.
3.In the opened Web Login dialog sign in to your Mailchimp account.

note Note

Different API versions provide access to somewhat different sets of objects and fields. Some features can be accessed only via API v3, and some - only via API v2.

 

OAuth Interactive authentication

 

OAuth Interactive authentication uses the authorization code flow with user sign-in in a browser window. This method allows obtaining an OAuth access token without requiring a security token or manually entering a client ID and client secret.

To connect with the OAuth Interactive authentication, perform the following steps:

1.In Authentication Type, select OAuthInteractive.
2.Click Test Connection.
3.In the browser window, sign in to Mailchimp with your username and password.

After successful authorization, the access token and related OAuth parameters are stored automatically, and you will be able to connect.

 

Additionally, you may configure Advanced connection options for more fine connection tuning.

 

ExpandedToggleIcon        Advanced Connection Options

The following table describes the options that you can include in the Connection String using the Advanced Connection Editor dialog box:

 

Option

Description

API Key

Specifies a key that grants access to your Mailchimp account.

Authentication Type

Specifies the authentication method to use when connecting to Mailchimp.

Client Id

Specifies the OAuth 2.0 client ID that you can obtain when you register a custom OAuth app for Mailchimp.

Client Secret

Specifies the OAuth 2.0 client secret that you can obtain when you register a custom OAuth app for Mailchimp.

Connection Lifetime

Specifies the maximum lifetime (in seconds) of a connection. When a connection is returned to the pool, its creation time is compared with the current time, and the connection is destroyed if that time span exceeds the value specified by Connection Lifetime. The default value is 0 (connection always returns to pool).

Connection Timeout

Specifies the length of time (in seconds) to wait for a connection to the server before terminating the attempt and generating an error. The default value is 60.

Default Command Timeout

Specifies the time in seconds to wait while trying to execute a command before terminating the attempt and generating an error.

Failover Retries

Specifies the number of retry attempts to re-run a command in case when the command failed because of an exception, that indicates that the reason of the failure may be temporary.

Initialization Command

Specifies a data source-specific command to execute immediately after the connection is established.

Local SQL Engine

Determines whether to enable local SQL processing (enabled by default). Local SQL processing allows performing complex SELECT statements that cannot be directly compiled to Mailchimp API calls. In this case ll the data from the mentioned cloud objects is queried to the local cache, and then the query is performed against the cache.

If local SQL processing is disabled, only simple SELECT statements that can be directly translated into Mailchimp API calls can be used. More complex SELECT statements will fail.

Max Pool Size

Specifies the maximum number of connections allowed in the pool. Setting the Max Pool Size value in the connection string can affect performance. The default value is 100.

Merge Fields Detection 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. Merge Fields Behavior parameter

The following values are available for this setting:

None - all merge tags are not read from Mailchimp and not added as ListMembers table fields.
JoinCommon - only merge tags that are defined for all the Lists are added as ListMembers table columns. Other tags are ignored. This is the default value.
JoinAll - 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 but different type, default value, required setting, 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.

 

note Note

Reading merge tag information takes some time. If you don't to use merge tags, set this parameter to None for best performance.

Min Pool Size

Specifies the minimum number of connections allowed in the pool. The default value is 0.

NormalizeDbNames

Determines whether database object names are normalized when retrieved from the database.

Persist Security Info

Indicates if security-sensitive information, such as the password, is not returned as part of the connection if the connection is open or has ever been in an open state.

Pooling

Specifies whether, by default, the connection is drawn from the appropriate pool or is created and added to the appropriate pool.

Proxy Host

Specifies the host name or IP address of the proxy server.

Proxy Password

Specifies the password for the proxy server account.

Proxy Port

Specifies the port number of the proxy server. The default value is 3128.

Proxy User

Specifies the proxy server account name.

Readonly

Indicates whether the connection is read-only (allows only SELECT statements).

Run Once Command

Specifies a command to execute immediately after establishing the connection. Unlike Initialization Command, it is not executed for connections obtained from the connection pool.

Token Server

Is not used for Mailchimp.

Use Merge Tag As Field Name

Determines whether to use merge tag values as custom field names or use label values instead.

UTC Dates

Converts dates to UTC format during import if set to True, and treats the date values entered by the user (in SELECT statements, etc.) as UTC dates when sending them to the data source.