# Inbox placement test

> Learn what an inbox placement test measures, how seed-list results work, and why a placement snapshot is not a delivery guarantee.

An inbox placement test sends a representative email to seed addresses at different mailbox providers, then reports whether those test messages reached the inbox, spam, or neither. It is useful provider-specific evidence for that message and sending path, not a guarantee of campaign-wide placement. Seed addresses do not behave like your subscribers, and mailbox providers do not publish every filtering input, so compare a result with authentication, complaint, and sending data before changing a campaign.

## Quick takeaways

- A placement test observes a sample message at test mailboxes, often by provider and folder.
- Inbox, spam, and missing results describe the seed-list outcome, not every subscriber's future outcome.
- Use the actual sender, subject, content, and infrastructure you want to evaluate.
- Check authentication and sender-quality evidence alongside the placement snapshot.
- Retest the same path after one controlled change so the result remains interpretable.

## How an inbox placement test works

An inbox placement test starts with a sample message that matches the mail you plan to send. [Amazon's inbox-placement documentation](https://docs.aws.amazon.com/pinpoint/latest/userguide/channels-email-deliverability-dashboard-pipt.html) describes sending that message to special addresses at major email domains, then reporting inbox, spam, missing, SPF, and DKIM outcomes by provider. The exact number of seed addresses and providers depends on the testing service.

That makes the result more specific than server acceptance. [Email deliverability](/learning/what-is-email-deliverability) includes the wider question of whether a message reaches a usable folder, while a placement test records what happened to its test copies at the monitored providers. It does not expose a receiver's private scoring formula.

![Seed-list test flow from a representative message to provider folder observations and a snapshot warning.](/images/editorial/inbox-placement-test/inbox-placement-test-flow.svg "1440x820")

*Source: Original Palisade deterministic diagram based on [Amazon's inbox placement test documentation](https://docs.aws.amazon.com/pinpoint/latest/userguide/channels-email-deliverability-dashboard-pipt.html). It explains the testing method and does not represent a provider interface or scoring formula. [Open the full-size diagram](/images/editorial/inbox-placement-test/inbox-placement-test-flow.svg).*

## What the result means

Treat the percentages as a snapshot of the message at those seed addresses. A high inbox percentage says the tested copies reached the inboxes in that test. A spam or missing outcome identifies a provider and message path worth investigating. Neither result proves how every subscriber will receive the next campaign.

[Kit's placement-test guidance](https://help.kit.com/en/articles/4478092-inbox-placement-tests-how-to-analyze-the-results) explains one important limitation: seed addresses have no real subscriber engagement, so their behavior can differ from your actual audience. This is why a placement test can start an investigation, but should not be the only evidence behind a broad campaign change.

```text
PLACEMENT TEST RECORD

Message version: July product update, version B
Sending path: production marketing sender
Provider outcome: inbox / spam / missing by provider
Authentication: SPF, DKIM, and DMARC results from a delivered copy
Sender-quality evidence: complaint and bounce trend for the same program
Next change: one controlled change, then retest the same path
```

## How to use the result without overreacting

### 1. Test the message you actually plan to send

Keep the sender identity, subject, content, links, and sending service representative. A message from another mailbox or a simplified template can test a different path than the campaign you need to assess.

### 2. Separate placement from message-signal diagnosis

If the test points to a placement concern, send the same message to Palisade's [email deliverability test](/tools/email-deliverability-test) when you also need message-level SPF, DKIM, DMARC, blocklist, or content evidence. That tool inspects a received message, but it does not report Gmail or Outlook folder placement. The two tests answer adjacent questions.

### 3. Check the evidence that seed mailboxes cannot supply

Review your own complaint, bounce, and engagement data for the same sender and audience. For Gmail, [Google's sender guidelines](https://support.google.com/a/answer/81126) direct senders to keep the Postmaster Tools spam rate below 0.3%, with below 0.10% recommended. That guidance is separate from a seed-list result and should be evaluated in the context of the messages and recipients covered by your program.

### 4. Change one variable and retest the same path

Do not treat one poor seed result as proof that a specific phrase, blocklist, or DNS record caused filtering. First use the delivered message and sender data to identify a plausible issue. Make one documented change, then run the same representative message through the same test approach. If mail is already reaching spam for real recipients, follow the evidence-ordered repair guidance in [why outbound email goes to spam](/learning/why-do-your-emails-go-to-spam-and-how-can-you-fix-it).

## When an inbox placement test is the wrong tool

A seed-list test is not the fastest way to answer every deliverability question. Use a message-level diagnostic when you need to inspect authentication or blocklist signals from one received email. Use provider postmaster and campaign data when the issue concerns your actual audience or complaint trend. If you are choosing a service category, the [email deliverability service guide](/learning/best-email-deliverability-service) separates placement monitoring from authentication monitoring, list validation, and consulting.

## Sources and further reading

- [Amazon Pinpoint inbox placement tests](https://docs.aws.amazon.com/pinpoint/latest/userguide/channels-email-deliverability-dashboard-pipt.html)
- [Kit: inbox placement test analysis](https://help.kit.com/en/articles/4478092-inbox-placement-tests-how-to-analyze-the-results)
- [Google email sender guidelines](https://support.google.com/a/answer/81126)

## Frequently asked questions

### What is an inbox placement test?

An inbox placement test sends a representative email to seed mailboxes and reports whether the test copies reached inbox, spam, or went missing. It measures a provider-specific test outcome for that message and path, not a promise for every recipient in a campaign.

### Does an inbox placement test guarantee inbox delivery?

No. A seed-list result is a snapshot from test addresses. Real subscriber engagement, sender history, provider-specific filtering, and later campaign conditions can differ, so use the result with authentication and sender-quality evidence.

### How do I measure inbox placement rate?

Divide the number of test copies reported in the inbox by the number of test copies sent or observed, using the testing service's stated method. Record spam and missing outcomes beside it, because an inbox percentage alone hides where the remaining copies went.

### Should I test every campaign before sending it?

Only when the risk, volume, or recent evidence justifies another placement snapshot. Testing is most useful for a representative message after a meaningful infrastructure or campaign change, or when real-recipient evidence points to a provider-specific placement issue.

### Can SPF, DKIM, and DMARC improve inbox placement?

Yes, passing and aligned authentication removes an important avoidable trust problem, but it does not control a receiver's folder decision. Check those results with a delivered message and combine them with complaint, reputation, and placement evidence.