We have fixed a bug where the Mandrill server was sending email events data with an invalid TIMESTAMP value with extra digits appended to it. We now consider the first ten digits and discard the extra digits to get the actual TIMESTAMP value.
We have changed the data type of the
location_latitude columns in the
EVENT table from DOUBLE to STRING.
We now support webhooks, which allows us to capture information about email events (“send”, “hard_bounce”, “soft_bounce”, “open”, “click”, “spam”, “unsub”, and “reject”) as they occur.
For existing Mandrill connectors, we will continue to fetch data using the API in addition to using webhooks. For all new Mandrill connectors, we will only fetch email information using webhooks.
We have added the following new tables, which store information about emails and their related events:
||Contains the attribute values of an email (message).|
||Contains information about email events (“send”, “hard_bounce”, “soft_bounce”, “open”, “click”, “spam”, “unsub”, and “reject”) as they occur.|
||Contains the SMTP Response received for the message.|
||Contains tag names that were applied to the message.|
||Contains the attribute values of an email template.|
||Contains the labels that are used in the email template.|
You can now view the list of schemas and tables in your dashboard in read-only mode.
You can now filter your exported data by the specific API keys that you used to send messages.
Mandrill silently revises aggregate clicks and opens metrics in the API results, so we have implemented a 30-day rollback sync to accurately capture this data.
_fivetran_id has replaced
id as the only primary key in the