Mandrill Connector Setup Guide

Mandrill Connector Setup Guide

by bryan_woodard on ‎04-07-2016 04:33 PM - edited on ‎12-18-2018 05:49 PM by (306 Views)

This article describes how to set up the Mandrill by MailChimp connector in your Universal Data Hub account.

In this article:

Table of Contents Placeholder

Connector Actions

Action Name AudienceStream EventStream
Send Transactional Email using a Template

Configure Settings

Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector.

After adding the connector, configure the following settings:

  • Mandrill API Key: This parameter is Required

Action Settings - Parameters and Options

Click Next or go to the Actions tab. This is where you configure connector actions.

This section describes how to set up parameters and options for each action.

Action - Send Transactional Email using a Template

Parameters

Parameter Description
Target Template
  • Required
  • Target Template.
Subaccount
  • Optional
  • Subaccount for this message
  • Must already exist or will fail with an error
Tag List
  • Optional
  • String(s) to tag the message with.
  • Stats are accumulated using tags, though Mandrill only stores the first 100 we see, so this should not be unique or change frequently.
  • Tags should be 50 characters or less.
  • Any tags starting with an underscore are reserved for internal use and will cause errors.
message.subject Message subject line
message.from_email Email address of sender 
message.from_name Name of sender
message.to.email
  • Required
  • Email address of recipient
message.to.name Name of recipient
message.important Values are true or false
message.track_opens
    • Track file opens
  • Values are yes or no
message.track_clicks
  • Track clicks
  • Values are yes or no
message.auto_text Optional
message.auto_html Optional
message.inline_css Optional
message.url_strip_qs Optional
message.preserve_recipients Optional
message.view_content_link Optional
message.bcc_address Optional
message.tracking_domain Optional
message.signing_domain Optional
message.return_path_domain Optional
message.merge Optional
message.merge_language Optional
async Optional
ip_pool Optional
send_at Optional
Google Analytics Domains to Set
  • Optional
  • An array of strings indicating for which any matching URLs will automatically automatically append Google Analytics parameters to their query string.
Google Analytics Campaign to Set
  • Optional
  • Optional string indicating the value to set for the utm_campaign tracking parameter.
  • If not provide, the from address for the email is used instead.
Recipient Header Type
  • Optional
  • The header type to use for the recipient, defaults to "to" if not provided one of the following: to, cc, bcc
  • to.type:
Header Data (Map Value to Key)
  • Optional extra headers to add to the message (most headers are allowed)
Template Content To Set (Map Content to Name)
  • An array of template content to send.
  • Each item in the array should be a struct with two keys:
    • name
      the name of the content block to set the content
    • content
      The actual content to put into the block
Global Merge Vars To Set (Map Content to Name)
  • Optional
  • Global merge variables to use for recipient.
    • name (string)
      The global merge variable"s name. Merge variable names are case-insensitive and may not start with an underscore (_) character
    • content (mixed)
      The content of the global merge variable
Metadata To Set (Map Value to Key)
  • Optional
  • Metadata an associative array of user metadata.
  • Mandrill will store this metadata and make it available for retrieval.
  • In addition, you can select up to 10 metadata fields to index and make searchable using the Mandrill search api.