
Morning
Overnight orders are already in Mailchimp with their products. The manager checks the campaign revenue from the weekend without exporting anything.
Data sync
A cookware brand's catalogue, customers, subscribers, carts, orders and promo codes flow into Mailchimp through a queue on the Magento cron, typically under a minute after the change. Unsubscribes come back the other way by webhook. The result is an audience where every contact carries their real history, and a product catalogue Mailchimp can recommend from.

Why it matters
Customers and newsletter subscribers land in the right audience with their Magento data, purchase statistics and score. Nobody uploads a CSV again.
Orders sync as they are placed and update on every status change, refund and shipment, so Mailchimp reports what each campaign and journey actually sold.
Simple, configurable, grouped, bundle, virtual and downloadable products with categories and gallery images, plus cart price rules and coupon codes for use in campaigns.
An unsubscribe in Mailchimp is applied in Magento by webhook and the other way round, and a customer deleted in Magento is removed from Mailchimp at the highest priority.
How it works
The setup wizard connects the store to Mailchimp and maps each store view to an audience. Ecommerce data sync is switched on.
Changes to customers, subscribers, orders, products, carts and promo rules are queued and sent by two cron lanes: a real-time lane for what just happened and a backfill lane for history.
Contacts get their merge fields, tags and score, orders attach to contacts, products populate the store catalogue, and behavioural events reach Mailchimp's Customer Journeys.
Unsubscribes and profile changes made in Mailchimp arrive by webhook and are written back to Magento. Every record shows its sync status in the customer, product and order grids, with a Push Now button when you want it sent again.
Ways merchants use it
Any Magento store that wants its Mailchimp audience to reflect the store as it is today, not as it was at the last export.

Overnight orders are already in Mailchimp with their products. The manager checks the campaign revenue from the weekend without exporting anything.

Twelve new products go live in Magento. By the afternoon they are in the Mailchimp catalogue and in the recommendation block of the next email.

A customer unsubscribes from a campaign. Magento knows within the next sync, and the checkout opt-in stays unticked for her.
What you need
Also in Marketing Automation
Questions
Products of every type with categories and images, customers with purchase statistics and score, newsletter subscribers with merge fields, carts, orders with their status changes, promo rules and coupons, and behavioural events, per store view.
Near real time: typically under a minute from the change in Magento to the update in Mailchimp, through a queue on the Magento cron.
Yes, both ways. An unsubscribe in Mailchimp arrives by webhook and is applied in Magento; an opt-out in Magento is sent to Mailchimp.
Yes. Resync a store from the admin or the CLI, choose how far back historical orders go, and push a single record again from its Mailchimp Sync tab.
A customer or subscriber deleted in Magento is removed from Mailchimp at the highest queue priority. Credentials never reach logs, and customer data in logs is masked on display by default.
The setup wizard takes a few minutes. If something in your setup is unusual, the Marketing Automation team at ebizmarts is one email away.