What are the volume requirements for SNDS and GPT data?
Updated on 18 Oct 2026: We clarified Google's API statistics minimum and added checks for expired SNDS access and shared IP reporting.
Microsoft's Smart Network Data Services (SNDS) can omit mail traffic and spam data for an IP that sends fewer than 100 messages on a given day. Google Postmaster Tools (GPT) documents an API statistics minimum of 50 users per day, but no message count guarantees every dashboard will populate. Low-volume privacy filtering still applies, so 100 or 1,000 messages per day is not a guaranteed dashboard threshold.
The counting unit matters more than a monthly total. SNDS reports by sending IP and Pacific day for traffic Outlook.com receives. Microsoft labels this day PST and includes daylight saving adjustments. Google Postmaster Tools reports several domain, IP, and compliance views for mail sent to personal Gmail accounts, and it uses UTC. A sender can send 20,000 messages in a month and still see empty panels when traffic is spread across days, IPs, domains, or recipient providers.
Answer in one place
- SNDS: Treat 100 Microsoft-recipient messages per IP per day as the practical reporting floor because Microsoft says data can be absent below it.
- Google Postmaster Tools: The API minimum is 50 users/day; dashboard visibility still depends on eligible data and privacy filtering.
- Reliability: Use consistent daily sending and compare several active days because one visible or missing point does not establish a threshold.
- Bulk rule: Do not confuse Gmail's 5,000-message daily bulk sender classification with the volume needed to populate Postmaster Tools.
SNDS and Google Postmaster Tools volume thresholds
For SNDS, plan around 100/day per sending IP. Microsoft's SNDS FAQ says mail traffic and spam data can be missing for an IP that sent fewer than 100 messages on the given day. This is a reporting suppression rule, not a deliverability rule. Sending 99 messages from an IP is not automatically bad, but SNDS can omit that day's data.
For Google Postmaster Tools, no published message count guarantees data in every dashboard. The Google dashboard documentation explains that reporting depends on the view. Spam rate uses DKIM-authenticated mail, reputation groups traffic by authenticated domains or IPs, authentication can be viewed by From domain or authentication domain, and compliance status applies at the primary-domain level.
|
|
|
|
|---|---|---|---|
100/day | IP + Pacific day | Data can be absent below 100 | |
No universal dashboard guarantee | Dashboard-specific + UTC day | Low-volume days can be omitted | |
Google Postmaster Tools API | At least 50 users/day | Domain + UTC day | Users, not message totals |
Gmail bulk sender | About 5,000/day | Primary domain and subdomains + 24 hours | Compliance classification, not a data floor |
Published volume rules and reporting units for SNDS and Google Postmaster Tools.
Reporting minimums and dashboard visibility
Microsoft's reporting caveat, Google's API minimum, and Gmail's bulk sender rule measure different conditions.
SNDS below 100/day
Published caveat
Traffic and spam data can be absent for the IP.
SNDS at 100+/day
Practical floor
The IP clears the stated low-volume caveat, but data is not guaranteed.
Google Postmaster Tools
Dashboard-specific
No published message count guarantees data across all dashboards.
Gmail bulk classification
Separate rule
About 5,000 messages in 24 hours triggers sender requirements, not dashboard visibility.
Google's 50-user API minimum
Google's API statistics guide states that domains must send to at least 50 users per day to receive statistics. The unit is users, not messages.
Sending 100 messages to 10 Gmail users does not meet that condition. Track distinct recipients alongside daily message totals.
The API minimum does not guarantee every dashboard will populate. Privacy filtering and each dashboard's eligible data still apply.
Why SNDS and Google Postmaster Tools go blank
The common mistake is counting all sent mail. Neither system reports a full email program. SNDS reports Outlook.com consumer traffic for authorized IPs, including Hotmail, Live, and MSN addresses. Google Postmaster Tools reports what Google sees for verified domains sending to personal Gmail accounts ending in @gmail.com or @googlemail.com. Mail sent to corporate domains or other providers, including Google Workspace accounts, does not increase the relevant personal Gmail count.
This is why monthly volume produces misleading expectations. A domain sending 3,000 messages per month sounds active. If it sends 100 messages per day, only 40 go to personal Gmail accounts, and those 40 use two authentication domains, Google has little data for each slice. The same logic applies to SNDS when Microsoft traffic is spread across several IPs.
SNDS
- Counting unit: Use an individual sending IP on a specific Pacific day.
- Recipient scope: Count Outlook.com consumer traffic, rather than every Microsoft-hosted mailbox.
- Blank reason: The IP sent too little mail, SNDS access is missing or expired, or no relevant signal exists.
Google Postmaster Tools
- Counting unit: Use the domain or IP grouping for the selected dashboard on a UTC day.
- Recipient scope: The data applies to personal Gmail accounts, not every Google-hosted address.
- Blank reason: Gmail volume is too low, the domain is unverified, authentication is missing, or the panel lacks enough signal.
Each Google Postmaster Tools dashboard has its own eligible data. The Spam Rate dashboard measures user-reported spam against DKIM-authenticated mail delivered to engaged users' inboxes. Messages automatically filtered to spam are excluded from that inbox denominator. Reputation views group DKIM-authenticated traffic first, with SPF-authenticated traffic used when DKIM is absent. Feedback Loop data needs valid Feedback-ID headers plus enough messages and spam reports. One panel can contain data while another remains blank.
Google Postmaster Tools dashboard with gaps and insufficient data on low-volume days.
A blank panel proves only that the provider did not return data for that day and view. It does not prove that delivery was healthy or broken. Compare the provider view with sending logs, bounces, authentication results, and complaint handling.
How to measure volume correctly
The cleanest way to investigate whether SNDS or Google Postmaster Tools will show data is a daily recipient-provider report. Record recipient deliveries and distinct recipients by provider, time zone, sending IP, visible From domain, SPF domain, and DKIM signing domain. This exposes the thin slices hidden inside a campaign total.
Example daily deliveries and distinct recipientstext
date,day_boundary,destination,from_domain,dkim_domain,ip,recipient_deliveries,distinct_recipients 2026-06-01,UTC,gmail,example.com,example.com,192.0.2.10,138,80 2026-06-01,America/Los_Angeles,microsoft,example.com,example.com,192.0.2.10,121,116 2026-06-02,UTC,gmail,example.com,example.com,192.0.2.10,47,38 2026-06-02,America/Los_Angeles,microsoft,example.com,example.com,192.0.2.10,92,89
The SNDS counts show which days fall below Microsoft's published low-volume caveat: June 1 is above 100 and June 2 is below it. Clearing that caveat does not guarantee data. Gmail message totals alone do not guarantee dashboard visibility; check distinct recipients and the selected view. A second authentication domain or sending IP can divide the traffic further for particular dashboards.
- By destination: Separate personal Gmail, Microsoft consumer mail, Google Workspace, corporate domains, and other providers.
- By day and time zone: Compare UTC days for Google Postmaster Tools and Pacific days for SNDS.
- By IP: Split Microsoft counts by sending IP because the SNDS caveat is IP-specific.
- By domain: Split Gmail counts by visible From, SPF, and DKIM domains to match the selected dashboard view.
Keep volume planning separate from reputation analysis. No data in Google Postmaster Tools does not mean complaints are zero. A missing SNDS row does not mean the IP had no Microsoft traffic. In both cases, the provider withheld or lacked enough data for that view.
When the data appears and how long it stays
Provider dashboards do not update in real time. SNDS aggregates the previous Pacific day's data around midnight, and processing can take a few hours. Microsoft keeps SNDS data available for 90 days. Google Postmaster Tools uses UTC and typically updates within 24 hours, although updates can take longer.
|
|
|
|
|---|---|---|---|
SNDS | Pacific time, with daylight saving adjustments | A few hours after midnight | 90 days |
Google Postmaster Tools | UTC | Usually within 24 hours | Up to 120 days selectable |
Gmail compliance status | Rolling multi-day view | Changes can take up to 7 days | Current status view |
Timing differences that can make recent data look incomplete.
Wait for the normal processing window before diagnosing a missing day. For Gmail compliance changes, compare the status again after seven days because the dashboard uses a rolling average. Day-boundary differences also explain why internal logs and provider totals can disagree even when both are correct.
Check the clock before the threshold
A late dashboard, a UTC versus Pacific mismatch, or a rolling compliance calculation can look like low-volume suppression. Normalize logs to the provider's day before changing sending volume.
For Gmail compliance, "No data found" means the requirement lacks enough qualifying received mail to evaluate. DNS-related status reflects the configuration observed when those messages arrived, so a current DNS fix does not immediately change the displayed status.
What to check before blaming volume
Volume is only one reason these dashboards go blank. Before changing a sending plan, check authorization, domain verification, and authentication. An IP can have enough Outlook.com traffic but remain invisible without SNDS access. Microsoft requires approved reattestation to retain network access after its 10-month approval or migration period; check the expiration date in Access Control. A domain can have personal Gmail traffic but show no Postmaster data when the wrong authentication domain was added or the domain is not verified.
On a shared IP, SNDS data describes traffic for the whole IP, including other senders. The network owner or sending provider normally controls access. Ask for the relevant IP data when you cannot obtain authorization, and do not assume that your own campaign volume equals the IP total. A dedicated IP still needs authorization and sufficient Outlook.com traffic.
Start with a broad domain check. A domain health check can expose authentication and DNS issues that make provider dashboards harder to interpret. Check SPF, DKIM, DMARC, reverse DNS, and whether the actual sending source matches the expected source.
?
What's your domain score?
Deep-scan SPF, DKIM & DMARC records for email deliverability and security issues.
Then review the exact DKIM signing domain, SPF Return-Path domain, and visible From domain used by each sender. Google Postmaster Tools asks for the DKIM or SPF authentication domain during setup. Its Authentication dashboard can group results by From domain or by DKIM and SPF domains, so selecting the wrong view can look like a volume problem.
Basic DMARC record for monitoringdns
_dmarc.example.com TXT "v=DMARC1; p=none; rua=mailto:dmarc@example.com"
Do not raise volume just to create data
Increasing send volume only to populate Google Postmaster Tools or SNDS is risky. Weak list quality can create complaints, spam trap hits, and blocklist or blacklist exposure before the dashboards become useful.
- Better move: Send consistently to engaged recipients and let provider data appear when the eligible volume is sufficient.
- Bad move: Combine stale lists or unproven segments only to cross an assumed reporting floor.
Monitor authentication when provider data is missing
SNDS and Google Postmaster Tools are destination-specific and incomplete by design. They show what Microsoft or Google exposes after its reporting conditions are met. They do not replace DMARC aggregate reporting, source inventory, bounce analysis, or blocklist and blacklist monitoring.
Suped is our DMARC and email authentication platform. Its DMARC monitoring workflow groups sending sources, SPF results, DKIM results, and DMARC domain matching across providers. Its blocklist monitoring can add context when a provider panel is blank or a sending IP changes.
Suped DMARC dashboard showing email volume, authentication health, and source breakdown
Use SNDS for Microsoft IP-level signals, Google Postmaster Tools for Gmail dashboard signals, Suped for cross-provider authentication and source monitoring, and sending logs for exact daily counts. Together, those views separate low eligible volume, setup errors, reputation problems, and provider suppression.
For a single-message check, send a campaign-style message through Suped's email tester before waiting for provider dashboards. This does not replace SNDS or Google Postmaster Tools trend data. It catches authentication, DNS, content, and routing errors in an individual message.
A practical monitoring workflow
- Confirm SPF, DKIM, DMARC, reverse DNS, and TLS before interpreting provider dashboards.
- Track daily destination volume by provider time zone, sending IP, and authentication domain.
- Compare DMARC and delivery signals when a provider panel has no data.
- Investigate complaint spikes, blocklist or blacklist hits, and unknown sources promptly.
How to act on missing data
When SNDS is empty, first check whether the IP reached 100 Outlook.com-recipient messages during the relevant Pacific day. Then confirm that the IP is authorized in SNDS and that access has not expired. If those checks pass and the row remains blank, compare bounces, complaint feeds, and Microsoft-specific deferrals instead of assuming the IP is clean.
When Google Postmaster Tools is empty, check eligible authenticated mail to personal Gmail accounts for the relevant UTC day. Then check setup details: an unverified domain, the wrong SPF or DKIM domain added to Postmaster Tools, a subdomain split, or several authentication domains dividing volume. Also confirm which dashboard view is selected because its domain grouping can differ.
How a daily total splits across sending IPs
Illustrative counts: the first bar is the daily total, and the next two divide that same traffic by IP. Do not add all three bars together.
Gmail
Microsoft
Other
The sender has 490 messages in one day, but neither Microsoft IP slice reaches 100. Google receives 120 messages, but distinct recipient counts and dashboard eligibility still matter. A Gmail domain view can combine traffic across IPs; an IP split alone does not establish a separate Gmail domain threshold. Stable routing and consistent authentication domains make gaps easier to diagnose.
If data appears and then disappears, compare missing dates with send calendars and provider time zones. A paused campaign, routing change, IP pool change, DKIM change, or domain change can explain the gap. If eligible volume stayed stable, compare the result with SNDS and GPT accuracy guidance before making a major sending decision.
Views from the trenches
Best practices
Track daily personal Gmail and Microsoft consumer volume separately from campaign totals.
Group verified domains, DKIM signing domains, and visible From domains by sending stream.
Pair sparse provider panels with DMARC, bounce, complaint, and blocklist (blacklist) evidence.
Common pitfalls
Treating Gmail's 5,000-message bulk rule as a Postmaster data minimum causes errors.
Spreading low Microsoft consumer volume across many IPs can leave every SNDS row empty.
Changing domains during warmup can split the traffic that Google groups for reporting.
Expert tips
Use active-day counts because monthly totals hide provider-specific low-volume days.
Check domain verification and authentication before blaming an empty panel on volume.
Normalize logs to UTC for Google and Pacific time for SNDS before comparing daily totals.
Marketer view
Marketer from Email Geeks notes that SNDS warns mail traffic and spam data can be absent below 100 messages from an IP on a given day.
2019-09-27 - Email Geeks
Marketer view
Marketer from Email Geeks reports seeing some Google Postmaster data near 100 messages per day, but Google does not publish that number as a minimum.
2019-09-27 - Email Geeks
