Omnichannel Email Marketing: Integrating Email With Your Stack
Where email fits alongside SMS, push and retargeting, and how to stop the same person getting the same message four times.
On this page
The short version
- Channels need assigned roles. Without them, the same message goes out everywhere and the reader experiences it as repetition rather than reinforcement.
- Set a frequency budget per person across all channels, not per channel. Four touches feels like four regardless of how they were split.
- Suppression has to work across channels or a customer will be sold something by SMS an hour after buying it.
Coordination problems in multi-channel marketing rarely look like coordination problems from the inside. Each channel is doing something reasonable. The email team sends a promotion, the SMS tool sends a reminder, the ad platform retargets, and the customer receives four versions of one message in a day and concludes that you are hounding them.
Fixing it needs three things: a role per channel, a shared frequency budget, and suppression that actually crosses tool boundaries.
Roles, not duplication
The test for whether a channel has a role is whether there is a message you would send there and nowhere else. If everything that goes to SMS is a shortened version of an email, SMS has no role — it is a second delivery mechanism for the same content, and the reader pays for it in attention.
Email's structural advantage is that it persists. A message someone may want to find again in three weeks belongs in email. SMS has the opposite property: high immediacy, low tolerance for volume, effectively no archive. Sending a detailed guide by SMS wastes the channel; sending a two-hour delivery window by email wastes the message.
One frequency budget per person
Set a maximum number of commercial touches per person per week across every channel, and enforce it centrally. The number itself matters less than the fact that it exists — most organisations have never set one, which means their effective limit is the sum of what every team independently considered reasonable.
Enforcement is the hard part, because it requires channels to check something before sending rather than after. In practice most teams achieve it with a shared suppression window: anyone who received a commercial message in the last N hours is excluded from the next one, whichever channel it comes from.
The collisions worth engineering against
| Collision | What the customer sees | Fix |
|---|---|---|
| Post-purchase promotion | An ad for the thing they just bought | Purchase event suppresses across all channels immediately |
| Duplicate reminder | Email and SMS, minutes apart | One channel owns each reminder, decided per flow |
| Stale retargeting | Ads for a completed action | Conversion writes to the ad audience within the hour |
| Unsubscribe leak | Opted out of email, still texted | One preference record, honoured by every tool |
| Re-engagement overlap | Win-back email plus win-back push | Engagement tier is shared, not per channel |
The unsubscribe leak is the one with legal consequences as well as reputational ones, and it is the most common, because preference data usually lives in whichever tool collected it.
Where to start if none of this exists
Start with suppression, because it prevents the failures that actively cost you customers. One shared record of who has bought, who has opted out and who was contacted most recently, readable by every tool that sends anything.
Roles come second and are a decision rather than a build. The frequency budget comes last, because enforcing it requires the suppression layer to exist first.
Frequently asked questions
Do we need a customer data platform for this?
Not initially. Most of the value comes from a shared suppression list and agreed channel roles, both of which can run on your existing stack. A platform becomes worth it when the number of tools makes manual synchronisation unreliable.
What is a reasonable weekly touch limit?
There is no universal figure — it depends on what you sell and how often people buy. Set one from your own complaint and unsubscribe data, then hold it, because the value is in the constraint existing rather than in its exact level.
Should the same creative run across channels?
The same offer, yes. The same creative, no — a message written for email reads as padded in SMS and a message written for SMS reads as abrupt in email.