Skip to main content
Card class: Cross-ChannelCategory: Email Marketing
Distribution of hours-to-purchase after a campaign send. Tight cluster <24h = strong send; long tail = weak hook.

At a glance

The distribution of hours between a Mailchimp campaign send and the resulting attributed purchase, computed across the top 10 revenue-generating campaigns in the period. Buckets: <1h, 1-4h, 4-12h, 12-24h, >24h. A tight cluster <24h means the campaign hooks immediate-purchase intent (good); a long tail beyond 24h means the campaign builds awareness but doesn’t drive immediate action (the hook is weak). Mailchimp’s 24h click attribution default means anything beyond 24h is unattributed; the >24h bucket here captures click-then-bookmark-then-buy patterns visible only via UTM matching.
What it countsPer-campaign hour-bucket distribution: percentage of attributed orders falling in each of [<1h, 1-4h, 4-12h, 12-24h, >24h] post-send. Computed by joining Mailchimp campaign send_time with commerce platform’s order created_at, filtered by UTM source = Mailchimp.
API endpointMarketing API v3 for campaign send_time and per-campaign report; commerce platform API for order created_at and customer email match. Engine joins client-side.
Audience-based scopeTop-10 revenue campaigns across all audiences. Audience-level lag distributions not surfaced.
Channel scopeEmail regular + A/B test campaigns only. Customer Journey emails excluded (they trigger on behaviour, not scheduled send, lag distribution would be meaningless).
Bounce / spam handlingBounces have no purchase, excluded by definition.
Attribution modelMailchimp’s 24h click default is the “attributed” cutoff. Orders >24h post-click are NOT in Mailchimp’s reported revenue but ARE captured here via UTM matching, surfacing the over-window long tail.
MPP impactNone. Lag is measured from send to order, not via opens.
Click-vs-send anchorLag is measured from send_time (campaign push time), not click-time. Customers who open hours later still measure their lag from send. This makes the metric directly comparable across campaigns.
CurrencyNot applicable.
Time window90D (longer window for stable distribution; lag distributions are noisy on small samples)
Alert trigger- (no alert; this is a diagnostic / discovery card)
Rolesmarketing

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 kitchenware brand on Shopify, Mailchimp Standard. Top 3 campaigns over 90D window 02 Feb 26 to 02 May 26.
Campaign<1h1-4h4-12h12-24h>24hTotal orders
Mother’s Day “Cook For Mum”28%42%14%8%8%168
Spring sale 20% off (3-day flash)15%38%22%14%11%122
March newsletter (general content)4%12%18%16%50%28
Five observations:
  1. Mother’s Day’s lag profile is textbook strong. 70% of orders within 4 hours of send, 84% within 12 hours. The campaign creates immediate purchase intent because the deadline (Mother’s Day) is concrete and the product is gift-able. A campaign with this lag profile justifies the broadcast send model, you’re hitting an intent-rich window.
  2. Spring sale is good but slower than Mother’s Day. The flash sale draws purchases over a longer window (24% in the 4-24h bucket) because customers want to compare before buying. This is healthy for promotional sends; the 3-day duration of the flash matches the buying-cycle behaviour. Don’t push customers harder; let them browse.
  3. The March newsletter is a weak hook. 50% of orders fall in the >24h bucket, which means the newsletter raised awareness but didn’t drive action. Customers came back days later via direct visits or organic search. Mailchimp’s 24h attribution doesn’t credit these orders, so the newsletter’s reported revenue understates its actual contribution. For awareness-style sends, Email Share of Total Store Revenue is the better metric than per-campaign attributed revenue.
  4. The list-based blast pattern shows up in the lag distribution. Mother’s Day went to the full list including dormant subscribers; among the dormant subscribers who did buy, lag was longer (because they need more time to re-engage with the brand). Segmented sends to “engaged 60d” subscribers would produce a tighter lag profile across all three campaigns. This is the segmentation-vs-list debate quantified.
  5. The >24h bucket is the under-credited revenue bucket. Mailchimp doesn’t attribute orders beyond 24h to the campaign that drove awareness. For awareness-heavy newsletters and brand campaigns, the >24h share can be 30-60%, meaning Mailchimp’s e-commerce-attributed revenue substantially understates the actual contribution. Use this card to identify newsletters where the long tail is doing real work.

Sibling cards merchants should reference together

CardWhy pair it with Send-to-Purchase Lag
Mailchimp Top Campaigns by RevenueLag distribution makes most sense for the top revenue campaigns; same scope.
Mailchimp Click RateHigh click rate + tight lag = strong send. High click rate + long tail = good content but weak buying trigger.
Mailchimp Email-Attributed RevenueLag exposes the under-attributed long tail beyond Mailchimp’s 24h window.
Mailchimp Email Share of Total RevenueAwareness-heavy newsletters under-credit on this share; lag explains why.
Shopify Time-to-PurchaseIndependent measure of buying-cycle length per product category.
Mailchimp Campaign Send CadenceIf sends are too frequent, lag gets compressed (customers buy sooner to clear inbox); if too rare, lag stretches.
Mailchimp Conversion RateTight lag campaigns typically have higher conversion rate; the metrics correlate.
GA4 Email Channel SessionsCross-validation, GA4 sees the click-to-purchase journey across the full window, not just 24h.

Reconciling against the vendor’s own dashboard

Where to look in Mailchimp’s own dashboard: Mailchimp does not surface this distribution natively. The closest views are Mailchimp → Reports → individual campaign → E-Commerce tab which shows orders per campaign without lag bucketing, and Mailchimp → Reports → Comparative Reports which doesn’t bucket by lag either. This card is a Vortex IQ-derived distribution computed by joining Mailchimp send_time with commerce platform order created_at. Why our number may legitimately differ from a hand-built calculation:
ReasonDirection of divergence
Time-zone. Send_time is in Mailchimp’s account tz; order created_at is in the commerce platform’s tz; Vortex IQ normalises to UTC. Boundary edge cases shift by 1 hour.<1% on bucket distribution
UTM matching vs Mailchimp’s internal attribution. Mailchimp’s e-commerce events match by customer email and click cookie. Vortex IQ uses UTM source + email match. The two should agree on most orders; a small share differ on edge cases (forwarded emails, shared devices).±2 pp on individual buckets
>24h bucket extension. Mailchimp’s reported revenue caps at 24h; this card extends to >24h via UTM. The >24h bucket is unique to this card and not in any Mailchimp report.None on Mailchimp side; this is the value-add of the card
Customer Journey exclusion. This card is regular + A/B campaigns only. Mailchimp’s UI doesn’t offer a clean way to filter the same way.None when scoped correctly
Page caps. Top-10 limit means newer or smaller campaigns may not appear; the lag distribution is biased toward big winners.Distribution skewed toward tentpole campaigns
Cross-connector reconciliation (this is the central purpose):
CardExpected relationshipWhat causes legitimate divergence
shopify.total_revenueLong-tail (>24h) orders sit in Shopify’s total but not in Mailchimp’s attributed revenue. Lag distribution surfaces the under-attributed share.None; this is the gap-quantification.
shopify.time_to_purchaseShopify’s overall time-to-purchase distribution should be similar shape to Mailchimp campaigns’. If Mailchimp’s lag is much shorter, sends are well-targeted; much longer, sends drive awareness only.Different windows; Shopify includes non-Mailchimp purchases.
ga4.ga_revenue_trendGA4’s email channel attribution sees the full journey; comparing GA4 email revenue against Mailchimp’s attributed revenue surfaces the long-tail under-attribution.UTM hygiene matters.
klaviyo.klv_xc_send_to_purchase_lagWhen both ESPs run, Klaviyo’s 5-day attribution window catches more of the long tail; expect Klaviyo’s >24h bucket to be smaller than Mailchimp’s because Klaviyo has already credited those orders to itself.Different attribution windows, different exposure to the same tail.

Known limitations / merchant FAQs

What does a “good” lag distribution look like? For promotional / tentpole campaigns: 60-80% of orders within 4 hours of send. For awareness / brand campaigns: a flatter distribution with 30-50% in the >24h bucket is normal and acceptable. Don’t apply promotional benchmarks to brand sends and vice versa. Why is so much of my newsletter revenue in the >24h bucket? Newsletters typically build awareness rather than drive immediate purchase. Customers read the content, get a positive impression, and return organically days later when they need the product. Mailchimp’s 24h click attribution doesn’t credit these orders. The >24h bucket is the under-credited revenue, real but invisible to Mailchimp’s reports. How can I tighten the lag on a campaign? Three levers: (1) add concrete urgency (deadline, low stock, “ends Sunday”); (2) use product-led subject lines with specific items rather than abstract themes; (3) send at peak inbox-check times (Tuesday-Thursday 10am or 7pm UK) so opens happen close to send. Tightening lag from 12-24h to <4h typically lifts attributed revenue 30-50% because more orders fall inside the 24h attribution window. My lag is bimodal, a peak <1h AND a peak at 24-48h. What’s that? Two-segment audience. The <1h peak is your high-intent loyal subscribers. The 24-48h peak is recipients who waited for end-of-day or weekend before buying. This is healthy and reflects two genuinely different customer populations. Don’t try to flatten it; segment instead. Why would I want a long lag? For high-AOV / considered purchases (furniture, electronics, B2B subscriptions). Customers research over days. A long lag means your email seeded the consideration phase. The trade-off: long lag means most revenue falls outside Mailchimp’s 24h window and isn’t attributed back, so you’ll under-report email’s contribution. Use Email Share of Total Revenue for the honest measure. Does this card include orders from forwarded emails? Yes if the forwarded recipient still has the UTM parameters intact when they click. Most webmail clients preserve UTM on forward; some Outlook variants strip them. Forwarded clicks may show a longer lag because the forwarder typically sends 1-2 days after receiving. Why is the today value volatile? The lag distribution is computed across the top 10 campaigns over 90D, so daily readings only shift if a new campaign enters the top-10 ranking. For most accounts the distribution stabilises after the first 14 days and moves slowly thereafter. My lag distribution shifted dramatically month-over-month, what happened? Most likely you changed your campaign mix. Adding more promotional / discount campaigns tightens lag; adding more newsletter / brand campaigns lengthens it. Cross-check with Top Campaigns by Revenue, if the top-10 changed substantially, the distribution change is structural. Does the long tail >24h work for Customer Journey emails? Customer Journey emails have a different lag pattern because they trigger on behaviour. Abandoned-cart emails go out 1h after cart creation, so lag from send to purchase is naturally tight (<4h for 70%+). This card excludes Customer Journey emails for that reason; their lag distribution would distort the campaign-level comparison. Should I optimise for the <1h bucket? For promotional sends, yes. For everything else, no. The right metric is total revenue from the campaign, not lag. A campaign with 30% <1h and 40% 4-24h drives more revenue than one with 80% <1h on a small spike, because the longer-engaging audience spends more total. Use lag as a diagnostic for campaign type-fit, not as a target.

Tracked live in Vortex IQ Nerve Centre

Top Sends → Purchase Lag 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.