> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Unsubscribe Burst (>3x 7-day baseline), Mailchimp > Unsubscribe Burst (>3x 7-day baseline) for Mailchimp stores. A live alert when a campaign sheds subscribers far above normal. Tracked live in Vortex IQ Nerve Centre. **Card class:** [Hero](/nerve-centre/overview#card-classes-explained) • **Category:** [Email Marketing](/nerve-centre/connectors#connectors-by-type) > Pace check, sustained 3x usually means a content or segmentation problem. Pause sends and investigate before the next campaign goes out. ## At a glance > A real-time anomaly detector for unsubscribe spikes. It fires when a campaign's unsubscribe rate runs more than three times the account's rolling 7-day baseline unsubscribe rate. **Unsubscribes are permanent and compounding**, every subscriber lost to a burst is a recipient you can never re-message and a contact you may still be paying for, so a burst is both an immediate signal that something in the send was wrong and a forward warning that the next campaign will reach a smaller, possibly more irritated audience. The usual causes are a content or subject-line mismatch, a send to a segment that did not opt in for that kind of message, a sudden frequency increase, or a re-engagement send to a dormant tier that mostly wanted out anyway. The card surfaces the offending campaign so the team can pause the wider send and fix the cause before the damage spreads across the programme. | | | | ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **What it counts** | A multiple: the campaign's unsubscribe rate divided by the account's 7-day rolling baseline unsubscribe rate. The card lists each campaign whose multiple exceeds 3x, with the campaign name, its unsubscribe rate, the baseline, and the absolute count of unsubscribes. | | **Why a multiple, not an absolute rate** | A flat absolute threshold (say, 1 percent) is too crude. A brand whose normal unsubscribe rate is 0.1 percent should be alarmed at 0.4 percent; a brand whose normal rate is 0.6 percent should not. Measuring against each account's own baseline catches the deviation that matters for *that* account. | | **Why 3x** | Three times baseline is a deliberate signal-to-noise threshold. Normal send-to-send variation rarely exceeds 2x; a sustained 3x almost always points at a specific, fixable cause rather than random fluctuation. | | **Common root causes** | (1) Content or subject-line mismatch, the email promised or implied something the body did not deliver. (2) Wrong segment, a send went to people who never opted in for that message type. (3) Frequency spike, too many sends in a short window triggers fatigue unsubscribes. (4) Re-engagement send to a dormant tier where unsubscribing is the natural response. (5) A list of recently-acquired, poorly-qualified subscribers (often paid-social-sourced) churning on first contact. | | **Currency** | n/a, this is a count and a multiple. The downstream revenue cost surfaces as shrinkage in [`net-audience-growth-30d`](/nerve-centre/kpi-cards/mailchimp/audience-growth-rate) and [`revenue-per-recipient`](/nerve-centre/kpi-cards/mailchimp/revenue-per-recipient). | | **Time window** | `RT` (real-time) against a 7-day rolling baseline. The campaign rate is evaluated as soon as send activity registers; the baseline is the trailing-7-day reference. | | **Alert trigger** | Any campaign whose unsubscribe rate exceeds 3x the 7-day rolling baseline. Each qualifying campaign is one alert row. | | **Sentiment key** | `mc_alert_unsubscribe_burst` | | **Roles** | owner, marketing | ## Calculation Calculated automatically from your 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 fashion brand on BigCommerce running Mailchimp Standard, normal weekly cadence. The account's 7-day rolling baseline unsubscribe rate is 0.18 percent. Snapshot for sends in the week ending Friday 12 Jun 26. | Campaign | Recipients | Unsubscribes | Unsub rate | vs baseline (0.18%) | Alert? | | ----------------------------- | ---------: | -----------: | ---------: | ------------------: | ------ | | Weekly New Arrivals | 41,200 | 78 | 0.19% | 1.1x | No | | Mid-Season Sale (full list) | 44,800 | 121 | 0.27% | 1.5x | No | | "We Miss You" win-back blast | 9,300 | 196 | 2.11% | 11.7x | Yes | | Flash 48h, 3rd send in 4 days | 40,100 | 248 | 0.62% | 3.4x | Yes | What this snapshot is telling us: 1. **Two campaigns tripped the alert, for two different reasons.** The win-back blast at 11.7x baseline and the third flash-sale send at 3.4x baseline are both well above the 3x threshold, but the diagnosis and fix differ. 2. **The win-back blast at 11.7x is partly expected, partly a warning.** Re-engagement sends to dormant subscribers naturally draw high unsubscribe rates, many of those contacts wanted out and the email was simply the prompt. Some of this is healthy list-hygiene (better an unsubscribe than a future spam complaint). But 2.11 percent is high even for win-back; check the subject line and offer. **Action**: confirm this was a deliberate dormant-tier send. If so, it is doing its job but should be sized and timed carefully; if the segment accidentally included engaged subscribers, that is a real loss. 3. **The third flash-sale send at 3.4x is the genuine problem.** Three sends in four days is a frequency spike, and the unsubscribe rate climbing send-over-send is the classic fatigue signature. **Action**: pause the rest of the flash sequence. The marginal revenue from a third send rarely covers the lifetime value of the subscribers it burns. Cross-reference [`send-cadence`](/nerve-centre/kpi-cards/mailchimp/send-cadence), the spike will be visible there. 4. **The two non-alerting campaigns are healthy.** New Arrivals at 1.1x and the sale at 1.5x are normal variation. A full-list sale send drawing slightly above baseline is expected and not a concern. 5. **The compounding cost.** The two bursts together shed 444 subscribers in a week against a baseline that would have predicted roughly 130. The \~310 excess unsubscribes are permanent, every future campaign now reaches a smaller audience, and the revenue-per-recipient math degrades accordingly. The diagnostic flow when this card fires: 1. **Identify whether the burst was intentional.** A planned win-back or sunset send to a dormant tier will naturally spike; distinguish it from an accidental burst on an engaged segment. 2. **Check the segment.** Did the send reach people who opted in for this message type? Mis-targeted sends are the most common avoidable cause. 3. **Check the frequency.** Was this the third or fourth send in a short window? Fatigue bursts climb send-over-send. 4. **Review the content and subject line.** A mismatch between the subject promise and the body, or a tone that does not fit the brand relationship, drives unsubscribes. 5. **Pause the wider campaign if a sequence is running.** Do not let the next send in a sequence go out on the same flawed premise. The rapid-response playbook for marketing leadership: | Time horizon | Action | | ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | | First 30 minutes | Confirm whether the burst was a deliberate win-back send or an unexpected spike on an engaged audience. | | First 2 hours | If unexpected, pause any pending sends in the same sequence and identify the segment and content cause. | | First day | Estimate the permanent audience loss and feed it into the next campaign's reach forecast; review the segment definition that produced the send. | | First week | Review send frequency and segmentation policy; recurring bursts signal a structural cadence or targeting problem, not a one-off bad campaign. | ## Sibling cards merchants should reference together | Card | Why merchants reach for it | | -------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | | [`unsubscribe-rate`](/nerve-centre/kpi-cards/mailchimp/unsubscribe-rate) | The slower-moving 30-day rate this alert is a spike-detector for. The burst catches what the rolling rate will only register later. | | [`net-audience-growth-30d`](/nerve-centre/kpi-cards/mailchimp/audience-growth-rate) | Where the permanent cost of a burst lands. A burst pulls net growth down for the period. | | [`send-cadence`](/nerve-centre/kpi-cards/mailchimp/send-cadence) | Frequency-driven bursts show up here. If cadence spiked alongside the burst, frequency is the cause. | | [`abuse-spam-complaint-spike`](/nerve-centre/kpi-cards/mailchimp/abuse-spam-complaint-spike) | Spam complaints often accompany unsubscribe bursts and are far more damaging to deliverability. Check both together. | | [`top-campaigns-by-revenue`](/nerve-centre/kpi-cards/mailchimp/top-campaigns-by-revenue) | Weigh the revenue a burst-causing send earned against the subscribers it cost. Frequently the trade is not worth it. | | [`spam-complaint-rate`](/nerve-centre/kpi-cards/mailchimp/spam-complaint-rate) | The deliverability-damaging cousin of unsubscribe. A burst that is also drawing complaints is a sender-reputation event. | | [`email-health-kpis`](/nerve-centre/kpi-cards/mailchimp/email-health-kpis) | Unsubscribe rate is a weighted sub-metric of the composite health score. Sustained bursts drag the composite down. | | [`segments-overview`](/nerve-centre/kpi-cards/mailchimp/segments) | Mis-targeted segments are the most common avoidable burst cause. Use to audit which segment the offending send went to. | ## Reconciling against Mailchimp **Where to look in Mailchimp's own dashboard:** * **[Mailchimp → Reports → All campaigns](https://us1.admin.mailchimp.com/reports/)** and open the offending campaign report. The Unsubscribed figure and rate are in the campaign summary. * **Mailchimp → Audience → All contacts → filter by unsubscribed** to see who left and (where captured) the campaign that prompted it. * **Mailchimp → Reports → Comparative reports** to view unsubscribe rate trend across recent campaigns, which is the raw material for the rolling baseline. **Why the Vortex IQ alert may legitimately differ from a single Mailchimp number:** Mailchimp shows the absolute unsubscribe count and rate per campaign; it does not compute a 3x-baseline multiple. Reconciliation is therefore confirming the campaign rate and the baseline, not disputing a Mailchimp figure: | Reason | Direction | What to do | | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | | **Baseline definition.** The alert compares against a 7-day rolling account baseline; Mailchimp shows only the per-campaign rate. | Not directly comparable | The campaign rate should match Mailchimp's; the multiple is Vortex IQ's derived comparison against your trailing 7 days. | | **Send-time vs evaluation-time.** Unsubscribes accrue for hours or days after a send; the multiple is computed on the data available at evaluation. | Multiple may rise after first evaluation | Re-check after unsubscribes have fully accrued; large sends keep shedding for 24-48 hours. | | **Account-wide vs audience-specific baseline.** The baseline blends across the account; an audience with a structurally higher unsubscribe norm can trip more easily. | Vortex IQ may flag a high-norm audience | Consider the sending audience's own historical rate when judging whether a burst is genuinely abnormal. | | **Refresh lag.** The alert evaluates on each sync cycle; Mailchimp's report updates within minutes of unsubscribe activity. | Vortex IQ moves **slowly** vs the live report | Wait for the next sync; check `last_synced_at`. | **Quick rule for support tickets:** when a merchant asks "Mailchimp shows 0.6 percent unsubscribe, why is that an alert?", explain the card measures against *their own* baseline, not a fixed threshold. 0.6 percent on an account that normally runs 0.18 percent is a 3.4x deviation worth investigating, even though 0.6 percent sounds low in isolation. The deviation is the signal. ## Known limitations / merchant FAQs **My win-back campaign always trips this. Is that wrong?** No, it is expected. Re-engagement and sunset sends to dormant subscribers naturally draw high unsubscribe rates because many of those contacts wanted out and the email was the prompt. For win-back specifically, a burst is partly healthy list hygiene, an unsubscribe is preferable to a future spam complaint. The card still flags it so you can confirm the send was deliberate and that the segment did not accidentally include engaged subscribers. Treat a flagged win-back as "confirm, then dismiss" rather than "emergency". **Why measure against a 7-day baseline rather than a fixed rate?** Because a fixed rate is wrong for most accounts. A brand whose normal unsubscribe rate is 0.1 percent and a brand whose normal rate is 0.6 percent need different alarm points. Measuring each send against the account's own recent baseline catches the deviation that matters for that specific programme, which a one-size threshold cannot do. **A new product launch drew a lot of unsubscribes. Was the launch a mistake?** Not necessarily. A high-reach launch send to the full list will draw more unsubscribes in absolute terms simply because more people received it. What matters is the rate relative to baseline and whether the launch revenue justified the audience cost. Pair this alert with [`top-campaigns-by-revenue`](/nerve-centre/kpi-cards/mailchimp/top-campaigns-by-revenue): a launch that earned strongly and shed a modest excess of subscribers may be a fine trade; one that earned little and shed many is not. **The same campaign keeps appearing in the alert across syncs. Why?** Because the condition is still true, the campaign's rate is still above 3x baseline. Unsubscribes accrue for a day or two after a large send, so the multiple can stay elevated until accrual completes. The alert clears once the campaign's rate settles back within range relative to the rolling baseline, or once the send ages out of the active window. **Does this count spam complaints?** No. This card counts unsubscribes specifically. Spam complaints are tracked separately by [`spam-complaint-rate`](/nerve-centre/kpi-cards/mailchimp/spam-complaint-rate) and [`abuse-spam-complaint-spike`](/nerve-centre/kpi-cards/mailchimp/abuse-spam-complaint-spike), because complaints damage sender reputation far more than unsubscribes do. A send that triggers both an unsubscribe burst and a complaint spike is a serious problem; check both cards. **Can Vortex IQ pause my campaign automatically?** No. Vortex IQ is read-only by design. It flags the burst, names the campaign, and points at the likely cause; pausing a sequence or revising a segment happens in Mailchimp by the merchant's team. The Vortex Mind Customer Recovery Opportunity report can raise a merchant-side Action recommending a pause, but the action stays with the merchant. *** ### Tracked live in Vortex IQ Nerve Centre *Unsubscribe Burst (>3x 7-day baseline)* is one of hundreds of KPI pulses Vortex IQ tracks across Mailchimp and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. [Start for free](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.