Email industry brief: Microsoft telemetry changes, CNIL pixels, and six moves to watch (2026)

Scope

Six email-specific developments published or materially updated between 22 and 29 July 2026, ranked by direct impact on sending, compliance, and platform operations. Where the underlying event predates the article, its original date is stated.

1. Microsoft removes SNDS trap-hit counts

What changed. Microsoft says trap-hit counts will no longer appear in Smart Network Data Services reports from 22 July 2026. During the transition, reported values may differ from earlier reports and should not be treated as exact. Microsoft also deprecated the old automated-access URLs on 22 June. 1

EmailExpert reports that the wider SNDS and Junk Email Reporting Program migration is also moving complaint reports to a header-only ARF format: complainant addresses are redacted and the original message body is removed. 2

Why it matters. Trap hits were an early warning for acquisition and list-hygiene problems. With that signal gone, and less complaint data available, senders need their own identifiers in the surviving headers and must test suppression end to end. Check every SNDS/JMRP integration against live data before the next Outlook or Hotmail send.

2. France's tracking-pixel transition has ended

What changed. France's three-month transition for email tracking pixels ended on 14 July 2026. EmailExpert's 23 July follow-up says senders who informed pre-existing contacts in time may continue on an opt-out basis, but the objection control must remain separate from unsubscribe and must switch the pixel off for that recipient. Senders who missed the notice cannot rely on the transition for non-exempt tracking. 3

CNIL's 22 July FAQ says the deliverability exemption is narrow: the pixel must collect only what is strictly necessary, such as the date of the last open, and consent is required when it also collects opening time or other data. For newsletters, CNIL says the exemption depends on whether the message was explicitly requested and on all other conditions being met. 4

Why it matters. French recipients now need a real tracking preference, not a second unsubscribe path hidden in the footer. Audit pixels used for engagement scoring, send-time optimisation, and sales alerts separately from pixels used for narrow deliverability controls.

3. Gmail turns the 0.1% spam rate into an active warning

What changed. EmailExpert reports that Gmail's Postmaster Tools Deliverability analysis now issues an explicit warning when a sender's spam rate exceeds 0.1%. The article distinguishes that warning level from the 0.3% enforcement ceiling in Google's bulk-sender requirements. 5

Why it matters. A sender can be authenticated and still be telling Gmail that recipients do not want the mail. Treat 0.1% as the operating limit, add the new verdict to routine reporting, and investigate audience, cadence, and suppression changes before a programme approaches 0.3%.

4. Ireland's DPC reports a sharp rise in direct-marketing investigations

What changed. Ireland's Data Protection Commission published its 2025 annual report on 30 June. It records 275 concluded electronic direct-marketing investigations, an 88% increase from 146 in 2024, and 50 warning letters over unsolicited marketing communications. 6 EmailExpert's 23 July analysis places the figures in an email-specific enforcement context and reports 245 new complaints in the category. 7

Why it matters. Ireland is not only a major GDPR jurisdiction for large technology companies. Teams with Irish establishments should document consent, lawful basis, unsubscribe handling, and suppression logic as routine campaign controls. A warning letter is part of the enforcement path, not a substitute for fixing the process.

5. Klaviyo makes ESP provisioning part of the developer stack

What changed. On 28 July, Klaviyo announced that it is available as a provider in the Stripe Projects developer preview. A developer or coding agent can create or connect a Klaviyo account, receive scoped credentials, provision a sending domain, and manage plans from a command-line workflow. The preview is US-only, and the available services are currently free email and mobile messaging plans. 8

Why it matters. ESP onboarding is moving closer to infrastructure provisioning. That can shorten the path from a new application to its first lifecycle emails, but it also makes credential scope, domain approval, and human review part of the deployment checklist rather than an operations-only task.

6. Chrome tests email verification without sending a verification message

What changed. Chrome's 8 July origin-trial announcement describes an Email Verification Protocol that lets a browser confirm control of an address through a signed-in email provider and autofill, without sending an OTP or magic link. The trial requires a participating site to register and provide a token, and Chrome says the issuer API is still under development. 9 MarTech covered the experiment on 29 July as a possible way to reduce signup friction and improve first-party data quality. 10

Why it matters. Newsletter and account signup teams can watch this as a conversion experiment, not as a replacement for email onboarding. Chrome says the protocol verifies control of the address, not delivery of a message, so welcome, consent, and fallback flows still need to exist.

What to check before the next send

Test Microsoft complaint parsing and suppression with a known complaint, and confirm that your campaign identifiers survive in headers.
Inventory tracking pixels by purpose and recipient region, with a separate control for French recipients.
Add Gmail's 0.1% warning to reporting, then review Irish consent and suppression records alongside the same dashboard.

Email industry brief: Microsoft telemetry changes, CNIL pixels, and six moves to watch