Customers buying from your store but missing from your email list = recurring marketing leak. Sync via Mailchimp’s ecom integration or manual list-add.
At a glance
The count of customers who have purchased from your store but are not subscribed in Mailchimp. This is a cross-channel card: it compares the store’s customer list against the Mailchimp audience and surfaces the gap, people who have proven they will buy but who you cannot reach through your cheapest, highest-ROI retention channel. This is one of the most common and most quietly expensive leaks in ecommerce. Every customer in this gap is someone you paid to acquire (through ads, organic, or word of mouth) and are now unable to nurture toward a second purchase by email. They will not get your welcome series, your win-back, your product launches, or your abandoned-cart recovery, because they are not on the list. The gap usually opens for mundane reasons: guest checkout that did not capture consent, an ecom integration that is not syncing customers, or customers who unsubscribed but keep buying. The fix is straightforward, sync the store customers into Mailchimp (with proper consent) via the ecom integration or a compliant list-add, so the size of the gap is far less important than the fact that it is closeable revenue.
| What it counts | The number of store customers (people with at least one order) whose email address is not present and subscribed in any Mailchimp audience. The headline is the count; the high-value subset (top spenders in the gap) is the priority. |
| Why cross-channel | The customer list is a store fact; the subscribed audience is a Mailchimp fact. The gap between them, buyers who are not subscribers, is only visible by joining both. Neither system flags it alone. |
| Why it is expensive | Each customer in the gap was acquired at full cost and is now unreachable by your cheapest retention channel. The lifetime value you forfeit by not being able to email them, no welcome, no win-back, no launch, no cart recovery, compounds over every campaign they miss. |
| Common causes | (1) Guest checkout that did not capture email-marketing consent. (2) The ecom integration not syncing customers into Mailchimp (or syncing incompletely). (3) Customers who unsubscribed but keep purchasing (these stay in the gap by their own choice and must not be re-added without consent). (4) Email-address mismatches between the store and Mailchimp records. |
| The compliance caveat | Customers who did not consent, or who actively unsubscribed, must not be added to marketing email without a lawful basis. The fix is to capture consent at the right moments, not to bulk-import unconsented buyers. |
| Currency | The gap carries forfeited lifetime value; the count is the headline. Revenue context lives in total-revenue. |
| Time window | 30D (30-day rolling on recent buyers), surfacing newly-leaked customers as they appear. |
| Alert trigger | More than ~100 high-value customers in the gap, a leak large enough to warrant fixing the consent-capture or sync pathway, not just a one-off add. |
| Sentiment key | mc_xc_subscriber_vs_customer_drift |
| Roles | owner, marketing, finance |
Calculation
Calculated automatically from your joined store and Mailchimp data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
A kitchenware brand on BigCommerce running Mailchimp Standard. Snapshot for buyers in the 30-day window ending Monday 08 Jun 26.| Measure | Count |
|---|---|
| Store customers who purchased (30d) | 2,140 |
| Of whom subscribed in Mailchimp | 1,510 |
| In the gap (buyers not subscribed) | 630 |
| Of the gap: high-value (above-average order value) | 142 |
| Cause | Approx. share of the gap | Closeable? |
|---|---|---|
| Guest checkout, no marketing consent captured | 58% | Yes, capture consent at checkout |
| Ecom integration not syncing some customers | 24% | Yes, fix the sync |
| Unsubscribed but still buying | 13% | No, must respect the opt-out |
| Email mismatch (store vs Mailchimp record) | 5% | Yes, reconcile records |
- 630 of 2,140 recent buyers (29 percent) are not on the email list. Nearly a third of customers you can sell to once, you cannot email. And 142 of them are high-value. This is a material, mostly-closeable leak, the alert fires because the high-value subset (142) is well above the ~100 threshold.
- The biggest cause is fixable: guest checkout without consent (58 percent). Most of the gap is customers who checked out as guests and were never asked to opt in. The fix is upstream, add a clear, compliant email-marketing consent option at checkout (and post-purchase) so these customers enter the list legitimately going forward. This stops the leak at its source rather than chasing already-leaked customers.
- The second cause is purely technical: sync gaps (24 percent). A quarter of the gap is customers the store has (with consent) but the ecom integration did not push into Mailchimp. The fix is to repair the integration sync, these customers can be added immediately because consent already exists. Cross-reference the connector status to confirm the ecom integration is fully connected.
- The third cause must be left alone: unsubscribed-but-buying (13 percent). These customers opted out of email but still purchase. They must not be re-added to marketing email, that would breach their opt-out and email regulation. The right response is to respect the opt-out and reach them through other channels (on-site, SMS with separate consent, or simply excellent product and service). Counting them in the gap is informative, but they are not a closeable part of it.
- The fourth cause is housekeeping: email mismatches (5 percent). A small share are customers who are on the list but under a different email than the store has on file. Reconciling the records closes these.
- The economics of closing the gap. Of the 630, roughly 87 percent (the consent and sync causes) are legitimately closeable. Bringing those ~550 buyers onto the list, with proper consent, makes them reachable by every automation that drives repeat purchase: welcome, win-back, launches, cart recovery. For customers you already paid to acquire, this is among the cheapest incremental revenue available.
- Decompose the gap by cause. The fix is entirely different for consent gaps, sync gaps, opt-outs, and mismatches.
- Fix consent capture first. Most gaps come from guest checkout without consent; fixing the checkout opt-in stops the leak at source.
- Repair the ecom integration sync. Customers with consent that simply did not sync can be added immediately.
- Respect opt-outs. Unsubscribed buyers stay out of marketing email; do not bulk-import them.
- Reconcile email mismatches. A small housekeeping pass closes the records that differ between store and Mailchimp.
| Time horizon | Action |
|---|---|
| First day | Decompose the gap by cause; confirm the ecom integration is connected and syncing. |
| First week | Add a compliant email-marketing consent option at checkout and post-purchase to stop the leak at source. |
| First month | Sync the consented-but-unsynced customers into Mailchimp; reconcile email mismatches; size the recovered reach. |
| Ongoing | Monitor the gap each period; a persistent gap means the consent-capture pathway, not just the back-catalogue, needs fixing. |
Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
top-spenders-unengaged-on-email-90d | The other revenue-at-risk leak: high-value customers who are on the list but ignoring it. Read together for the full retention-gap picture. |
audience-coverage-of-customer-base | The percentage view of the same gap: what share of customers your list actually covers. |
net-audience-growth-30d | Closing this gap is a legitimate, high-quality growth source, consented buyers are the best subscribers. |
audience-count | The list size this gap could grow if the closeable customers were synced. |
total-revenue | The revenue context; the gap is reachable repeat-purchase revenue you currently forfeit. |
welcome-automation-status | Newly-synced customers should flow into the welcome series; confirm it is live to nurture them. |
win-back-automation-recovery-rate | Once on the list, lapsing customers from this gap become win-back candidates. |
segments-overview | Use to segment newly-synced customers by purchase behaviour for tailored onboarding. |
Reconciling against Mailchimp
Where to look in Mailchimp’s own dashboard, and in your store:- Mailchimp → Account → Integrations to confirm the store ecom integration is connected and syncing customers, the most common technical cause of the gap.
- Mailchimp → Audience → All contacts for the subscribed audience this card compares the store customer list against.
- Your store’s customer list (BigCommerce, Shopify, etc.) for the full set of buyers, including guest-checkout customers, that forms the other side of the comparison.
| Reason | Direction | What to do |
|---|---|---|
| Email matching. Customers are matched by email between store and Mailchimp; a typo or alternate address shows as a gap even though the person is on the list. | Gap may overstate | Reconcile email mismatches; a small share of the gap is matching artefacts, not genuine non-subscribers. |
| Consent state. Unsubscribed and never-consented buyers both appear in the gap but are not closeable. | Gap includes non-closeable rows | Decompose by consent; only the consented-but-unsynced and consent-capturable customers are actionable. |
| Integration coverage. If the ecom integration is partial or recently connected, more customers appear unsynced than truly are. | Gap may overstate | Confirm the integration is fully connected and back-filled before acting on the count. |
| Guest checkout. Guest buyers may lack a stored marketing-consent flag even if they would consent; they appear in the gap until consent is captured. | Gap reflects a consent-capture gap, not a sync failure | Fix the checkout consent flow; these are closeable going forward, not retroactively without consent. |
| Refresh lag. The gap recalculates each sync; store and Mailchimp data update on their own cadences. | Vortex IQ moves slowly | Wait for the next sync; check last_synced_at. |