The Gap Between "Delivered" and "Seen"
A 99% delivery rate sounds like a success. In reality, it tells you only that the receiving mail server accepted your message. It says nothing about what happened next. Whether that message landed in the primary inbox, the spam folder, or the promotions tab is a question most sending platforms could not answer until recently.
For Amazon SES senders, this was a genuine blind spot. SES has always provided bounce and complaint data through Amazon SNS, and the Virtual Deliverability Manager (VDM) introduced engagement tracking and delivery insights. But inbox placement itself, the percentage of messages that actually reach the recipient's primary inbox, was invisible. You could watch your bounce rate stay below 2% and your complaint rate stay under 0.1%, and still have a third of your marketing mail silently disappearing into spam folders across Gmail, Outlook, and Yahoo. Industry figures consistently put the average inbox placement rate at roughly 83%, meaning approximately one in six legitimate commercial emails never reaches the primary inbox. For senders with reputation problems, that proportion climbs far higher.
In May 2026, AWS addressed this gap directly. The Global Deliverability feature set inside Virtual Deliverability Manager brings inbox placement rate reporting, pre-send content testing, and passive blocklist monitoring into the SES console as a single paid subscription. This article explains exactly what each feature does, how to read the data it produces, where its visibility ends, and how to combine it with real-time monitoring tools to build a complete deliverability picture.
What Amazon SES Launched in May 2026
On 29 May 2026, AWS announced that Amazon SES now offers inbox placement metrics and blocklist monitoring. The announcement was brief, but the documentation behind it describes something considerably more substantial. Global Deliverability is a new tier within Virtual Deliverability Manager that extends visibility beyond the SES sending infrastructure itself. Where standard VDM surfaces delivery rates, bounce classifications, complaint rates, and engagement signals for mail sent through SES, Global Deliverability goes further: it provides analytics based on a representative sample of your sending across every provider your domains send through, not just Amazon SES.
The feature set includes four components: campaign analytics, inbox placement rates, inbox placement tests, and blocklist monitoring. Campaign analytics surfaces per-campaign deliverability and engagement metrics drawn from sampled data associated with your monitored domains, including mail sent through non-SES providers. Inbox placement rates provide ISP-level placement data updated hourly. Inbox placement tests let you send candidate content to seed accounts at major mailbox providers before any real subscribers receive it. Blocklist monitoring checks your dedicated IPs and sending domains against major blocklist operators on an hourly basis. All four are accessible from the Virtual Deliverability Manager section of the Amazon SES console, and they are supported in all AWS commercial regions where SES is available.
Inbox Placement Rates by Domain and Campaign
What the metric actually measures
Inbox placement rate is the proportion of delivered emails that reach the recipient's primary inbox rather than the spam or junk folder. A 95% delivery rate combined with a 70% inbox placement rate means that roughly a quarter of your accepted messages are invisible to recipients. Your ESP reports the first number; the second requires a separate data source entirely.
AWS calculates inbox placement rates using samples of industry data. The documentation describes the figures as being based on a representative sample and explicitly states they do not reflect the full volume of emails sent. AWS does not publicly disclose the panel partners, panel size, or regional coverage behind these figures. That opacity is worth noting: the numbers are directional indicators rather than precise counts. They are best read as trend data, a signal that something has changed, rather than an exact audit of every message you send.
Reading the data in the console
Within the Global Deliverability section of the VDM console, the Inbox placement rates view gives you an ISP-level breakdown showing inbox rate, spam rate, inbox count, and spam count for each major mailbox provider, including Gmail, Outlook, and Yahoo. An aggregate metric summarises overall inbox and spam rates across all ISPs for a selected domain. A time-series chart displays inbox placement rates by ISP over a chosen date range of 7, 14, 30, or 90 days, allowing you to spot trends and correlate drops with specific sends or configuration changes. Data is updated hourly, so you are looking at near-real-time trend data rather than waiting for a daily report.
To access this data, navigate to the Amazon SES console, select Virtual Deliverability Manager from the left navigation pane, then choose Inbox placement rates under Global deliverability. Select your monitored domain from the domain selector, adjust the date range if needed, and review the ISP breakdown table alongside the trend chart. Pay attention to provider-specific outliers: a weak Outlook score can drag down your overall aggregate even when Gmail performance looks healthy, because the providers use substantially different filtering models.
Benchmarks to aim for
Industry data puts the cross-sector average inbox placement rate at approximately 83%, meaning roughly one in six marketing emails does not reach the inbox. A placement rate of 87% or higher puts you in the top quarter of senders, and programmes with strong authentication, engaged lists, and disciplined list hygiene regularly achieve 93% or above. A rate below 80% signals that you are losing material revenue and engagement to non-delivery; anything below 70% is a serious problem that warrants immediate investigation. Provider-specific variation is significant: Gmail's overall acceptance rate runs high, though a substantial portion of bulk mail lands in the Promotions tab rather than Primary, while Outlook has historically been more conservative with inbox rates for bulk senders who have not specifically optimised for Microsoft's filtering signals. Yahoo tends to sit closer to the global average.
When your VDM inbox placement rate drops, the immediate question is whether the decline is domain-wide or provider-specific. A sudden drop at Gmail alone suggests a content or engagement signal issue, or a complaint rate creeping toward Google's published 0.10% danger threshold. A simultaneous drop across all providers suggests a more systemic problem: a blocklist listing, an authentication failure, or a sharp deterioration in list quality. This is where correlating VDM placement data with your real-time bounce and complaint stream becomes essential.
Pre-Send Inbox Placement Tests
Inbox placement tests are the most practically useful feature in the Global Deliverability suite. Rather than learning that your last campaign landed heavily in spam after the fact, you send your candidate content to seed accounts at major mailbox providers before any real subscribers receive it.
The mechanism is a standard seed-list test. SES sends your campaign to monitored addresses maintained at major providers, and the system checks where each message lands, whether inbox, spam, or missing entirely, and reports back. Results are typically available within two to four hours. Each completed test provides an overall summary showing inbox percentage, spam percentage, and missing percentage across all tested ISPs, along with an ISP breakdown giving per-provider figures for Gmail, Outlook, Yahoo, and other major providers. The test details section records the report ID, subject line, from address, creation date, and test status, giving you a clear audit trail across test runs.
To run a test, navigate to Virtual Deliverability Manager in the SES console, choose Inbox placement tests under Global deliverability, and follow the guided flow to submit your content. The test should use the exact content, subject line, from address, and sending domain you intend to use in production. Testing a stripped-down version of your email that omits the elements most likely to trigger filters gives you a result that flatters the real message and defeats the purpose of the exercise entirely.
Your Global Deliverability subscription includes a set number of inbox placement tests per month, with overage charges applying beyond that allowance. Check the Amazon SES pricing page for the current included quantity and overage rate, as these figures are subject to change. If you are running close to your monthly allowance, prioritise tests for high-volume campaigns, campaigns targeting new domains or segments you have not previously mailed, and any send where the content differs significantly from your recent history.
Blocklist Monitoring
Global Deliverability monitors your dedicated IPs and sending domains against major blocklist operators, performing hourly checks and surfacing alerts through the VDM Advisor when a listing is detected. These alerts can also be consumed programmatically via Amazon EventBridge, which means you can route blocklist notifications into your existing alerting infrastructure rather than relying on someone checking the console.
AWS describes the monitored blocklists as the industry's major blocklist operators without naming them individually. This is a genuine limitation for teams that need to know whether their IP or domain has appeared on Spamhaus, SURBL, or Barracuda specifically, because different providers weight different blocklists and a listing that matters enormously at one mailbox provider may be irrelevant at another. The VDM documentation does note that when a listing is detected, it provides the listing reason and the delisting procedure, which is practically useful for remediation even if the pre-disclosure coverage remains opaque.
When a blocklist alert surfaces, the investigation process follows a predictable pattern. First, confirm the listing using a public multi-list checker to identify exactly which lists are involved and when the listing appeared. Second, trace the cause: the most common triggers are a spike in complaint rate, a spike in hard bounce rate indicating spam trap hits, or a sudden large volume increase that resembles the pattern of a compromised account. Third, act on the underlying cause before requesting delisting. Submitting a delisting request without fixing the problem that caused the listing is ineffective and damages your credibility with the blocklist operator. Fourth, monitor closely after delisting to confirm the problem does not recur.
VDM Pricing: A Realistic Assessment
Virtual Deliverability Manager is billed at $0.07 per 1,000 emails on top of the standard SES sending cost of $0.10 per 1,000 emails, at volumes under 10 million emails per month. AWS introduced tiered pricing for VDM in February 2025, so the per-message rate decreases as your monthly sending volume crosses specific thresholds. That entry-level rate of $0.07 represents a 70% premium on the base sending cost. At 100,000 emails per month, enabling VDM adds approximately $7 to your monthly SES bill for that component. At one million emails per month, the VDM surcharge at the base tier alone is $70. A separate Deliverability Dashboard tier is also listed in SES pricing at $1,250 per month, aimed at enterprise senders who need deeper inbox placement analysis; confirm current pricing and scope directly on the Amazon SES pricing page before budgeting for it, as service definitions can change.
For senders where inbox placement directly affects revenue, such as transactional communications with high commercial value, e-commerce order flows, or marketing programmes where email is a primary acquisition channel, the cost is easily justified. For low-volume transactional senders with consistently clean lists and stable complaint rates, standard SES monitoring may be sufficient during normal operations. A practical approach is to enable VDM Global Deliverability during active campaign periods or when troubleshooting a deliverability problem, and to be deliberate about whether you leave it running continuously at lower sending volumes. The data it provides is genuinely useful, but it should be evaluated against the cost at your actual sending volume.
What VDM Does Not Cover
Understanding what VDM's Global Deliverability does not do is as important as understanding what it does. The inbox placement rate data is sampled and updated hourly; it is not a per-message audit. If a single large campaign fires and starts generating complaints or bounces at an elevated rate, VDM's placement dashboard will reflect the deterioration on its next hourly update, but by then the damage to your sending reputation may already be done.
VDM does not provide a real-time event stream for individual bounce and complaint notifications. Those signals flow through Amazon SNS and must be captured by your own endpoint or a third-party monitoring service. If a transactional email campaign starts generating hard bounces against a set of invalid addresses, VDM's aggregate dashboard will eventually reflect a lower placement rate, but it will not fire an immediate alert the moment your bounce rate crosses a threshold.
VDM also does not manage your suppression list. When Amazon SES receives a hard bounce or a complaint, the address must be suppressed to prevent future sends, either via the SES account-level suppression list or your own list management logic. VDM surfaces the aggregate rates; the per-address management is your responsibility. Similarly, VDM does not provide webhook or API alerting for reputation events. The blocklist monitoring integrates with EventBridge, which is useful, but there is no native mechanism for VDM to push a real-time alert when your complaint rate crosses 0.08% or your bounce rate suddenly spikes on a single configuration set. That monitoring layer requires a dedicated tool.
How to Combine VDM with SES Monitor
The right mental model is to treat VDM's Global Deliverability as your strategic intelligence layer and a real-time monitoring tool like SES Monitor as your operational protection layer. They address different problems and the two are genuinely complementary.
VDM tells you, across a rolling window of up to 90 days, how your sending domains are performing at each major mailbox provider, which campaigns are landing cleanly and which are not, and whether your IPs or domains have appeared on blocklists. It answers the question: is my email programme healthy overall, and where are the weak spots by provider or campaign type? That intelligence should drive strategic decisions about list segmentation, content changes, domain warm-up scheduling, and whether a particular campaign type needs its own dedicated subdomain and sending stream.
SES Monitor addresses the layer beneath that. It connects to your SES event stream via Amazon SNS and processes individual bounce and complaint events as they arrive, in real time. When a single send generates an unusual spike in hard bounces, perhaps because a list segment was imported without adequate validation, SES Monitor can alert you within seconds and automatically route those addresses to suppression before the next send fires. When your complaint rate approaches the 0.10% threshold that Google uses as a hard limit, SES Monitor provides the granular per-send and per-configuration-set visibility that allows you to identify the specific campaign or segment responsible and act before the rate crosses the line. VDM's hourly dashboard will show you the deterioration; SES Monitor's real-time alerts mean you can respond before the deterioration takes hold.
In practice: check your VDM inbox placement trends weekly to monitor domain health and campaign performance across providers; use VDM inbox placement tests before high-stakes or high-volume sends; watch VDM's blocklist monitoring for structural reputation threats; and rely on SES Monitor for the continuous, per-message bounce suppression, complaint alerting, and reputation threshold monitoring that protects your programme between those strategic check-ins.
Step-by-Step: Enabling VDM Global Deliverability
Via the AWS console
Sign in to the AWS Management Console and open the Amazon SES console. In the left navigation pane, select Virtual Deliverability Manager. If you have not yet enabled VDM at the account level, choose any of the "Get started with Virtual Deliverability Manager" prompts on the overview page and step through the onboarding wizard, which configures engagement tracking and optimised shared delivery. Once VDM is enabled, return to the Virtual Deliverability Manager settings page and choose "Enable global deliverability." You will be prompted to add the domains you want to monitor and to confirm the subscription. Global Deliverability is enabled per region. Domain monitoring tracks metrics across regions, accounts, and sending providers for your monitored domains, while IP monitoring tracks only the dedicated IPs available in the region where you enable it.
Via the AWS CLI
To enable VDM at the account level using the AWS CLI, run the following command, substituting your target region as needed:
aws --region us-east-1 sesv2 put-account-vdm-attributes --vdm-attributes VdmEnabled=ENABLED
To enable both engagement tracking and optimised shared delivery together, pass a JSON input file using the --cli-input-json flag with the appropriate VdmAttributes structure. Once VDM is active, enabling Global Deliverability and managing monitored domains can be done through the console's Virtual Deliverability Manager settings page or via the SES API v2 using the Global Deliverability operations documented in the SES Developer Guide.
Interpreting Your First Inbox Placement Report
When your first inbox placement data populates, typically within a few hours of enabling Global Deliverability assuming your monitored domains have recent sending activity, read the ISP-level breakdown first, not the aggregate. The aggregate conceals provider-specific problems. A blended rate of 85% can mask a 65% placement rate at Outlook sitting alongside 95% at Gmail, and those two situations require entirely different remediation approaches.
For each provider, note whether your spam rate is below 10%. Rates between 10% and 20% suggest a content or engagement signal problem with that provider's filters. Rates above 20% indicate a more serious reputation issue. Cross-reference any unusual ISP reading with your SES Monitor data for the same period: a jump in complaint rate at Microsoft addresses often precedes a worsening Outlook inbox placement rate by one to two sending cycles. Catching the complaint signal early through real-time monitoring gives you the opportunity to act before VDM's placement data shows the downstream effect.
A drop in inbox placement rate without a corresponding rise in bounces or complaints often points to content or engagement factors: a subject line triggering spam filters, a template change that altered link density, or a list segment that has aged beyond the point of active engagement. In that scenario, run an inbox placement test with your current template against your last known good version to isolate the change. If the test confirms the content is the issue, iterate before sending to your full list.
A Deliverability Monitoring Checklist for SES Senders in 2026
Amazon SES's Global Deliverability features are the most significant improvement to built-in deliverability visibility that SES has offered. They close a genuine gap that existed for years: the inability to know whether mail was landing in inboxes or spam folders. For any sender running meaningful volume through SES, the case for enabling VDM and its Global Deliverability subscription is strong.
At the same time, VDM's strategic intelligence is most effective when paired with real-time operational monitoring. The two serve different roles, and neither alone is sufficient for a sender that takes reputation seriously.
Authentication. Confirm SPF, DKIM, and DMARC are correctly configured for all sending domains. Gmail, Yahoo, and Microsoft now enforce bulk sender authentication requirements. Authentication is the entry requirement, not a deliverability advantage.
Enable VDM and Global Deliverability. Add your monitored domains and allow the inbox placement rate data to accumulate for at least seven days before drawing conclusions. Enable EventBridge integration for blocklist alerts from day one.
Run a baseline inbox placement test. Before your next major campaign, run a pre-send test using your current template and sending identity. Establish a baseline so that future test results have a point of comparison.
Connect SES Monitor. Route your SES bounce and complaint notifications through Amazon SNS to SES Monitor. Configure threshold alerts for bounce rate and complaint rate so that deterioration is caught in real time, not on your next VDM check-in.
Review VDM placement data weekly. Look at trends by ISP and by campaign. Investigate any provider where the spam rate has risen week on week. Correlate placement changes with your SES Monitor bounce and complaint data.
Suppress immediately. Hard bounces and complaint events must feed into your suppression list without delay. No VDM feature manages this for you; it requires active suppression management at the point each event fires.
Keep complaint rates below 0.08% as an operational target. Google's published threshold is 0.10%, but the operational safety margin is narrower than that figure suggests. Crossing 0.10% risks immediate inbox placement degradation at Gmail.
If you are not yet tracking your SES bounce and complaint events in real time, that is the single highest-priority gap to close. Start a free SES Monitor trial and connect it to your SES event stream today; it takes minutes to set up and gives you the real-time reputation layer that VDM's strategic dashboard does not provide.