Your welcome email is scheduled for this afternoon. So is an abandoned-cart reminder. Meanwhile, your SMS platform is about to send a sale announcement. Each message makes sense on its own, but to your customer, they may feel like one store asking for attention three times in a day.
Frequency caps help you prevent that overlap. A frequency cap is a rule that limits how many marketing messages a person can receive within a defined period. For ecommerce email and SMS automations, the useful approach is to set limits across campaigns and flows, decide which messages take priority, and specify what happens when a message is held back. Here’s how to build a policy that protects the customer experience without unnecessarily blocking timely messages.
What should an ecommerce frequency cap cover?
Start with a person-level marketing cap, not a separate limit for every automation. If your welcome flow, browse-abandonment flow, cart flow, and promotional campaigns each have their own cap but do not share a contact history, the same customer can still receive too many messages.
Your policy should answer four questions:
- Which messages count? Include promotional campaigns and marketing automations that compete for attention.
- Which channels count? Set email and SMS limits individually, then add a combined limit if your systems can coordinate them.
- What is the time window? Define whether a “day” means a rolling 24 hours or a calendar day in the recipient’s time zone.
- What happens at the limit? Decide whether a message is delayed, skipped, or replaced by a higher-priority message.
Keep essential order and service communications distinct from marketing. An order confirmation or delivery update should not be blocked simply because the customer received a sale email. Equally, calling a promotional message “transactional” does not make it one. Classify messages by their purpose and follow the consent and messaging rules that apply to your business and recipients.
Set separate email, SMS, and combined limits
Email and SMS do not demand attention in the same way. An SMS arrives more directly, so many stores choose a tighter SMS limit than email. There is no universal number that fits every catalog, buying cycle, or customer preference; use a conservative starting point and adjust based on your results.
For example, an initial policy might look like this:
| Rule | Illustrative starting point | Purpose |
|---|---|---|
| Email marketing | No more than one message in a rolling 24 hours and three in seven days | Prevents campaigns and flows from stacking up |
| SMS marketing | No more than one message in seven days | Reserves a more intrusive channel for messages worth sending |
| Combined marketing | No more than two messages across email and SMS in a rolling 48 hours | Catches cross-channel overlap |
These are examples, not benchmarks or legal limits. A store with a short seasonal sale may need a different approach from one selling products customers purchase a few times a year. Whatever numbers you choose, document them so everyone planning campaigns and automations works from the same rules.
Use rolling windows when possible
A calendar-day cap can allow an email at 11:50 p.m. and another shortly after midnight. A rolling 24-hour limit prevents that particular burst. If your platform only supports calendar-day rules, check its time-zone settings and add minimum spacing between sends where possible.
Decide which automation wins when messages collide
A cap tells your system when to stop; a priority order tells it what to send instead. Without priorities, a low-value promotion might use the last available slot just before a useful cart reminder becomes eligible.
One possible priority order for marketing messages is:
- Time-sensitive, behavior-based messages: An abandoned-cart reminder while the shopper’s interest is still recent.
- Onboarding messages: A welcome email that delivers a promised offer or helps a new subscriber understand your store.
- Relevant follow-ups: Browse-abandonment or post-purchase recommendations, where permitted and appropriate.
- Broad campaigns: General sales announcements and newsletters.
That order is a starting point, not a rule for every store. A promised welcome discount may matter more than a browse reminder. A post-purchase cross-sell should not outrank a helpful order-related update. The important step is to make the decision deliberately.
Consider a shopper who opts in at noon, adds an item to their cart at 2 p.m., and qualifies for a promotional email at 4 p.m. You might send the welcome email immediately, hold the cart email until the next eligible slot, and suppress the broad promotion. If the shopper purchases before the cart email sends, cancel the reminder rather than releasing a stale message.
Build your frequency-cap workflow step by step
1. Inventory every message a customer can receive
List campaigns, welcome sequences, cart and browse reminders, win-back flows, post-purchase marketing, SMS promotions, and service notifications. Record the trigger, channel, typical send delay, intended audience, and whether the message is marketing or operational. This often reveals overlap before you change a single setting.
2. Check consent and preferences before applying caps
Frequency caps do not replace permission. Check that each recipient is eligible for the specific channel and message type, and honor opt-outs and stated preferences. SMS rules vary by jurisdiction and can include requirements beyond those for email. If you market internationally, review the applicable requirements rather than relying on one global policy.
3. Add shared suppression rules
Where your tools allow it, evaluate recent sends across campaigns and automations just before each marketing message goes out. Suppress messages after a purchase when their purpose no longer applies, and pause competing promotions while a higher-priority flow is active.
If email and SMS run in separate platforms that cannot share send history, a “combined cap” will not enforce itself. In that case, coordinate campaign calendars, use available audience exclusions, and avoid scheduling both channels to target the same segment at once. Review what your platforms actually count: some rules apply only to campaigns, while others include automated flows.
4. Choose delay or skip for each message
Delaying a welcome email by a few hours may still be useful. Sending a cart reminder days after the item was purchased is not. Give time-sensitive messages an expiration point and recheck eligibility before a delayed send. For broad promotions, skipping the message is often better than creating a backlog that reaches customers after the offer has lost relevance.
5. Test the customer journey
Create test profiles that enter several flows on the same day. Check what happens when a customer subscribes, browses, starts checkout, purchases, and opts out. Confirm both the messages they receive and the ones they do not. Test near midnight and across time zones if those cases affect your store.
Measure whether your caps are working
Do not judge a frequency policy only by how many messages it prevents. Track sends per person, the share of messages delayed or suppressed, unsubscribes and SMS opt-outs, complaints, and revenue attributed to each flow. Look at these measures together: a lower send volume is useful only if the messages that remain are relevant and the business outcome holds up.
Review results by customer group, too. New subscribers, recent purchasers, and long-inactive customers may respond differently to the same cadence. If a valuable automation is frequently suppressed by broad campaigns, adjust campaign scheduling or priorities before raising your overall cap.
Common frequency-capping mistakes to avoid
- Capping each flow in isolation: A limit on cart emails does not stop a welcome email and an SMS promotion arriving alongside them.
- Exempting every automation: Automated does not mean exempt from the customer’s attention limit.
- Letting delayed messages pile up: Recheck relevance, consent, and purchase status before sending anything from a queue.
- Using one limit for every subscriber: Start with a clear default, then consider preferences and engagement where your data supports a different cadence.
- Ignoring the customer’s local time: Frequency and quiet-hour settings solve different problems; review both, particularly for SMS.
Make every available message slot count
A good frequency cap is not simply a brake on your marketing. It is a way to choose the most useful message for a customer at a particular moment. Start by mapping your flows, set conservative channel and combined limits, establish priorities, and test what happens when triggers overlap. Then refine the policy using customer response rather than sending more by default.
If you are not ready to change your automations today, take one practical first step: review a week of your email and SMS sends from the perspective of a single customer. Any day that feels crowded is a good place to introduce a cap or a suppression rule.
Veelgestelde vragen
Should transactional emails count toward a marketing frequency cap?
Usually, essential order and service messages should remain deliverable regardless of marketing caps. Keep them clearly separated from promotions, and check the rules that apply to how you classify and send each message.
Should an abandoned-cart email override an SMS campaign?
It depends on timing, consent, and the value of each message. If the cart reminder is timely and the SMS is a broad promotion, prioritizing the cart reminder may make sense. Write that priority into your workflow so the choice is consistent.
What if my email and SMS platforms cannot share frequency data?
Use the controls you do have: separate channel limits, audience exclusions, a coordinated send calendar, and manual checks before major campaigns. Do not assume you have a working cross-channel cap unless both platforms can account for the same customer’s sends.
How often should I review my frequency caps?
Review them after major changes to your campaign schedule, automation flows, or SMS program, and during regular performance reviews. Pay particular attention to suppressed-message rates, opt-outs, complaints, and whether high-priority messages are being blocked.