Skip to main content
Metrics type: Key Metrics • Category: Email Marketing
Sudden bounce surge = list contamination from a bad import. Cap sends until investigated.

​
At a glance

A 24-hour anomaly detector for bounce-rate spikes. Fires when last-24h bounce rate exceeds the 30-day rolling baseline by more than 2 standard deviations. A sudden spike almost always means list contamination from a bad import, a re-engagement send to a dormant tier, or a deliverability event. Cap sends until investigated. Compares against Bounce Rate’s slower-moving 30D rate; this alert catches the spike before the 30D rolling number registers it.

​
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 small DTC accessories brand on Shopify with Mailchimp Standard, single audience of 24,000. Steady-state metrics over the prior 30 days: Then, on 28 Apr 26, the merchant imported 3,500 contacts from a recent trade show signup CSV without confirmation. They sent the next regular newsletter to the full audience of 27,500. Five observations:
  1. The alert fired exactly as intended. Without the alert, the merchant would have continued sending under the assumption everything was fine. The 30D rolling rate would only register the breach over the next 5-7 days, by which time Gmail and Yahoo would already be throttling the domain. The 24h spike alert exists to catch the bad import before reputation damage compounds.
  2. The bad import contributed 6.3% bounce rate on its own slice. 220 hard bounces out of 3,500 imported = 6.3%, well above the 5% Mailchimp Compliance ceiling. Trade-show CSVs almost always degrade faster than expected: emails written by hand on a clipboard contain typos, throwaway addresses given to avoid spam, role-based aliases that bounce on bulk sends.
  3. The existing audience’s bounce rate at 0.69% is healthy, the spike is import-only. This diagnostic separation is the value of the alert. If both slices showed elevated bounces, the cause would be deliverability (sender reputation crisis); seeing only the import slice spike means the cause is list contamination.
  4. The remediation sequence is well-defined. Step 1: pause sends to the imported contacts immediately. Step 2: suppress the hard-bouncing 6.3% of imports (220 contacts) explicitly. Step 3: send a confirmation email to the remaining 3,280 imports asking them to opt in (double-opt-in). Step 4: only the confirmed survivors return to the audience proper. Step 5: monitor the next 3 sends; if the 24h alert stays cleared, you’re recovered.
  5. Mailchimp’s automation depth is light enough that this manual remediation is required. Klaviyo has a built-in “list cleanse on import” flow that flags this pattern automatically. Mailchimp does not. Vortex IQ’s audit MC-DEL-001 (sustained bounce >5%) and this 24h spike alert together cover the gap, but the response is still merchant-driven.

​
Sibling cards merchants should reference together

​
Reconciling against the vendor’s own dashboard

Where to look in Mailchimp’s own dashboard: Mailchimp does not surface a “spike alert” natively. The closest views are Mailchimp → Reports → individual recent campaign → Performance for the per-campaign bounce rate of the suspected trigger, and Mailchimp → Account → Sender Reputation for the blended reputation score that lags behind the spike. This alert is a Vortex IQ-derived statistical detection layered on top of Mailchimp’s raw bounce data. Why our alert state may legitimately differ from a hand-built calculation: Cross-connector reconciliation: This alert is Mailchimp-internal. Closest cross-references:

​
Known limitations / merchant FAQs

The alert just fired, what’s my next step? Stop sends to the affected audience immediately, even if the absolute rate looks “okay” (e.g. 4% bounce rate is below the sustained 5% Mailchimp Compliance ceiling but is still a 2σ spike if your baseline is 1.4%). Then identify the trigger: open Mailchimp → Reports, sort by bounce rate, look at the most recent send. If a single campaign drove the spike, suppress the bouncing addresses (1-2 minutes in Mailchimp UI) before the next send. Why does this fire when my 30D rate is still healthy? That’s the point. The 30D rolling rate dilutes a single bad send across 30 days of healthy ones; by the time it crosses the 5% threshold, your domain reputation is already damaged. The 24h spike alert catches the bad send when remediation is still cheap, before Gmail/Yahoo register the breach in their reputation systems. Will the alert fire on my normal re-engagement campaign? Yes if the campaign bounces above 2σ baseline. Re-engagement campaigns inherently bounce 5-15% (dormant addresses degrade), which is well above typical 1-2% baseline. The alert is doing its job by flagging the elevated rate. Strategically, run re-engagement campaigns to small batches (<2,000) so the 24h aggregate stays below the 2σ threshold even with high per-campaign rates. Can I tune the threshold? Not from the card; the 2σ rule is hard-coded. If you regularly run high-bounce-rate campaigns (re-engagement, dormant cleanup) and want to suppress false positives, run them in small batches over multiple days so each 24h window stays under threshold. My alert is firing but I haven’t sent anything in 24h, why? Customer Journey emails count toward the 24h window. Even with no broadcast campaigns, a high-volume welcome flow or abandoned-cart automation can fire enough sends to register. If those sends are bouncing at elevated rates, the alert catches it. Cross-check Customer Journey Count and the per-journey performance. What if I just sent to a brand-new audience? First-send-to-import bouncing is normal and expected, the alert correctly fires. The right response: confirm whether the import was double-opt-in. If yes, the high bounce rate is unlucky list quality and you’ll suppress and recover. If no, the import shouldn’t have been sent without confirmation, suppress the worst-bouncing 5-10% and stop sending to the rest until you’ve run a confirmation flow. Does the alert distinguish hard from soft bounces? No. Both contribute to the 24h rate equally because both indicate immediate deliverability risk. Soft bounces that recover into deliveries don’t reduce the alert; once a soft bounce is recorded for a recipient on a send, it counts. Why not 3σ? 3σ corresponds to ~99.7% confidence; firing only on 0.3% of sends would miss meaningful spikes that are real but not extreme. 2σ is the standard convention for early-warning anomaly detection. False-positive rate at 2σ is acceptable (~5%, mostly on re-engagement campaigns which the merchant should know to expect). The alert was firing then cleared on its own, what happened? Mailchimp auto-suppresses hard bouncers after first bounce. Subsequent 24h windows don’t include those addresses, so the rate falls naturally. The alert clearing isn’t necessarily proof you’re fine, the contaminated addresses moved to “cleaned” status, but they still consumed sends and damaged reputation on the way. Investigate the trigger even if the alert cleared. Do I need to do anything when the alert hasn’t fired? No. This is an exception alert; absence of fire means baseline is stable. Continue monitoring Bounce Rate for the slower-moving 30D view.

​
Tracked live in Vortex IQ Nerve Centre

Bounce Spike 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 or book a demo to see this metric running on your own data.