Email marketing automation is the set of messages a system sends on your behalf when something happens: a sign-up, a purchase, an abandoned basket. Done well, it is the most reliable revenue channel most businesses own, because the list belongs to you and nobody auctions access to it. Done badly, it teaches customers to ignore you and mailbox providers to treat you as spam. This article is for business owners and marketing managers who want the first outcome. It covers welcome sequences, lifecycle triggers, frequency, the deliverability basics of SPF, DKIM and DMARC, and what to report.
What should a welcome sequence actually do?
The welcome sequence is the most-read email you will ever send, because it arrives while the person still remembers asking for it. Most businesses waste it on a single thank-you message with a logo.
A good sequence does three jobs over a few messages in the first couple of weeks. It sets expectations: what you will send, how often, and how to leave. It delivers what was promised, immediately. And it asks one question that lets you segment: which product line, which need, which language. In a bilingual market that last question is not optional. Capture the language preference at sign-up and send the whole sequence in it, rather than sending English to everyone with an Arabic paragraph at the bottom.
Which lifecycle triggers are worth building?
Triggers are messages sent because the customer did or did not do something, and they outperform broadcasts because the timing is the customer's, not yours. Build them in this order, because each is usually worth more than the next:
- Transactional and post-purchase. Confirmation, shipping, delivery, and a follow-up asking whether everything was right.
- Abandonment. A basket, a quote or an application left half-finished. One reminder is helpful; a sequence of five is a threat.
- Onboarding. Messages keyed to what the customer has and has not done yet, not to how many days have passed.
- Renewal and re-engagement. A reminder before a renewal is courtesy. A "we miss you" message after a long silence is fine once; if it gets no response, stop and remove the address.
- Reviews. Ask after the customer has had time to form an opinion, not the morning after delivery.
Every trigger needs an exit rule. If the customer buys, the abandonment sequence must stop the same minute. Nothing damages trust faster than being nagged about something you have already done.
How often is too often?
There is no universal number, and anyone who gives you one is guessing. Frequency should be set by the value of what you are sending. A weekly email with something genuinely useful in it is welcome; a daily promotion is not.
Practical guardrails:
- Cap total sends per person per week across all automations and campaigns, so a customer in three sequences does not get three emails on the same morning.
- Let people choose less instead of nothing. A preference page offering a monthly digest keeps subscribers who would otherwise leave.
- Watch unsubscribes and complaints per send, not in aggregate.
- Prune the list. Addresses that have not engaged in a long time hurt deliverability for everyone else. Send a final message and remove them.
What do SPF, DKIM and DMARC do, and do I need them?
Yes, and they are the reason otherwise good programmes end up in the spam folder. All three are records published in your domain's DNS. SPF lists which servers may send mail for your domain. DKIM adds a signature to each message so the receiving server can verify it was not altered and really came from you. DMARC tells receiving servers what to do when a message fails those checks, and sends you reports about who is sending in your name.
Without them, your messages are indistinguishable from someone impersonating you, and the large mailbox providers now treat that as grounds for rejection. Setting them up is a short task for whoever manages your domain, and it must cover every service that sends on your behalf: the CRM, the invoicing tool and the support desk, not only the marketing platform. Start DMARC in monitoring mode, read the reports, then tighten the policy once every legitimate sender is covered.
Two further habits: send marketing from a dedicated subdomain so a problem there does not affect your staff's mail, and warm up any new sending domain gradually.
What should the email report show?
Not opens. Since mailbox providers began pre-loading images and blocking trackers, open rates measure the mail client's behaviour more than the reader's. Report on revenue per send, enquiries per send, and unsubscribes and complaints per send, by automation and by campaign. For each trigger, compare the people who entered it with a group who did not, when you can hold one out. That is the number that says whether the automation is earning its place or merely running.
When we build email programmes at Codigoo, the automations are specified in English and Arabic from the start, the deliverability records are in place before the first send, and the report the owner sees is the revenue one. The goal is a channel customers are glad to be on, which is the only kind that keeps paying.