
Morning check
Twelve merchants, one dashboard each, all green. The developer moves on to the day's work.
Monitoring
An agency runs the extension for a dozen merchants. The dashboard in each Magento admin shows sync status, revenue attribution, store health and alerts; the cron and queue monitors show depth, throughput and recent runs; notifications flag anything that needs a look. The developer fixes it from the admin or the CLI, and the docs explain every state.

Why it matters
Sync status, queue depth, last activity and errors per store view, so a problem on one storefront is not hidden by ten healthy ones.
Notifications in the admin when a sync fails or the queue backs up, and sync that stops itself after a streak of network failures instead of hammering a dead connection.
Retry and heal on the entity queue, run-now on the cron monitor, an API log with request, response and latency per call, and CLI commands for status, drain, resync and webhook key rotation.
The agency guide in the documentation covers running the extension for many merchants from one team.
How it works
Marketing, Intuit Mailchimp, Dashboard: sync status, revenue attribution, abandoned carts, audience snapshot, customer segments, store health and alerts, plus a status card on Magento's own dashboard.
Cron Monitor for queue depth, throughput and recent runs with run-now; Queue Monitor and Entity Queue for every row; Events Tracking for behavioural events; API Log, Webhooks and a QoS report with success rate, retries and latency percentiles.
Operational and critical messages land in Notifications in the admin. Anonymised health snapshots also reach ebizmarts support, outbound only and with an opt-out, so the people who wrote the extension can spot trouble too.
Retry and heal failed rows, reconnect an account, or resync a store from the admin or the CLI. Logs mask customer data by default and never hold credentials.
Ways merchants use it
Agencies running many stores, in-house teams who cannot watch an admin all day, and anyone who has been surprised by a stale audience.

Twelve merchants, one dashboard each, all green. The developer moves on to the day's work.

A merchant's hosting blocked outbound calls overnight. Sync stopped itself after the failure streak, the notification landed, and once the firewall was fixed the queue drained before lunch.

A store migrated servers. One resync from the CLI, dry-run first, rebuilds its sync overnight, and the campaign performance report is complete again by morning.
What you need
Also in Marketing Automation
Questions
Sync status, revenue attribution, abandoned carts, audience snapshot, customer segments, store health and alerts, per store view, in the Magento admin.
Through Notifications in the Magento admin, with operational and critical messages about the installation. Sync also stops itself after a configurable streak of network failures.
Yes, from the admin or the CLI. Single records can be pushed again from their Mailchimp Sync tab, and failed queue rows can be retried and healed.
Anonymised health snapshots: counts, percentiles and codes, never customer data. It is outbound only, a merchant can opt out, and ebizmarts being unreachable never affects the sync.
The documentation has a dedicated page on revenue discrepancies and their usual causes.
The setup wizard takes a few minutes. If something in your setup is unusual, the Marketing Automation team at ebizmarts is one email away.