How Much Revenue Should Email and SMS Drive?
Use retention revenue share without fooling yourself: define the denominator, separate attributed from incremental revenue, compare like periods, and diagnose the system behind the number.
- Calculate retention revenue share with a stable denominator
- Separate operating targets from universal benchmarks
- Diagnose list growth, flows, and campaigns without over-crediting the channel
No prior lesson required.
What percentage of revenue should email and SMS drive?
ZHS uses 25–45% of total store revenue attributed to email and SMS combined as a directional operating range for an established DTC retention program. It is not a promise and it is not an incrementality estimate. Catalog, repeat cycle, traffic mix, promotion intensity, channel eligibility, attribution settings, and brand maturity can move the number materially.
Do not quietly turn this combined-channel range into “email alone should drive 30%.” Report email, SMS, and the combined total separately. Label all three as platform-attributed unless a holdout or other causal method supports an incremental claim.
Why do credible benchmarks disagree?
Most disagreement comes from definitions rather than performance. One report may use total Shopify revenue as the denominator; another may use online revenue, tracked revenue, or revenue from recipients who were eligible for marketing. One platform may credit an open; another may credit only clicks. The lookback window, identity matching, timezone, returns, taxes, shipping, discounts, and subscriptions can all differ.
Questions to answer before comparing revenue-share numbers
| Criteria | Definition to record | Why it changes the result |
|---|---|---|
| Numerator | Email, SMS, or combined attributed revenue | Combining channels produces a larger share than email alone |
| Denominator | Gross, net, online, or total store revenue | Returns, retail, taxes, and shipping change the base |
| Attribution | Click/open window and model | Longer or view-through windows credit more orders |
| Population | All orders or only identifiable customers | Identity resolution changes match rate |
| Period | Comparable dates and promotion mix | BFCM cannot be treated like a typical month |
| Causality | Attributed versus incremental | Dashboard credit is not proof the order required the message |
If these definitions do not match, show the figures side by side instead of averaging them into fake precision.
How do you calculate retention revenue share?
Choose one documented store-revenue denominator and use it consistently. Pull email- and SMS-attributed revenue for the same timezone and date range, reconcile major exclusions, and divide the combined attributed amount by store revenue. Also retain the channel split so combined growth cannot hide email or SMS deterioration.
Attributed retention revenue share
(email-attributed revenue + SMS-attributed revenue) ÷ total store revenue × 100- The numerator and denominator cover identical dates and timezones
- Returns, cancellations, tax, shipping, and discounts are treated consistently
- The attribution model and lookback windows are recorded
- This is labeled attributed, not incremental, revenue
Use the same saved report every period. A changing definition makes the trend unusable.
Example with visible assumptions
If a store records $2,000,000 in the selected revenue denominator, Klaviyo attributes $480,000 to email and $120,000 to SMS under the documented settings, the combined attributed share is 30%. That arithmetic does not prove the messages caused $600,000. It tells the team where the platform assigns credit and whether the operating system deserves deeper inspection.
| Input | Value |
|---|---|
| Store-revenue denominator | $2,000,000 |
| Email-attributed revenue | $480,000 |
| SMS-attributed revenue | $120,000 |
| Combined attributed retention revenue | $600,000 |
| Combined attributed share | 30% |
What should you inspect when the share is low?
A low share is a symptom, not a prescription to send more. Diagnose the system in order: measurement, eligible audience, capture, automated coverage, campaign execution, and product repeatability.
Diagnose a low retention-revenue share
Lock denominator, attribution settings, channel split, timezone, returns, and exclusions.
Audit forms, checkout capture, acquisition source, net list growth, and suppression.
Prioritize welcome, checkout, cart, browse, site, post-purchase, replenishment, and winback based on the business.
Use total attributed revenue, placed-order rate, complaints, and unsubscribes by segment.
Repurchase cycle, margin, inventory, product fit, and acquisition quality can cap the channel.
Do not prescribe higher frequency until measurement, eligibility, and customer economics are understood.
How much should automated flows contribute?
ZHS uses 30–50% of email-attributed revenue as a directional operating range for a built-out flow program. The denominator is email-attributed revenue, not total store revenue. A replenishable product with mature post-purchase journeys can differ from a low-repeat catalog.
Use the share to identify missing automation, then diagnose individual flows with eligible entries, skip reasons, delivery, click, conversion, total attributed revenue, and downstream customer behavior. No single metric should decide whether a longer flow is better.
How should campaign cadence affect the benchmark?
ZHS often operates mature programs around 12–16 campaign sends per month across segmented tracks, but cadence is an operating choice, not an industry law and not a guaranteed route to a revenue-share number. Count what each subscriber actually receives, not merely how many campaigns the calendar contains.
Scale a track only while marginal sends retain acceptable conversion and total attributed revenue without unacceptable complaints, unsubscribes, or deliverability deterioration. A high-intent cohort may support more frequency than a cool audience. Seasonal launch months may support more than routine weeks.
How do you estimate the opportunity without promising revenue?
Use scenarios, not a single “money left on the table” claim. Apply several attributed-share assumptions to the same documented denominator, then show what must be true for each scenario. Keep the result separate from an incremental forecast.
Attributed-share scenario gap
store-revenue denominator × (scenario share − current attributed share)- The scenario is directional, not guaranteed
- Attribution settings remain identical
- No claim is made that the entire gap is incremental
- Capacity, list growth, product demand, and margin can support the program
A scenario helps prioritize investigation. It is not a forecast until the underlying drivers are modeled.
What is the ZHS benchmark reporting standard?
Every benchmark report should name the numerator, denominator, population, period, attribution method, channel scope, and whether the result is attributed or incremental. If those definitions are missing, the number is context, not a decision-ready comparison.
Revenue-share reporting checklist
- Email, SMS, and combined attributed revenue are shown separately
- The store-revenue denominator is named
- Date range and timezone match
- Attribution model and lookback windows are recorded
- Returns, cancellations, taxes, shipping, and discounts are handled consistently
- Flows and campaigns are split
- Attributed and incremental language are not mixed
- The same definitions are used in every article and report
- Changes in platform settings are annotated on the trend
- Action is based on supporting metrics, not revenue share alone
The benchmark becomes useful when definitions remain stable enough to compare decisions over time.
The ZHS house view is deliberately conditional: 25–45% is a combined attributed operating range, 30–50% is flows as a share of email-attributed revenue, and neither number replaces causal measurement or customer economics.
Need help implementing this?
We build and manage complete email & SMS programs for DTC brands. Get a custom plan for your brand.
Apply Now