Coderhouse goes global

🌍

Read more

What Is Email Deliverability? How GTM Engineers Protect Outbound Domains

AI Engineering

Build and ship real applications with LLMs, agents and automation.

8 weeks · Live online · View course →

Data Analytics

Go from zero to job-ready analyst with SQL, Python and BI tools.

10 weeks · Live online · View course →

Dan Patiño

AI Strategy & Innovation at Coderhouse

Artificial Intelligence

What Is Email Deliverability? How GTM Engineers Protect Outbound Domains

What Is Email Deliverability? How GTM Engineers Protect Outbound Domains

Email deliverability is the ability of an email to land in the recipient’s inbox instead of the spam folder, a promotions tab or a silent rejection. For go-to-market teams that rely on outbound, it is the invisible layer that decides whether a carefully personalized sequence gets read or disappears.

Deliverability used to be a topic for email marketers. Today it sits squarely in the GTM engineer’s job: the same person who builds enrichment workflows and AI-written sequences also owns the sending domains, DNS records and volume rules that keep those sequences out of spam. This guide explains how deliverability works, which signals mailbox providers use, and how GTM engineers protect outbound domains as they scale.

What is email deliverability?

It helps to separate two ideas that are often confused:

  • Delivery rate is the share of emails accepted by the receiving server (not bounced). An email can be “delivered” and still go straight to spam.

  • Deliverability (inbox placement) is the share of emails that actually reach the inbox. This is the number that matters for replies and pipeline.

Mailbox providers such as Gmail, Outlook and Yahoo decide inbox placement using three groups of signals: authentication (can the sender prove who they are?), reputation (how have recipients reacted to this domain and IP in the past?) and content and engagement (do people open, reply, delete or report the messages?).

Why deliverability became a GTM engineering problem

Two shifts pushed deliverability into the technical side of revenue teams. First, outbound became automated: AI SDRs and sequencing tools can send thousands of emails a day, which magnifies any mistake. If you are new to that model, our guide on what an AI SDR is and how GTM teams build outbound automation covers the moving parts.

Second, mailbox providers tightened their rules. Since February 2024, Google’s email sender guidelines require all senders to Gmail accounts to set up SPF or DKIM, keep valid forward and reverse DNS, use TLS and keep spam rates reported in Postmaster Tools below 0.3%. Senders of more than 5,000 messages a day to Gmail must also set up SPF, DKIM and DMARC, align the From domain and support one-click unsubscribe for marketing and subscribed messages. Yahoo announced similar requirements at the same time. Configuring and monitoring all of that is engineering work.

The authentication stack: SPF, DKIM and DMARC

SPF (Sender Policy Framework)

SPF is a DNS TXT record that lists the servers and services allowed to send email for your domain. When your sequencing tool sends on your behalf, it needs to be included in that record, or receiving servers may treat the message as suspicious.

DKIM (DomainKeys Identified Mail)

DKIM adds a cryptographic signature to each email. The receiving server checks it against a public key published in your DNS, which proves the message was not altered and really comes from your domain.

DMARC

DMARC, defined in RFC 7489, ties SPF and DKIM to the visible From address through “alignment” and tells receivers what to do when checks fail: p=none (monitor only), p=quarantine or p=reject. It also sends aggregate reports, which are a goldmine for spotting tools that send as your domain without being configured correctly.

A practical rule: every new tool that sends email (CRM, sequencer, support desk, product notifications) should be added to SPF, signed with DKIM and verified in DMARC reports before it goes live.

How GTM engineers protect outbound domains

Authentication is the entry ticket. Protecting reputation over time takes a set of operational habits that GTM engineers usually encode in their stack:

  1. Separate sending domains. Many teams send cold outbound from secondary domains (for example, a variant of the main brand domain) so a reputation hit never touches the primary domain used for customers, invoices and product email.

  2. Warm up gradually. New domains and mailboxes start with low daily volume that grows over weeks. Sudden spikes are one of the clearest spam signals.

  3. Cap volume per mailbox. Instead of pushing one inbox hard, teams spread volume across several mailboxes with conservative daily limits and rotate them in the sequencer.

  4. Verify emails before sending. Bounces damage reputation fast. Verification steps should run after enrichment and before any contact enters a sequence. Our explainer on data enrichment and waterfall enrichment shows where that check fits.

  5. Target tightly. Relevance is a deliverability tactic. Emails sent to people who match your ideal customer profile get more replies and fewer spam reports.

  6. Make opting out easy. A clear way to stop receiving emails reduces spam complaints. For bulk marketing mail, one-click unsubscribe follows RFC 8058.

  7. Write like a human. AI-generated copy should be varied, plain-text friendly and light on links, images and tracking. Identical templates sent at scale are easy for filters to cluster.

Metrics to monitor

  • Spam complaint rate in Google Postmaster Tools, kept well below the 0.3% threshold.

  • Bounce rate per list and per enrichment source, to catch bad data early.

  • Reply rate and positive reply rate, which are more reliable engagement signals than opens, since privacy features distort open tracking.

  • DMARC pass rate across all tools sending as your domains.

  • Inbox placement tests with seed accounts before launching a new campaign or domain.

The best setups push these numbers into a dashboard and trigger alerts, for example pausing a mailbox automatically when its bounce rate crosses a limit.

Common deliverability mistakes

  • Launching a sequence from a brand-new domain with no warm-up.

  • Sending cold email from the primary company domain.

  • Uploading purchased or unverified lists straight into the sequencer.

  • Adding a new sending tool without updating SPF and DKIM.

  • Leaving DMARC reports unread for months.

  • Measuring success by volume sent instead of replies and meetings booked.

FAQ

Is email deliverability the same as delivery rate?

No. Delivery rate only says the receiving server accepted the email. Deliverability is about where it landed: inbox, promotions or spam.

Do I need DMARC for cold outbound?

Gmail requires DMARC for senders above 5,000 messages a day to its accounts, and having it in place is a best practice at any volume because it proves alignment and gives you visibility into who sends as your domain.

How long does domain warm-up take?

It depends on the provider and target volume, but teams typically ramp new domains over several weeks while watching bounces, complaints and replies before reaching full volume.

Keep learning with Coderhouse

Deliverability is one of the systems a GTM engineer designs end to end, alongside enrichment, routing and AI-assisted outbound. If that is the path you want, the GTM Engineer Course is opening an early-access waitlist. Explore all three programs:

Dan Patiño

I'm Dan Patiño, head of AI Strategy & Innovation at Coderhouse. My day-to-day work involves merging the tactical management of e-commerce (CRO, Email Marketing and SEO) with the development of disruptive solutions. I specialize in building internal AI-powered apps to automate tasks and boost innovation within the team. I firmly believe that technology is strategy's best ally. To dive deeper into my professional journey, I'll be waiting for you on my LinkedIn profile.