Reference

Configuration settings

A map of every settings group in Intuit Mailchimp: find any option at a glance.

Open Marketing → Intuit Mailchimp → Configuration to reach everything on this page. The same section is also available under Stores → Configuration, in the Intuit Mailchimp tab, if you prefer Magento’s standard configuration tree. Switch the store-view scope switcher first: many settings are per store view, so what you save applies only to the view you have selected.

Connection

The master on/off switch for the extension, plus the per-store-view link to your Mailchimp account.

Enabled: turns the entire extension on or off for the current scope.

Connect your account →

Pixel Tracking

Turn the Mailchimp Pixel on or off for this storefront.

Activate Pixel on this Store: enables the Pixel for this store view; Mailchimp confirms before the switch flips.
Auto-Track Page Views: the Pixel tracks page views automatically whenever it is active; this setting records your preference and does not change what the Pixel tracks.
Hash Email for Identify: visitor identification always uses a SHA-256 hashed email when the browser supports it; this setting records your preference and does not change how identification works.

The Mailchimp Pixel & behavioral events →

Ecommerce Sync

Controls which store data flows to Mailchimp for revenue tracking, product recommendations, and automations.

Enable Ecommerce Sync: master switch for all ecommerce data sync. When disabled, products, orders, carts, and promo codes stop syncing; gallery image updates already queued are allowed to finish.
Sync Abandoned Carts: queues active carts in real time at the highest priority and sends them within about a minute, so Mailchimp can send abandoned cart recovery emails.
Sync Products: syncs your full catalog (name, price, URL, main image) for product recommendations in campaigns. Every product type syncs, including Adobe Commerce gift cards and product types added by third-party extensions. Every product assigned to the store’s website is queued; products older than the warm sync window wait until Process Historical Data is enabled.
Sync Orders: new orders sync as they are placed and update on every status change, powering revenue attribution, lifetime value, and post-purchase automations. The date range and status selection below control the historical import and revenue calculations.
Sync Promo Rules & Codes: syncs cart price rules and their coupon codes for use in campaigns. The initial import covers active rules; after that, every rule save keeps Mailchimp current, marking deactivated rules as disabled.
Order Sync Range: the date window for the historical order import. The same dates also determine which customers are included in the initial import; orders older than the warm sync window import while Process Historical Data is enabled.
Order Statuses to Sync: selects which order states are included in the historical import and in revenue and lifetime value calculations (default: processing, complete, closed). Orders placed after go-live sync on every status change regardless of this selection.
Process Historical Data: processes cold-tier data (historical orders, customers, and products older than the warm sync window) once all newer data has fully synced. The system re-evaluates this switch after each Go Live or Re-sync; enabling it may add contacts to your Mailchimp audience, so it can affect your Mailchimp plan.
Sync Product Images: syncs additional gallery images beyond the main product image (one extra API call per additional gallery image). The main product image always syncs with the product.

How syncing works →

Contact Sync

Controls how customers and newsletter subscribers are added to your Mailchimp audience.

Sync Customers: syncs customer profiles as audience members with merge fields and purchase data. It covers customers who have placed at least one order, so your contact count stays proportional to your active buyers; shoppers who only left a cart reach your audience through Sync Abandoned Carts in Ecommerce Sync.
Sync Last Order Merge Fields: adds four optional merge fields describing the customer’s most recent order: LASTSKU, LASTAMT (the order total, net of refunds, in your store’s base currency), LASTID, and LASTCAT. Off by default, since Mailchimp caps the number of merge fields per audience.
Sync Newsletter Subscribers: syncs Magento newsletter subscribers as subscribed audience contacts.
Double Opt-In: sends a confirmation email to new subscribers before adding them to your audience.
Default Subscription Status for Synced Customers: sets whether synced customers land as Subscribed or Non-subscribed (non-subscribed is recommended for compliance).
Sync New Non-Subscribed Customers: governs the customer-profile sync. When on, new customers sync regardless of newsletter status; when off, new non-subscribed customers are skipped by the profile sync, while order and cart sync can still add a shopper’s contact when those features are on.
Data fields: maps Magento customer attributes to Mailchimp merge fields (store-view scope only).
Rebuild merge fields: a button that rebuilds the merge fields in your Mailchimp audience; shown when Sync Customers is on.

How syncing works → · Grow your audience →

Adds a newsletter checkbox to specific storefront pages so shoppers can opt in during their natural flow. Both surfaces are off by default; their settings appear once Sync Newsletter Subscribers is enabled.

Checkout Success Page: shows a “Subscribe me to email updates” checkbox on the order-confirmation page, for guests and registered customers alike. Shoppers whose email is already subscribed never see it, and it hides automatically when the Pixel is active.
Customer Registration Form: adds a “Sign me up for marketing emails” checkbox to the storefront account-creation form; new subscriptions respect double opt-in.

Grow your audience →

Customer Tags

Automatically tags audience members with the product categories in their order history.

Enable Automatic Tags: applies cat:<category path> tags (for example, cat:men/shoes/running) to contacts with a registered customer account, based on the categories they have purchased from in this store view. Guest purchases are not tagged.

Tags, data fields & segmentation →

Pulse Behavioral Events

Controls the server-side behavioral events that complement the Pixel.

Process Pulse Events: master toggle for the behavioral events pipeline (default: Yes).
Events to ignore when Pixel ON: the events the Pixel already covers from the browser; only applies while the Pixel is actively tracking. All are selected by default so the server side skips them; deselect an event to also send it server side.
Skip page-view events: keeps page views out of the server-side events lane (default: No). It does not affect the Pixel’s own page-view tracking.

The Mailchimp Pixel & behavioral events →

Admin Dashboard

Controls the Mailchimp card on Magento’s admin dashboard.

Show Status Card on Admin Dashboard: shows a Mailchimp Status card with total contacts, abandoned carts, recovered revenue, and a customer-segments breakdown (default: Yes; global scope).

Advanced

Developer and operational settings. Change these only when troubleshooting or as directed by support.

Debug Logging: writes detailed sync activity to var/log/. Global scope; disable in production.
PII Masking in Logs: controls whether customer data is redacted in log files and in the admin payload detail views (the Webhook Log and the Queue Audit Trail). Defaults to masked; unmasked mode auto-reverts after 24 hours.
Error Retention: how many days sync-queue error rows are kept before the hourly cleanup removes them; the underlying error details remain in the API Sync Log.
Auto-Stop Failure Streak: how many consecutive connection failures must occur before sync for an account stops automatically (default: 8).
Auto-Stop Minimum Minutes: how long that failure streak must persist before the automatic stop applies (default: 30). A stopped account resumes from the Mailchimp Accounts page.
API Sync Log retention (days): how long API request/response records are kept; successful payloads are trimmed earlier than error payloads.
Sync Queue retention (days): how long completed sync queue rows are kept before the hourly cleanup.
Cron Telemetry retention (hours): how long cron telemetry records are kept (default: 24).
Additional retention windows for relay, webhook, cart token, and event data are also adjustable here.

Privacy, data & compliance →

Each connected store registers with ebizmarts so we can support your installation and improve the extension. The registration is separate from your Mailchimp connection and sends no order, customer, or cart data; it does carry store and admin contact details, and Privacy, data & compliance lists exactly what is sent.

Registration Service URL: the ebizmarts registration endpoint. Leave at the default unless support directs you to change it.

Data sharing is on by default and can be paused per store from the Support tab in that store’s Mailchimp connection popup. Pausing stops the hourly health-data push; the registration snapshot and the liveness ping continue so we can keep supporting the installation.

Questions along the way? Troubleshooting has the answers, and ebizmarts support is one email away.

Next: Privacy, data & complianceWhat data the extension handles and shares, and the controls available to you.