A strong email revenue report should still leave room for the question you need to answer: is the program earning the investment? Email-list ROI compares the incremental contribution the program produces with the cost of creating it. ROI.LIVE keeps that separate from revenue per subscriber and platform-attributed revenue. Those measures describe performance, but cannot establish how much additional profit email caused.
An email list gives you a route to an audience under the applicable permissions and platform rules. Keeping that route useful takes work and money: acquiring subscribers, creating and sending messages, then fulfilling the resulting orders. Include that work when deciding what the program earns.
Our email marketing service scope connects the campaigns, customer flows and reporting responsibilities behind that investment.
Define the measures before the report
Four measures that should not share one label
| Measure | Calculation | What it describes |
|---|---|---|
| Revenue per subscriber | Defined revenue ÷ defined subscriber count | Revenue productivity for that denominator and period |
| Platform-attributed revenue | Revenue assigned under the platform's attribution settings | Credited sales, which may overlap other influence |
| Contribution before program cost | Net revenue − relevant variable order costs | Amount available before the program costs included next |
| Incremental program ROI | (Incremental contribution − incremental program cost) ÷ incremental program cost | Return under a stated incrementality method |
Match the measure to the question before comparing reports. Revenue per recipient for one campaign differs from annual revenue per subscriber, and a list-size snapshot differs from delivered recipients. Keep the period and audience consistent so a change in the label or denominator does not become a performance story.
Use your own inputs
Program return calculator
Use a suitable incrementality estimate for incremental ROI. If the input is only platform-attributed revenue, interpret the output as an attributed model. Avoid double-counting costs.
A worked return calculation
From added revenue to program ROI
Illustrative model with a suitable estimate of incremental revenue.
Read the full explanation
This example is illustrative. A suitable experiment estimates that the email program added $20,000 of net revenue. The associated product and variable order costs total $12,000, leaving $8,000 of incremental contribution before program cost. Incremental program cost is $3,000.
The modeled net incremental contribution is $5,000. ROI is $5,000 ÷ $3,000 = 166.7%. If the $20,000 were only platform-attributed revenue without a credible incrementality estimate, the same arithmetic would describe an attributed model, not proven incremental ROI.
Estimate incrementality with an appropriate comparison
A randomized holdout can help estimate what would have happened without a message or program when it is suitable and operationally feasible. Define the audience, assignment, outcome window and intended metric before sending. Account for overlapping campaigns and follow-up purchases.
If a suitable experiment is unavailable, show attributed contribution and explain its limits. It still gives you something to inspect. An analytics dashboard does not make the result incremental: customer demand, paid traffic and other messages can all influence the same order.
Include the costs that change the conclusion
Include the costs that could change your spending decision: subscriber acquisition, software, creative work, management and relevant discounts or incentives. Count each once. Keep order costs in contribution and program costs in the chosen return model, with that boundary written into the report.
Revenue is not nearly pure margin merely because acquisition has paid back. The business still supplies the product and fulfills the order. The acquisition-cost calculator shows how much those costs can change the amount available.
Inspect customers at a comparable age
Track acquisition cohorts and their observed contribution over matching horizons. A new subscriber group has had less time to buy than an older one. The cohort guide shows how to preserve that distinction.
Email and SMS permissions are separate. Klaviyo's consent guidance explains that email permission does not automatically authorize SMS. Do not treat the same audience list as transferable consent for every channel.
Make the next decision from the evidence
If attributed revenue rises but contribution falls, inspect discounts, product mix, returns and program cost. If contribution improves but cash arrives too late, review the payback model. A useful report connects the result to a specific change in acquisition, messaging, offer or cost.
Reconcile one reporting period to the order system and actual cost record. Show which result is attributed, which is an estimate of additional impact and what remains unknown. Then use that record to assess the next decision without asking the platform's revenue number to prove more than it measured.
Questions owners ask
Is revenue per subscriber the same as ROI?
No. Revenue per subscriber divides revenue by an audience count. ROI compares return with investment under a stated cost and incrementality model.
Does platform-attributed revenue prove incremental sales?
No. It credits sales according to attribution settings. A suitable comparison is needed to estimate what would have happened without the program.
What costs belong in email ROI?
Include relevant variable order costs and program costs under an explicit boundary, including acquisition, software, creative and management where applicable. Avoid double counting.
Can email subscribers automatically receive SMS?
No. Email and SMS permissions are separate. Use the appropriate consent for each channel.
Sources and method
External claims use the sources below. Worked examples and tools are labeled in the article; they are not customer results.
- Klaviyo: consent collection: Email and SMS consent are separate.
Substantively revised September 8, 2026. Definitions, calculations, sources and internal destinations were reviewed for this edition.
