Email is a sales channel with a hidden failure mode
For most online stores, email drives a steady share of revenue: abandoned cart flows, launches, win-back campaigns and the big seasonal sends. When deliverability slips, nothing visibly breaks. The ESP still reports messages as delivered, the flows keep running, and revenue per send just drifts down. By the time someone asks why Black Friday underperformed, the cause is weeks old.
Order and shipping emails have the same exposure. If your store platform sends receipts from your domain and that domain fails DMARC or lands on a blacklist, customers miss confirmations, open support tickets and sometimes dispute charges they do not recognize.
The sending setup of a typical store
A store rarely sends from one place. Each of these sends as your domain and each needs its own SPF entry or DKIM key. Every app you install adds another sender, and each one is a new way for authentication to break without anyone noticing:
- The store platform, for order, shipping and account emails.
- A marketing ESP for campaigns and automated flows.
- A help desk for support replies.
- A reviews app asking for product reviews.
- Google Workspace or Microsoft 365 for staff mail.
What can go wrong, and how monitoring catches it
Each of these happens in real stores, usually right after a change nobody connected to email. Monitoring links the cause to the symptom in minutes.
| Problem | What customers notice | What monitoring shows |
|---|---|---|
| A new app added to SPF pushes it over 10 lookups | Random mail goes to spam | SPF permerror alert with the lookup count |
| Reviews app signs DKIM with its own domain | Review requests fail DMARC | Unaligned source in DMARC reports |
| Gmail spam rate climbs after a big campaign | Later campaigns land in spam | Spam rate alert at 0.1 percent, again at 0.3 |
| Link domain or shortener gets listed on URIBL | Campaigns with that link go to spam | Listing alert with removal steps |
| DMARC record lost in a DNS migration | Spoofing becomes possible, Gmail and Yahoo rules unmet | Missing record alert |
Run a free check on your own domain or IP, then keep it monitored.
Check NowThe spam rate threshold that matters most
Since February 2024, Google and Yahoo require bulk senders to keep the user-reported spam rate below 0.3 percent, and Google recommends staying below 0.1 percent. Stores cross that line most often during peak season, when lists that were quiet all year suddenly get daily emails. Connect Google Postmaster Tools on the Business plan and you get an alert at 0.1 percent, early enough to slow down, tighten segments to engaged buyers and recover before the 0.3 percent mark.
The same rules require SPF, DKIM, a DMARC record aligned with your From domain, and one-click unsubscribe on marketing mail. You can confirm the DNS part any time with the free DMARC checker and SPF checker, and read the full list in our bulk sender requirements checklist.
A peak season routine
- 1 Six weeks before peak, check your Domain Health score and fix every open finding.
- 2 Review DMARC reports for unaligned apps and fix their DKIM setup.
- 3 Run an inbox placement test on your main campaign template at Gmail, Outlook and Yahoo.
- 4 Ramp volume to less engaged segments gradually, not all on the first day of the sale.
- 5 During the sale, keep spam rate and blacklist alerts on in Slack, and run a placement test before each big send.
Which plan suits a store
A single brand with one or two domains usually fits Business at $149 a month, or $74 billed yearly. It adds the pieces stores need most: Google, Microsoft and Yahoo reputation signals, spam rate alerts, sender source discovery in DMARC reports up to 1,000,000 messages a month, and 50 inbox placement tests a month. Starter at $49 ($24 yearly) covers blacklist and DNS monitoring for smaller shops. Groups running many brands, or agencies managing stores for clients, look at Agency.
All checks are DNS only, so nothing is ever sent from your domain by us. The wider picture of signals is described on our email deliverability monitoring page.
Frequently asked questions
Why are my order confirmation emails going to spam?
Usually because the platform sending them is not authenticated for your domain, the domain fails DMARC alignment, or it shares reputation with marketing mail that collects complaints. Check SPF, DKIM and DMARC, and consider a separate subdomain for marketing.
Should ecommerce marketing and transactional emails use different domains?
Many stores send marketing from a subdomain such as news.example.com and receipts from the main domain or another subdomain. That way a campaign that collects complaints does not drag order emails down with it.
What spam rate is too high for an online store?
Anything at or above 0.3 percent at Gmail is a problem under Google rules, and you should aim to stay below 0.1 percent.
How do I prepare email deliverability for Black Friday?
Fix authentication weeks ahead, warm up volume gradually, focus early sends on engaged buyers, test placement before big sends, and watch spam rate and blacklist alerts throughout the sale.
Do I need blacklist monitoring if my ESP manages the IPs?
Yes, for your domains. Your ESP watches its shared IPs, but domain lists such as Spamhaus DBL and URIBL judge your own domain and link domains, and only you will notice those listings. Monitoring also covers the store platform and apps that send outside your ESP.