Hevo can replicate your Mailchimp data to your data warehouse using Mailchimp’s API.

For creating Pipelines using this Source, Hevo provides you a fully managed BigQuery data warehouse as a possible Destination. This option remains available till the time you set up your first BigQuery Destination irrespective of any other Destinations that you may have. With the managed warehouse, you are only charged the cost that Hevo incurs for your project in Google BigQuery. The invoice is generated at the end of each month and payment is recovered as per the payment instrument you have set up. You can now create your Pipeline and directly start analyzing your Source data. Read Hevo Managed Google BigQuery.

Configuring Mailchimp as a Source

Perform the following steps to configure Mailchimp as the Source in your Pipeline:

  1. Click PIPELINES in the Asset Palette.

  2. Click + CREATE in the Pipelines List View.

  3. In the Select Source Type page, select Mailchimp.

  4. In the Configure your Mailchimp account page, click + ADD MAILCHIMP ACCOUNT.

  5. Give Hevo access to your account by entering your Mailchimp credentials.

  6. In the Configure your Mailchimp Source page, specify the following:


    • Pipeline Name: A unique name for the Pipeline, not exceeding 255 characters.
  7. Click TEST & CONTINUE.

  8. Proceed to configuring the data ingestion and setting up the Destination.

Data Replication

Default Pipeline Frequency Minimum Pipeline Frequency Maximum Pipeline Frequency Custom Frequency Range (Hrs)
1 Hr 1 Hr 48 Hrs 1-48

Note: The custom frequency must be set in hours, as an integer value. For example, 1, 2, 3 but not 1.5 or 1.75.

  • Historical Data: From Release 1.82, Hevo ingests your historical data using the Recent Data First approach. This enables you to have quicker access to your historical data.

    • For Pipelines created before Release 1.82: By default, Hevo replicates all the historical data present in your Mailchimp account.

    • For Pipelines created after Release 1.82: You can select the historical sync duration at the time of creating a Pipeline. Default duration: 3 Months.

  • Incremental Data: Once the historical load is complete, all new and updated records for the List Members and custom objects are synchronized with your Destination as per the ingestion frequency. For the remaining objects, Hevo re-ingests all the Events.

Note: From Release 1.85, Hevo ingests only new and updated data for Full Load objects to optimize the quota consumption. This feature is currently available on request only. You need to contact Hevo Support to enable it for your team.

Schema and Primary Keys

Hevo uses the following schema to upload the records in the Destination:

Data Model

The following is the list of tables (objects) that are created at the Destination when you run the Pipeline:

Note: All objects other than List Members, Member Tags, and Tags are Full Load objects.

Object Description
Automations The automations table contains information of all Automations belonging to your Mailchimp account.
In Mailchimp, automations allow you to build a series of emails that are sent to subscribers when triggered by a specific date, activity, or event.
Information about Emails and Unsubscribers associated with each automation is also ingested by Hevo.
Automation Emails An automation email is an email that is part of an automation.
An automation can consist of multiple emails.
The automation_emails table contains details of each automation email such as create time, update time, recipients, number of opens, number of clicks and so on.
Automation Removed Subscribers The automation_removed_subscribers table contains details about members that have unsubscribed or have been removed from an Automation recipient list.
Campaigns Campaigns in Mailchimp allow you to design email templates that can be sent to a mailing list.
Hevo ingests data of all campaigns associated with your Mailchimp account and stores them in the campaigns table.
Subscriber activity in a specific campaign as well as unsubscriber reports are also extracted for each campaign.
Email Activity Reports Member’s subscriber activity in a specific campaign.
The email_activity_reports contains detailed information regarding any member activity.
Each activity is also accompanied by a timestamp.
Lists Lists also known as your audience in Mailchimp are used to store and manage your contacts.
The lists table contains detailed statistics for each list present in your Mailchimp account.
List Abuse Reports Reports of members from a particular list that have marked an email as spam accompanied by a timestamp of the action are stored in the list_abuse_reports table.
List Members The members table contains detailed information about all members belong to your mailing lists.
List Segments Segments are a section of a list that includes only those subscribers who share specific common field information.
Information regarding segments of a list are stored in the segments table.
A tag that is created and assigned to members is also considered a segment.
A segment with the type static indicates a tag.
Member Tags Contains details of all the tags that are associated with a contact in your Mailchimp account.
Reports Mailchimp’s campaign and automation reports analyze clicks, opens, subscribers’ social activity, e-commerce data, and more.
A report is generated for each campaign that is part of your account and stored in the reports table.
Reports are updated each time a campaign is sent.
Segment Members The segment_members table contains details about members belonging to various segments.
Tags Contains the details of all the tags used to organize your contacts into multiple categories.
Unsubscribes The unsubscriber_reports table contains information about list members who unsubscribed from a specific campaign.



Revision History

Refer to the following table for the list of key updates made to this page:

Date Release Description of Change
Sep-07-2022 1.97 Updated section, Data Model to include information about new objects.
Aug-24-2022 NA Updated sections, Data Replication and Data Model to reorganize content for better understanding and coherence.
Jul-27-2022 NA Updated Note in section, Data Replication.
Mar-21-2022 1.85 Added a note in section, Data Replication to inform about optimized quota consumption for Full Load objects.
Feb-21-2022 1.82 Updated section, Data Replication to add information about reverse historical load and configurable historical sync duration.
Oct-25-2021 NA Added the Pipeline frequency information in the Data Replication section.
Last updated on 08 Sep 2022

Tell us what went wrong