Inbox placement: definition and practice

Definition

Inbox placement concerns where a receiving system places an email after processing it. It differs from server acceptance, which can occur before a message is filtered into spam or another destination. It also differs from a recipient reading, replying to, or valuing the message. Those outcomes should be measured and described separately.

Placement varies with sending configuration, reputation, message content, recipient behaviour, and receiver rules. A result from a test set is evidence about that test, not proof of every recipient's experience. Any reported measure needs a defined method, population, and period. A blanket claim without that context can conceal uncertainty about whether actual target mailboxes received messages in the intended location.

In origination work

Review domain authentication and the real sending path, then distinguish accepted, bounced, filtered, and replied outcomes where evidence permits. Preserve the limitations of placement tests instead of converting them into a guaranteed campaign result. Optional outreach should still depend on target approval, messaging approval, and suppression checks. A relevant, carefully researched approach does not bypass receiver policies, and technical delivery does not establish an owner's interest in a transaction. Report the evidence available for each stage rather than treating a lack of bounce as an inbox-placement finding.

What determines placement

Inbox placement is the share of sent mail that arrives in the recipient's inbox, as opposed to spam folders or being rejected. Mailbox providers decide using signals including authentication, sending-domain and IP reputation, recipient engagement and complaints, list quality, message content and sending patterns. No provider publishes a complete formula, so placement is measured and managed, not guaranteed.

Providers do publish thresholds and expectations. Google's guidelines for senders, for example, set a spam complaint rate that senders are asked to stay under, and ask bulk senders to authenticate their mail and provide one-click unsubscription. Free tools such as Google Postmaster Tools show a sender's domain reputation and spam rate as Gmail sees them, and other providers publish sender resources.

Measuring honestly

Placement can be estimated with seed lists, with provider dashboards, and with engagement data, and each method has limits. Seed accounts may not behave like real recipients; dashboards cover only one provider; open rates are distorted by privacy features that preload images. Use more than one method, and be wary of any single headline figure, including a vendor's. A claim such as 99 percent placement should be tied to a stated method, period and sample.

Bounce and complaint data are more reliable than opens. Track hard bounces, soft bounces, complaints and unsubscribes by domain and by campaign. Rising complaints or bounces are early warnings that list quality or targeting has slipped, and they can be acted on directly: pause, review the segment, and remove problem addresses before reputation suffers.

Practices that protect reputation

Send to small, well-targeted lists of people with a real reason to receive the message, at modest volumes that increase gradually; authenticate with SPF, DKIM and DMARC; include accurate identification and a working unsubscribe; honour opt-outs immediately; and avoid sending to addresses that have bounced. Sending from a dedicated domain isolates risk. These are the habits that industry best-practice documents and provider guidance describe.

Place the limits on the claim. Even a clean programme cannot promise that a given message will be read, only that it was sent properly and delivered to the inbox at a measured rate. And because sensible outreach to this audience is a one-to-one professional communication, restraint is better than volume: a poor reply rate with few complaints is a healthier signal than a high send count with rising ones.

Sender authentication (SPF, DKIM, DMARC) — Email standards that help receivers assess sending-domain authorisation, signatures, and alignment with the visible sender domain.
Suppression list — A maintained set of records that prevents contact for specified recipients, companies, or communication scopes.
Deal flow — The stream of potential transaction opportunities entering a defined acquisition process over a stated period.

Sources and further reading

Email sender guidelines, Google Workspace Admin Help. The receiving side's published requirements, including authentication and the spam-rate threshold for bulk senders.
Set up Postmaster Tools, Google. Gives senders domain reputation and spam-rate data as Gmail sees it.
Outlook.com sender requirements and troubleshooting, Microsoft. The equivalent rules for the other half of corporate inboxes.
Sender best practices, Yahoo Sender Hub. A second large provider's authentication and complaint-rate expectations.
Published documents and best common practices, M3AAWG. Industry best practice on sending reputation, list hygiene and abuse handling, written by the operators.
RFC 7489 — Domain-based Message Authentication, Reporting, and Conformance (DMARC), IETF. Alignment, policy and the aggregate reports that tell you who is sending as you.

To apply these distinctions to your own acquisition criteria, discuss your research brief or inspect the demo platform.