Keep Deliverability High
Deliverability is the likelihood of your emails reaching your Profiles' inboxes. You can have a large impact on your email deliverability — it's not just a technical issue, it's something you influence with every send. This article gives you the practical steps to keep your delivery rate high and your sender reputation strong.
In this article
What is email deliverability?
Email deliverability is determined by several factors on both the sender's and receiver's side — including consent, authentication, sender reputation, content quality, ISP throttling, bounces, and spam filtering.
Delivery rate is calculated by dividing the number of emails delivered by the number of emails sent. A healthy list should achieve a delivery rate around 99% — 100% is almost impossible for any list of meaningful size. A delivery rate significantly below 99% typically signals poor list quality, missing authentication, or spam-trigger content.
The journey to the inbox
When you hit "Send" in Apsis One, the email doesn't go straight to the recipient's inbox. It passes through several checkpoints — think of it like a package going through customs. At each stage, things can slow down, reroute, or even block delivery.
Step 1: Your sending platform (Apsis One)
This is where the journey starts. Apsis One sends the email from a managed IP address via your private technical sender domain. The system checks authentication (SPF, DKIM) and applies tracking parameters. When your Email Report shows "Delivered", it means the receiving server accepted the email — not that it landed in someone's inbox.
Step 2: The receiving mail server
The recipient's email provider (Microsoft 365, Google Workspace, a company's own server, etc.) accepts the email and then runs its own checks before placing it in the inbox. This is where delays most commonly happen:
What can happen | What it means |
Greylisting | The receiving server rejects the email with a temporary error code (4xx) as a spam prevention measure for unknown or first-time senders. Apsis's mail servers are configured to detect greylisting and automatically retry after 15 minutes (instead of the standard 2-hour retry interval for regular temporary bounces). |
Throttling | If the server receives a large batch of emails from one sender at once, it may respond with temporary rejection codes to slow down the flow. The emails are retried and delivered over a longer period. |
Step 3: Spam and security filters
Even after the receiving server accepts the email, it passes through spam filters, virus scanners, and reputation checks. These can add processing time, reroute the email to junk or spam, or hold it for review — all invisible to the sender. This is where your sender reputation, content quality, and authentication status determine whether the email is placed in the inbox, the promotions tab, or the spam folder.
Step 4: The inbox
Only after clearing all of the above does the email actually appear in the recipient's inbox. And even then, some email clients (especially Outlook desktop) don't always sync instantly — they fetch new mail on intervals, which can add a few more minutes of apparent delay.
💡 "Delivered" ≠ "In the inbox"
The delivery status in your Email Report tells you the receiving server accepted the email. Everything that happens after that — spam filtering, inbox placement, sync delays — is on the recipient's side and outside your direct control. What you can control is everything that affects your reputation at steps 1–3: authentication, consent quality, content, and sending patterns.
Apsis provides the sending infrastructure, IP management, and authentication protocols. What you control — consent quality, content, list hygiene, and sending patterns — determines what happens at each checkpoint along the way.
Consent management
Your audience quality is the single biggest factor in deliverability. Sending to Profiles who didn't consent, are inactive, or have invalid addresses damages your sender reputation and delivery rate.
Action | Why it matters |
Exclude inactive Profiles from sendings | Profiles who haven't opened or clicked in months drag down your engagement metrics. ISPs interpret low engagement as a sign of unwanted email. Build a Segment of inactive Profiles and exclude them from regular sends. |
Run re-engagement campaigns | Before removing inactive Profiles, try a targeted re-engagement campaign. Those who respond stay on your list; those who don't should be cleaned out. |
Analyse bounce rates and spam complaints | High bounce rates signal poor list quality. Spam complaints tell ISPs your email is unwanted. Monitor both in your Email Report and act quickly. |
Ensure imported addresses are real and consented | When importing addresses, verify they are real, actively used, and have provided consent. Don't import purchased or third-party lists — these almost always contain invalid addresses and spam traps. |
Never import third-party lists | Do not import files with addresses or information provided by a third party. These lists violate consent requirements and will damage your sender reputation. |
Enable double opt-in | Double opt-in requires new subscribers to confirm their email address by clicking a link in a confirmation email. This prevents spambot signups, typos, and fake addresses from entering your list — all of which would lead to bounces and damage your reputation. |
Bounces, spam complaints, and unsubscribes
Your Email Report contains three metrics that directly signal to ISPs whether you're a trustworthy sender. Ignoring them — or letting them creep up — is the fastest way to damage your deliverability.
Bounces
A bounce means the receiving server rejected the email. Bounces fall into three categories:
Type | What it means | What happens in Apsis One |
Soft bounce | A temporary issue — full inbox, server temporarily busy, message too large. | The system retries every hour for up to 48 hours after the initial send time. |
Hard bounce | A permanent failure — the email address doesn't exist, the domain doesn't exist, or the account is closed. | After 3 hard bounces for the same Profile, Apsis One stops sending to that address altogether. If the third hard bounce happened in a previous sending, the Profile is excluded from future sends automatically. |
Technical bounce | The receiving server rejected the email due to a technical error — network issue, SPF/DKIM/DMARC authentication failure. | Check your authentication setup. Technical bounces may indicate a DMARC configuration problem. See Email Authentication – Safe Sending. |
Why it matters for deliverability: A high bounce rate tells ISPs your list is poorly maintained. Repeated sends to invalid addresses look like spammer behaviour. Keep your bounce rate as close to 0% as possible by maintaining clean, consented lists.
Spam complaints
A spam complaint is recorded when a recipient clicks "Report spam" or "This is spam" in their email client. The complaint number in your Email Report reflects only Profiles who actively reported the email — it does not reflect the total number of emails that landed in a spam or junk folder (that's a separate, mostly invisible process).
Why it matters for deliverability: Spam complaints are the most damaging signal to your sender reputation. ISPs track complaint rates closely — Google recommends staying below 0.1% (1 complaint per 1,000 delivered emails). Consistently exceeding this threshold will result in your emails being routed to spam or blocked entirely. Common causes include sending to Profiles who didn't consent, sending too frequently, having a hard-to-find unsubscribe link, or sending irrelevant content.
Unsubscribes
An unsubscribe happens when a Profile clicks the unsubscribe link and confirms the opt-out. Unlike spam complaints, unsubscribes are a healthy signal — they mean the Profile found and used the intended opt-out mechanism instead of reporting you as spam.
Why it matters for deliverability: A visible, easy-to-find unsubscribe link actually protects your deliverability. When the opt-out path is clear, disinterested recipients unsubscribe cleanly instead of hitting the spam button. Never re-subscribe a Profile who has unsubscribed unless you have received explicit, new consent.
💡 Check your reports after every send
Monitor bounces, spam complaints, and unsubscribes in your Email Report after every sending. Export the Bounces tab to see individual bounce codes and reasons. If you notice high numbers, act immediately — don't wait for the next send.
Read more: Bounce rate and Spam complaints — detailed explanations, bounce codes, spam traps, and blacklists.
💡 Spam complaint visibility is limited
The spam complaint count in your Email Report only includes complaints sent back to Apsis via Feedback Loops (FBLs). Not all email providers participate in FBLs — notably, Gmail does not send spam complaints through Feedback Loops. To see spam complaint data for Gmail recipients, you need to set up Google Postmaster Tools for your sending domain. This is a free tool from Google that gives you visibility into your domain's reputation and spam rate among Gmail users.
Deliver-friendly content
The content of your email affects whether spam filters let it through. Follow these guidelines to stay out of the spam folder:
Guideline | Details |
Avoid spam trigger words in the subject line | Words like "free", "win", "money", "help", "urgent", and "act now" are common spam triggers. Use clear, relevant subject lines instead. |
Use URLs conservatively | Use clear, full URLs with proper parameters. Avoid URL shorteners (like bit.ly) — spam filters distrust shortened URLs because they hide the destination. |
Balance text and images | Don't build your email from images only. Use a mix of Heading, Paragraph, Image, and Button Elements. Emails that are one large image are more likely to be flagged as spam, and they don't display if images are blocked by the recipient's email client. |
Include an unsubscribe link | Required by law and expected by ISPs. Making it easy to unsubscribe reduces spam complaints — which is better for your reputation than having recipients mark you as spam because they can't find the opt-out. |
Email authentication
Email authentication proves to recipient servers that your email is legitimate and not sent by someone impersonating your domain. It's one of the most important factors in deliverability.
Protocol | What it does | Your role |
SPF | Prevents forged emails from being sent from an illegitimate source impersonating your domain. | No action needed — SPF is pre-configured on the Apsis One technical sender domain ( |
DKIM | Verifies you are authorised to send emails from your "from" domain. Significantly reduces spam folder placement. | Set up during onboarding with your Apsis Consultant. You provide a domain and selector; Apsis creates the key pair; you publish the TXT record in your DNS. |
DMARC | Built on top of SPF and DKIM. Provides reports on rejected emails and gives you control over how failed authentication is handled. | Configure on your domain's DNS. DMARC policies are set by you (or your IT team). |
Read more: Email Authentication – Safe Sending
⚠️ DKIM and DMARC are now required
Since mid-2025, major email providers (Google, Yahoo, Microsoft) actively enforce DKIM and DMARC as requirements for bulk senders. Without both in place, your emails are at serious risk of being blocked or sent to spam. Set up DKIM during onboarding and ensure your domain has at least a basic DMARC record (p=none). Don't skip either.
Custom domain
Setting up a Custom domain for links and system pages adjusts URLs in your emails and system-generated pages (like the web version and unsubscribe page) to display your own domain instead of the default Apsis tracking domain.
When Profiles hover over or click a link and see your own domain, it builds trust and reinforces your brand. It also improves deliverability — some spam filters treat emails with unfamiliar third-party link domains as suspicious.
Read more: Custom domain — Setup and onboarding
Warm up your sender domain
If you're new to Apsis One or haven't sent to large audiences before, your private technical sender domain needs to be gradually warmed up. Sending a large volume immediately from a new or unused domain looks suspicious to ISPs and can result in your emails being throttled, sent to spam, or blocked.
Good data hygiene combined with a gradual warm-up ensures your technical sender domain builds a positive reputation over time.
💡 Good to know
Sendings from completely new technical sender domains (considered neutral by ISPs) will often end up in the "Promotions" or "Other" tab in email clients like Gmail. This is normal and will improve as your sender domain builds reputation through consistent, well-received sends.
Warm-up guidelines
The warm-up process applies to any account that intends to send to more than 10,000 recipients per day. Adjust the numbers below to match your target sending volume.
Example: goal of 30,000 recipients per day
Day | Send to | Action |
Day 1 | 1,000 recipients | Check Email Reports — verify that delivery rate and open rates are good. Check your own recipient addresses to confirm they receive the email. Bad statistics may indicate DKIM/DMARC issues.* |
Day 2 | 5,000 recipients | Repeat follow-up. Send to new recipients — not the same ones as Day 1. Emailing the same recipients several days in a row may cause them to mark the email as spam. |
Day 3 | 10,000 recipients | Repeat follow-up. |
Day 4 | 20,000 recipients | Repeat follow-up. |
Day 5 | 30,000 recipients | Repeat follow-up. If all looks good, you're ready for normal sending. |
* For help with bad statistics, reach out to Customer Service and pause the warm-up process until the issue is resolved.
Example: goal of 10,000,000 recipients per day
Day | Send to |
Day 1 | 10,000 recipients |
Day 2 | 100,000 recipients |
Day 3 | 1,000,000 recipients |
Day 4 | 5,000,000 recipients |
Day 5 | 10,000,000 recipients |
Follow up after each day by checking delivery statistics and open rates.
What's next?
Email Authentication – Safe Sending — SPF, DKIM, DMARC, IP management, and TLS encryption.
Email – Best Practice — Design, content, and accessibility tips.
About Microsoft's EOP — How Exchange Online Protection affects deliverability.
Apple Mail Privacy Protection (MPP) — How Apple's privacy features affect open tracking.