Mailchimp ↔ Shopify integration

Shopify buyers land in the Mailchimp audience with what they bought, and a weekly report sets each campaign against the orders that followed it

The store is in Shopify, the newsletters are in Mailchimp, and the list of buyers moves between them as a file now and then. So a customer who bought a coffee machine yesterday gets a campaign offering the same machine, and nobody can say which campaign actually brought orders. The Mailchimp ↔ Shopify pair adds buyers to the Mailchimp audience with tags based on their orders, keeps those tags current as new orders arrive, and once a week puts the campaigns and the orders that followed them side by side. Below: what exactly moves, which scenarios we cover and which capabilities of both systems we rely on.

Request an integration System page: Mailchimp →System page: Shopify →

What moves between the systems

Shopify → MailchimpA new Shopify order reaches the pair shortly after it is placed, and the buyer is added to or updated in the Mailchimp audience, if they agreed to receive emails.
Shopify → MailchimpFrom the order's line items the subscriber gets tags such as the product category, first or repeat purchase and the date of the last order, so campaigns can be aimed.
Shopify → MailchimpExisting buyers are brought into Mailchimp once at the start, in portions, with the same tags, so the audience begins complete.
Mailchimp ↔ ShopifyOnce a week the pair takes the Mailchimp campaigns and clicks and the Shopify orders from the same buyers in the following days, and puts them side by side in one report for you.

What we connect

First we check how your store and Mailchimp are connected today, so the pair does not duplicate something already running.
We check which parts of the connection your Mailchimp plan allows and confirm the flows only after that.
On the Shopify side the store owner grants the pair read access to orders and customers, and to nothing else.
Together we agree the tags: which product groups matter to your campaigns and how a repeat buyer is defined.
The first transfer runs on a small part of the buyers; after you check the audience in Mailchimp, we move all the others.

Automation scenarios

An offer for what they already bought

Before everyone on the list gets the same campaign, including people who bought the product last week.

After the tag from the order lets you leave them out and send them accessories instead.

Buyers who have not come back

Before nobody knows who bought once and disappeared.

After the date of the last order is in Mailchimp, and a campaign can go only to those who have not ordered for a set time.

“Did that newsletter work?”

Before open rates are known, orders are known, but nobody lines them up.

After the weekly report shows next to each campaign how many of its readers ordered in the following days.

How it works technically

For those who want to check: each point links to the official documentation page it comes from.

Mailchimp's Marketing API gives programmatic access to account data — enough to sync email activity and campaign analytics with an external system, and to manage audiences and campaigns.
Source: mailchimp.com ↗ checked 2026-09-25
Which parts of the connection are usable depends on the account's Mailchimp plan level.
Source: mailchimp.com ↗ checked 2026-09-25
The Marketing API allows up to 10 simultaneous connections; going over that returns a 429 error.
Source: mailchimp.com ↗ checked 2026-09-25
The orders query returns the store's orders with status, customer and line items, and Shopify itself suggests using it to automate fulfillment workflows.
Source: shopify.dev ↗ checked 2026-09-27
An app can subscribe to store events (webhook topics) and receive data about them in near real time, instead of polling the store.
Source: shopify.dev ↗ checked 2026-09-27
Most Shopify rate limits use a leaky bucket; each app has a bucket whose size depends on the API and on the store's plan.
Source: shopify.dev ↗ checked 2026-09-27

Limits

The limits come from both systems. Which parts of the Mailchimp connection are available depends on the account's plan, and Mailchimp accepts up to 10 simultaneous connections, so the first transfer runs in portions. Shopify limits how often an app may request data, and the size of that allowance depends on the store's plan. The pair reads orders and customers in Shopify and does not change them; the weekly report shows orders that followed a campaign, which is not proof that the campaign caused them. Only buyers who agreed to receive emails are added to Mailchimp.

How to start

Three steps from a first message to work on your project.

01
Leave a request
Describe the task in the form — in text or by voice. Budget and timing are optional.
02
We review and estimate
A developer studies the brief, asks about anything unclear and sends an estimate.
03
We start
Once scope and price are agreed, the work begins.

Leave a request

or write to info@coreviaflow.space

Live project We built and run Gemalli — a B2B export platform with producer pages, a CRM and a deal chat. Read the case →

Questions

Does the pair change anything in our Shopify store?

No. It reads orders and customers and writes only to Mailchimp and to the weekly report.

Will people who did not agree to emails get campaigns?

No. Only buyers who agreed to receive emails in your store are added to the Mailchimp audience.

Does the report show exact revenue from each campaign?

It shows the orders placed by a campaign's readers in the days after it. That is a useful signal, but we do not present it as exact revenue caused by the campaign.