Email Deliverability
See how your domain is landing with each email provider, understand Yaplet's automatic per-provider warmup, and learn what to do when bounce or complaint rates climb.
Overview
Deliverability is whether your emails actually reach the inbox — not the spam folder, and not a hard rejection at the door. Yaplet manages this for you automatically, and the Deliverability tab on each sending domain shows exactly how you're doing with every major email provider.
How Yaplet protects your sending reputation
Every inbox provider (Gmail, Apple/iCloud, Microsoft/Outlook, and the rest) decides whether to trust your domain based on how recipients react to your mail. Too many bounces (mail to dead addresses) or complaints (people hitting "report spam") and the provider starts routing you to the spam folder — or the underlying sending account gets placed under review.
Yaplet runs a closed loop to keep you on the right side of that line:
- Per-provider warmup. Each provider gets its own sending limit that grows gradually as you send clean, engaged mail — so a new domain ramps up safely instead of blasting from day one.
- Automatic pullback. If bounces or complaints climb at a provider, Yaplet stops increasing that provider's limit — and past a higher threshold, actively reduces it — until the numbers recover.
- Engaged-first sending. Within every send, your most engaged subscribers go first, so the strongest signals reach providers earliest.
- Gmail spam reports. Gmail is the one major provider that never reports individual spam complaints back to senders. Yaplet closes that blind spot by reading your domain's spam data straight from Google, and when Gmail readers start reporting your mail it slows Gmail sending and holds back mail to inactive contacts — see Gmail spam reports below.
The Deliverability tab
Go to Settings → Connections → Emailing → Custom Domains, open a verified domain's card (Manage), and open its Deliverability tab. Under Deliverability health you'll see an overall health header, your current sending capacity (emails per day), how much you've sent in the last 7 days, and a per-provider breakdown.
The health score and bands
Each provider — and your domain overall — gets a 0–100 score and a health band. The band is what matters; the score is a finer reading within the band.
| Band | What it means |
|---|---|
| Healthy | Bounce and complaint rates are well within safe limits. Sending speed is increasing gradually. |
| At risk | One or more providers show elevated rates. Growth is paused to protect your reputation. |
| Critical | Rates have crossed the danger line. Sending speed is actively being reduced. |
| Not enough data | Too little recent volume to judge — keep sending. |
Per-provider breakdown
Because providers behave differently, deliverability is tracked separately for each one. The table groups your sends into Gmail, Apple, Outlook / Microsoft, and Other providers, and shows for each: the Health (score and band), Sent (7d), Address does not exist (the bounce rate — mail to addresses that don't exist, the only bounces that count against you), Mailbox full or temporary (how many emails bounced because a mailbox was full or a server was briefly unavailable — these don't lower the score), Complaint rate, Click rate, and the current per-provider Daily limit. A provider that's at risk or critical is called out inline, so you can see exactly which inbox is dragging your reputation down.
Gmail spam reports (Google Postmaster)
Most providers tell Yaplet — anonymously — every time a recipient marks your mail as spam, and those complaints feed the health bands above. Gmail doesn't. To protect its users' privacy, Gmail never reports individual complaints, which normally leaves senders guessing at the one provider that usually matters most. Yaplet closes this gap with Google's own reporting service (Postmaster Tools).
Unlock it with one DNS record. Your domain's records list includes an optional Google Postmaster row with a google-site-verification TXT record. Until it's added, the Deliverability tab shows an "Unlock Gmail spam-rate monitoring" note. Add the record and Yaplet verifies it with Google automatically — no account or extra setup on your side.
Reports, not percentages
Google shares only a percentage: the share of the Gmail readers it measured that day who marked your mail as spam. For most senders that is a small group — if Google measured about 90 readers, a single "Report spam" click already reads as 1.1%, almost four times Google's 0.3% danger line. So Yaplet turns the percentage back into the number behind it — "about 1 report among ~90 readers" — and bases every decision on how many reports there were over the last 7 days, not on one alarming-looking day. Google publishes no counts, so the number is always an estimate.
The Gmail card
Once Google has verified your domain, the Deliverability tab shows a Gmail card above the provider table:
- Status line — Gmail: normal, Gmail: warning since {date}, Gmail: slowed to {limit}/day or Gmail: recovering. During a warning it adds that growth is paused and nothing is held; during a slowdown it also shows how many campaign and automation emails are on hold and the day the hold should lift if no new reports arrive.
- Last 28 days — one square per day, colored by reports: none, 1 report, 2 or more, or no data yet. Hover a day for the estimate and Google's percentage. Google's data arrives 2–4 days late, so the newest days stay gray for a while.
- Likely sources — for the worst recent day, the campaigns and automations that sent most of that day's Gmail mail, with their priority, their share of the day's Gmail mail, and how much of it went to people who never open. Start there.
- On hold — what is waiting right now, and after the last slowdown how many held emails were released and how many old automation emails were dropped.
- Google's sender checklist — SPF & DKIM, DMARC alignment, DMARC policy, Encryption, Spam rate, DNS records, One-click unsubscribe and Honors unsubscribe, each with a check mark, needs work and a one-line fix, or no data yet, plus Google's overall verdict on the domain.
How Yaplet reacts
Every morning Yaplet reads Google's newest data and looks at the last 7 days together:
| Level | When | What happens |
|---|---|---|
| Normal | No reports worth acting on in the last 7 days | Nothing changes — a single report is noise. The card says Gmail: normal. |
| Warning | Reports are starting to add up over 7 days, or Google rates your spam rate needs work | The Gmail daily limit stops growing. Nothing is held and no email is sent. Google's rating alone can raise a domain to Warning, never higher. |
| Slowed | Reports and the spam rate reach a level that puts your Gmail delivery at risk | Gmail mail to inactive contacts goes on hold, and the Gmail daily limit is cut and stops growing — cut again on each later day with more reports at that level. |
| Severe | Many reports at a high spam rate | As Slowed, and the Gmail daily limit drops to the minimum. |
The highest level that fits applies. Other providers are never affected — only Gmail sending changes.
Who is held back
During a slowdown, only Gmail mail from Low and Normal priority campaigns and automations to inactive contacts waits. Inactive means the same as the subscriber filters' Gone quiet and Never engaged: no open or click in the last 90 days, or never opened or clicked after 5 or more emails. Everyone else keeps getting mail as usual:
- people who read your mail, and new subscribers (fewer than 5 emails received);
- campaigns and automations set to High priority — use High for cart, order and welcome emails (campaign priority, automation priority);
- confirmation emails.
Changing who gets your mail is what brings Google's ratio back down: readers rarely report you — people who never open are the ones who do.
When the hold lifts
There is no minimum length. The hold lifts on the first morning Google's last 7 days no longer reach the Slowed level. If no new reports arrive, that is about 8 days after the newest day with spam reports — the date the card shows — or sooner when older reports drop out of the 7 days first. Then:
- held campaign emails go out, most engaged first, within your normal limits — a paused campaign stays paused, and a campaign with a daily cap keeps its cap;
- held automation emails go out if they are at most 7 days old; older ones are dropped, because a weeks-old reminder would look careless;
- once Google's last 7 days are back at the Normal level and Google no longer rates your spam rate needs work, the Gmail daily limit grows back by 20% a day. If the level only falls to Warning, the hold lifts but the limit stays where it is until then.
Switching a campaign or automation to High during a slowdown releases what it already has on hold, at the latest the next morning.
The emails you get
The workspace owner gets one plain email in the morning when Gmail sending is slowed or cut to the minimum, one on each later day the limit is cut again, and one when the hold lifts; each also shows up as a notification in the app. Each says what happened, what Yaplet did automatically, what happens next and what you can do. The Warning level sends no email — it only shows on the card.
What to do at each band
When Yaplet pauses or slows a domain
The health bands above are a 7-day rolling read, so they move gradually. On top of them, Yaplet runs a real-time safety breaker that reacts within hours, so one bad send can't quietly wreck your reputation before the weekly average catches up. It watches three signals:
- Bounces — mail sent to addresses that don't exist.
- Spam complaints — recipients hitting "report spam".
- Refusals — a receiving provider rejecting your messages outright, without ever looking at the mailbox.
When it acts, a banner appears on the Deliverability panel and you get both an email and an in-app notification, naming which of the three triggered it and the numbers behind it.
When a provider refuses your mail
A refusal is not the same thing as a bounce, and it needs the opposite response. A bounce means one address is dead. A refusal means the provider — most often Microsoft/Outlook — has decided not to accept mail from your domain at all, so it rejects the message at the door without ever checking whether the mailbox exists. It's a judgment about your domain, not a fact about the address.
Yaplet slows a domain once too many of its recent sends are being refused, and pauses it if that share climbs much higher. Everyday background refusals — a handful of corporate mail servers that reject bulk mail on principle — sit far below that, and the check only engages once the domain has real volume behind it, so a few refusals on a small send trigger nothing.
Where else deliverability shows up
The same health signal appears throughout the Newsletter section so you never have to go looking for it:
- Campaign stats — each campaign report shows a Deliverability score for that send.
- Campaign lists — in the Sent column of each campaign row, a Deliverability badge appears only on a campaign whose bounce rate ran high, so the one row that needs attention stands out. Complaints are on the campaign's report page.
Link tracking and engaged-first sending
Engaged-first ordering ranks recipients by opens and clicks. If you haven't turned on branded link tracking, clicks can't be measured for that domain, so ranking falls back to opens only. Turning link tracking on gives the system a second engagement signal and sharpens who gets sent first.
Need more isolation?
Yaplet sends all customer email from a shared, pre-warmed IP pool by default — the right choice for almost everyone. If you send at high, consistent volume and want a sending reputation that's entirely your own, you can move your domain onto a dedicated IP.