Good to know: Object source
The Mandrill Source is an object source. This means that it sends information (traits) about a thing that exists and persists over time, such as a person or company, and which can be updated over time. Data from this source can only be exported directly to a warehouse, but it can then be used for further analysis. Learn more about cloud sources.
This source is supported in US data processing regions.
The Mandrill source is only supported in workspaces configured to process data in the US region. Workspaces configured with data processing regions outside of the US cannot connect to this source. For more information, see Regional Segment.
Mandrill is a transactional email API for MailChimp users.
Take your company’s email analysis to the next level by adding Mandrill as a Source to Segment. Segment automatically collects email events like
Opened and load them into your data warehouse.
From your workspace’s
Give the source a nickname and a schema name. The nickname is a label used in the Segment interface, and the schema name is the namespace you query against in your warehouse. Both can be whatever you like, but we recommend sticking to something that reflects the source itself, like
Mandrillfor nickname and
mandrill_prodfor the schema name.
Note: You can add more than one instance if you have multiple Mandrill accounts. That’s why Segment allows you to customize the source’s nickname and schema name!
- Copy the auto-generated Webhook URL.
In Mandrill, go to Settings > Webhook and paste the URL in the Event Notification settings pane.
Once you enable the webhook, you’re good to go! Segment automatically creates your collections based on which triggers you select. If any seem unnecessary for your analysis, feel free to leave them unchecked.
- Finally, back in the Segment UI, press Next and then Finish to wrap up the set up flow.
The Mandrill source is comprised only of a streaming component which listens in real time for inbound webhooks from Mandrill’s Webhooks and batches the events to be uploaded on your next warehouse flush. These events are only ever appended to your warehouse. Since Mandrill is strictly used for transactional emails triggered directly by API calls, there are no “dimensional” concepts in their data model that would require any additional components.
Collections are the groupings of resources we pull from your source. In your warehouse, each collection gets its own table.
|Sent||Event||Message has been sent successfully|
|Bounced||Event||Message has hard bounced|
|Opened||Event||Recipient opened a message; will only occur when open tracking is enabled.|
|Marked As Spam||Event||Recipient marked a message as spam|
|Rejected||Event||Message was rejected|
|Delayed||Event||Message has been sent, but the receiving server has indicated mail is being delivered too quickly and Mandrill should slow down sending temporarily|
|Soft-Bounced||Event||Message has soft bounced|
|Clicked||Event||Recipient clicked a link in a message; will only occur when click tracking is enabled|
|Recipient Unsubscribes||Event||Recipient unsubscribed|
This page was last modified: 08 Mar 2022
Questions? Problems? Need more info? Contact Segment Support for assistance!