• Myth, examined
  • E-commerce
  • 5 min read

Myth: More Emails Mean More Revenue

The chart that proves it is the same chart that hides the cost. Here is how to see both.

Author
ftes.ai Editorial
ftes.ai Team

The short answer

More emails mean more attributed revenue in the short term, because every extra send collects credit for purchases inside the attribution window. Over the horizon that matters the belief fails, because frequency erodes the list through unsubscribes, complaints and placement. A Retention FTE enforces a hard frequency cap and uses holdouts to show the real effect.

The role this piece is aboutRetention FTE · Lifecycle & Retention Marketer

Key takeaways

  • The belief is earned: attributed revenue rises with send volume in almost every monthly report.
  • What the report hides is list erosion: unsubscribes, complaints and placement losses that compound.
  • A frequency cap is a hard limit on messages per customer per period; on ftes.ai the Retention FTE cannot exceed it.
  • Holdouts show how much of the attributed revenue was going to happen anyway.
  • You can check for yourself: plot attributed revenue against unsubscribes and complaints for the same sends.

What is the belief, and where does it come from?

The belief is that sending more email produces more revenue, so the way to grow a store's email revenue is to send more often. It comes from the monthly report. Almost every sending platform attributes revenue to the last message a customer received within a window, so a store that doubles its campaign volume sees attributed revenue rise, often sharply, in the same month. The chart goes up and to the right, and the conclusion writes itself.

The belief deserves respect because the chart is real. The question is what the chart is measuring.

What is true in the belief?

What is true is that a message sent to a customer who was going to buy in the next few days often gets credit for that purchase, and more messages catch more of those purchases inside the window. It is also true that some customers genuinely buy because they were reminded, and that a store which sends too little leaves that revenue on the table. Frequency is not free of effect; the effect is just smaller and more mixed than the attributed number says.

It is also true that some segments tolerate more messages than others, and a store that sends everyone the same volume is under-messaging some and over-messaging the rest.

What does the report hide?

The report hides the cost, which arrives on a different chart and later. Every extra send raises the chance a customer unsubscribes or marks the message as spam; unsubscribes shrink the list and complaints damage inbox placement for everyone on it, including the flows that were working. Placement losses do not show as a line in the revenue report; they show as a slow decline in the flows' results months later, usually attributed to something else.

The other thing the report hides is how much of the attributed revenue would have happened without the message. A customer who buys every month will buy this month whether or not a campaign lands in the window. The attribution model gives the campaign credit anyway.

What does a frequency cap actually do?

A frequency cap sets the maximum messages a customer can receive in a period, across flows and campaigns together, with a priority rule that decides which message wins when they collide. On ftes.ai the Retention FTE treats the cap as a hard limit above the autonomy ladder: it cannot be exceeded at any level, and a campaign that would breach it for part of a segment is held for those contacts and reported in the morning brief with the count.

The cap is also per segment where the owner wants it. Customers who buy often can tolerate more; customers who bought once may not. The Retention FTE proposes the split from engagement and order data, and the owner approves it.

Revocation — disconnect, step back, pause, from one placeWallet — hard stop; spend bounded and visibleAudit trail — who, what, when, evidence, levelGates — approval on every action; fact gate on every claimPermissions — roles check every protected actionCredentials — scoped, encrypted, never exposedIsolation — organization on every query; properties separate
Figure 1The frequency cap sits above the autonomy ladder as a hard limit; held-back sends are reported, never silently dropped.

How does a holdout settle the question?

A holdout settles the question by removing attribution from the argument. Split a segment, message one part and not the other, and compare purchases over the same horizon. The difference is what the messages caused; everything else in the attributed number was going to happen. The Retention FTE proposes holdouts on any flow or campaign cadence where the store intends to claim lift, sizes them so a real difference could be seen, and reports the holdout size beside the result.

Holdouts also answer the frequency question directly: message one group at the current cadence and another at a higher one, and compare both purchases and unsubscribes over the horizon. That is the only chart that shows both sides.

How can a store check for itself?

A store can check the belief with data it already has. Plot attributed revenue per send against unsubscribes and spam complaints per send for the same period; if the second line rises with the first, the cost is visible. Then compare the flows' revenue per recipient across the months when campaign volume rose; if it fell, placement or fatigue is showing. Finally, run one holdout on one high-volume campaign cadence and read the difference.

The remaining truth is that some stores under-send, and the same checks will show that too: low unsubscribes, flat complaints, and a holdout that shows the messages do earn their place. The point is to measure rather than to assume in either direction.

Frequently asked questions

Do more emails mean more revenue?

In the attributed report, yes, short term. Over the horizon that matters, frequency erodes the list, and holdouts show much of the credit was not caused.

What is a frequency cap?

The maximum messages per customer per period across flows and campaigns. The Retention FTE cannot exceed it at any autonomy level.

How do I see the real effect of sending more?

Run a holdout at two cadences and compare purchases and unsubscribes over the same horizon.

Can some segments take more email?

Yes. Frequent buyers often can; one-time buyers often cannot. The cap can be set per segment.

Is under-sending also a risk?

Yes, and the same checks show it: low unsubscribes and a holdout that proves the messages earn their place.

  • E-commerce
  • Retention FTE
  • Myth
  • Email Frequency
  • Attribution
Further reading

Keep going.

Related guides on hiring and managing Digital FTEs.

Ready to hire your first Digital FTE?

Pick a role, connect the tools it needs, and review its first proposals this week.