What deliverability means
Deliverability is whether your emails actually reach the inbox — not the spam folder, and not bounced at the door. Yaplet manages most of it for you, and the Deliverability tab on each sending domain shows exactly how you're doing with every major email provider.
Yaplet manages warmup for you
Inbox providers (Gmail, Apple, Microsoft, and others) decide whether to trust your domain based on how people react to your mail. Too many bounces or spam complaints and they start routing you to spam. To keep you on the right side of that line, Yaplet:
- Warms up your domain automatically — it raises your sending speed gradually, and separately for each provider, as long as you stay clean.
- Pulls back on its own — if bounces or complaints climb at a provider, it stops speeding up, and slows down if they get worse, until things recover.
- Sends your most engaged subscribers first — so the strongest signals reach providers earliest.
- Watches Gmail through Google's own reporting — Gmail never reports spam complaints to senders directly, so Yaplet reads your Gmail spam data straight from Google once you add one optional DNS record, and slows Gmail sending on its own when real problems show up (see below).
There's nothing to configure: no daily limits, no warmup schedule. Your only job is to keep your list clean — the Deliverability tab tells you when something's off.
The Deliverability tab
Go to Settings → Organization settings → Emailing → Custom Domains, pick a verified domain, and open the Deliverability tab. You'll see an overall health score, your current sending capacity (emails per day), and a breakdown for each provider.
Health bands
Each provider — and your domain overall — gets a 0–100 score and a band. The band is what matters:
| Band | What it means | When |
|---|---|---|
| Healthy | Within safe limits — sending speed is increasing. | Bounce under 2% and complaints under 0.1% |
| At risk | Growth is paused to protect your reputation. | Bounce 2% or more, or complaints 0.1% or more |
| Critical | Sending speed is being reduced. | Bounce 5% or more, or complaints 0.3% or more |
| Not enough data | Keep sending to build a signal. | Fewer than 50 delivered in the last 7 days |
Scores reflect the last 7 days of bounces and complaints. A brand-new domain shows "Not enough data" until it has sent enough.
A rate only moves the band once there are at least 5 bounces or 5 spam complaints behind it — a couple of events on a small provider is noise, not a trend, so it is scored as clean.
Per-provider breakdown
Because providers behave differently, your sends are tracked separately for Gmail, Apple, Outlook / Microsoft, and Other providers — each with its own score, sent count, Address does not exist (the share of mail sent to addresses that don't exist — the only bounces that count against you), Mailbox full or temporary (the number of temporary bounces, such as full mailboxes, which don't hurt your score), complaint rate (with the number of complaints in brackets), click rate, and daily limit. Whichever inbox is dragging your reputation down is called out, so you know where to focus.
Gmail spam-rate monitoring
Most providers tell Yaplet — anonymously — when 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 would normally leave you blind at the provider that usually matters most. Yaplet closes this gap with Google's own reporting service:
- Unlock it with one DNS record. Your domain's records list includes an optional
google-site-verificationTXT record. Until it's added, the Deliverability tab shows an "Unlock Gmail spam-rate monitoring" note. Add it and Yaplet verifies it with Google automatically — no Google account needed on your side. - Reports, not just a percentage. Google only shares the share of your Gmail readers who marked your mail as spam. For a small sender that is misleading: if Google counted about 90 readers that day, a single "Report spam" click already shows as 1.1% — while Google's danger line is 0.3%. So Yaplet turns the percentage back into something you can picture, like about 2 reports among ~90 readers. Google publishes no counts, so these numbers are always estimates.
Google reports with a 2–4 day delay, and only for days with meaningful Gmail volume (roughly 50+ Gmail recipients in a day). If your domain shows no Gmail data yet, that's normal at low volume — not an error.
The Gmail card
Once Google has verified your domain's record, the Deliverability tab shows a Gmail card with:
- A status line — Gmail: normal, Gmail: warning, Gmail: slowed (with the current daily limit) or Gmail: recovering.
- The last 28 days — one square per day, colored by reports: no reports, 1 report, 2 or more, or no data. Hover a day to see its numbers. The newest days stay gray for a while because Google's data arrives late.
- Likely sources of a bad day — the campaigns and automations that sent most of that day's Gmail mail, with how much of it went to people who never open your emails.
- What's on hold — how many campaign and automation emails are waiting, and after a slowdown, how many were sent and how many were dropped.
- Google's sender checklist — SPF & DKIM, DMARC alignment, DMARC policy, encryption, spam rate, DNS records, one-click unsubscribe and honoring unsubscribes, each with a short fix when it needs work — plus Google's overall verdict on your domain.
How Yaplet reacts
Every morning Yaplet reads Google's last 7 days for your domain and sets a level — the highest one that fits applies. Only Gmail is affected; other providers keep their own limits.
| Level | When | What happens |
|---|---|---|
| Normal | At most 1 report in the last 7 days | Nothing — a single report is only shown on the card. |
| Warning | 2 or more reports in the last 7 days, or Google rates your spam rate "needs work" | Your Gmail limit stops growing. Nothing is held, and no email is sent. |
| Slowed | 3 or more reports and at least 0.3% over the last 7 days, or one day at 1% or more with 3 or more reports | Gmail emails to inactive contacts from Low and Normal priority campaigns and automations are put on hold, and your Gmail daily limit is halved — and halved again on each later day with 3 or more reports. People who read your emails and new subscribers keep getting everything. |
| Severe | 5 or more reports at 1% or more | As Slowed, and your Gmail limit drops to the minimum of 150 emails a day. |
An inactive contact hasn't opened or clicked anything in the last 90 days, or has never opened or clicked after receiving 5 or more emails. New subscribers (fewer than 5 emails) never count as inactive, so welcome emails keep flowing. Emails from High priority campaigns and automations, and confirmation emails, are never held. You set the priority on each campaign and automation.
When the hold lifts
The hold lifts as soon as Google's last 7 days no longer reach the Slowed level — in practice about a week to 10 days after the last bad day, because Google's data arrives late. The card shows the expected day: the hold lifts about [date] if no new spam reports arrive. Then:
- Held campaign emails are sent, most engaged readers first, within your normal limits.
- Held automation emails are sent too — except those older than 7 days, which are dropped, because a weeks-old reminder would look careless.
- Once Google's last 7 days show no more than 1 report, your Gmail limit grows back by up to 20% a day (the card shows Gmail: recovering).
Emails you'll get
The workspace owner gets an email in the morning (around 07:15 UTC) when Gmail sending is slowed down, another on each later day the limit is cut again, and one when the hold lifts. Each one 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 you can do
- Look at the likely sources of the bad day, and stop sending those campaigns or automations to people who never open.
- Set cart, order and welcome automations to High priority, so they're never held.
- Check Google's checklist and fix any item marked needs work.
What to do at each band
| Band | What to do |
|---|---|
| Healthy | Keep emailing only people who opted in, and remove old or unengaged addresses before they hurt you. |
| At risk | Clean your list now — remove old, invalid, or never-opening addresses, and stop emailing unengaged contacts. If rates keep rising, speed drops. |
| Critical | Stop importing unverified lists, remove bouncing and complaining contacts immediately, and send only to your most active subscribers until the numbers recover. |
When Yaplet slows or pauses a domain
The bands above come from a 7-day average — a gradual read. On top of that, Yaplet runs a real-time safety breaker that reacts within hours, so one bad send can't wreck your reputation before the weekly average notices. It watches three signals: bounces (mail to addresses that don't exist), spam complaints, and refusals — a provider rejecting your messages outright without ever checking the mailbox. When it acts, you'll see a banner on the Deliverability panel and get an email and an in-app notification naming which signal caused it:
- Sending speed reduced — one of those three rates is elevated, so Yaplet temporarily slows how fast this domain sends. Normal speed returns automatically as the rate recovers.
- Sending paused — if the rate climbs to a level that risks getting the domain blocklisted, Yaplet pauses all bulk sending from it for a review. Campaigns and email automations stop, and even test emails from the domain are blocked while it's paused. Your other Yaplet email keeps working. Yaplet emails you the details and a person on our team reviews it. A paused domain does not un-pause itself: sending stays off until Yaplet clears it, even after your rates recover. Fix the underlying list problem and contact support to have the pause lifted.
A refusal is not a bounce
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 judgement about your domain, not a fact about the address. Yaplet slows a domain once 5% of its sends in the last 24 hours are being refused, and pauses it at 15%. Both need real volume behind them: at least 200 emails sent and at least 25 refusals in that 24 hours before anything happens. Everyday background refusals — a few corporate mail servers that reject bulk mail on principle — sit far below that.
Cleaning your list will not fix a refusal — the addresses were never the problem. What helps is easing off that provider for a while: refusals normally clear on their own as your volume drops and your recent sending looks calmer. Avoid large campaigns aimed at the affected provider until the rate falls, and don't try to push through it by sending more.
This is protection, not a penalty. Bounces and complaints are almost always avoidable — only email confirmed opt-ins, and never import a purchased or stale list. Refusals are less directly in your hands, but the same habits are what stop a provider turning against your domain in the first place.
Where else you'll see it
The same health signal appears on each campaign's report and as a Deliverability badge on each campaign card in the Ongoing and Finished lists — so you can spot a bad send at a glance without opening the tab.
Keep your deliverability healthy
- Only email people who opted in.
- Never import a purchased or scraped list — it's the fastest way into the Critical band.
- Let Yaplet remove bounced and complained contacts (it does this automatically when it can).
- Turn on link tracking so engaged-first sending can rank by clicks, not just opens.
What's next
Haven't set up a domain yet? Start with Verify your sending domain. Sending at high, consistent volume and want a reputation entirely your own? See Dedicated IP.