A dated release roughly monthly, all on one page. Individual items are not permalinked, so each row below cites the release it appeared in and links to that release's anchor.
3 changes·verified 2 Aug 2026·read from Release notes
SharedThe platform covers the mechanical bit. The judgement is still yours.Already handledMainstream platforms do this automatically. You can move on.
Announced
Shared
Microsoft SNDS data appears in the Deliverability Center for Amazon SES senders
What changed: For workspaces that send email through Amazon SES, Braze’s Deliverability Center now displays Microsoft SNDS metrics for dedicated sending IPs, and backfills up to 90 days of history when the feature is switched on for the workspace.
Why it matters: SNDS is the only place Microsoft tells you what it thinks of your IP — complaint rate, trap hits, filter result — and most senders never look, because it lives behind a separate registration on a Microsoft site nobody has open. Putting it in the tool people already have open is the difference between knowing and guessing. Read the scope before you celebrate: dedicated IPs, and only for workspaces on Amazon SES.
Do next: Switch it on and read the backfilled 90 days before you read anything else. If your complaint rate at Outlook was already high, the history will show you the week it started, which is usually the week something else changed.
Orphaned subscription records stopped being inherited by new profiles
What changed: Braze now manages what it calls orphaned subscription state records — subscription data held against a phone number or email address that is not attached to any user profile — to stop a newly created profile inheriting subscription state from a deleted or unrelated user. Braze files the item under SMS; its own description of the record covers a phone number or an email address.
Why it matters: Inherited subscription state is a consent bug wearing the costume of a data bug. A profile created on an address that once belonged to someone else could arrive already subscribed, and nothing in your records would explain why. Every regime that requires provable consent requires it for a person, not for a string of characters that has had two owners.
Do next: If you have ever deleted and recreated users on the same addresses — a migration, a de-duplication, a tidy-up of test accounts — spot-check a handful of those profiles for a subscription nobody gave.
The Email Open event started carrying a machine_open field
What changed: Braze’s Email Open event now generates a machine_open field value, which reports into a Machine Open metric.
Why it matters: Apple’s Mail Privacy Protection fetches images on the recipient’s behalf, so a large share of every open a platform records is a proxy server rather than a person. Until the two are separated, open rate is a number describing Apple’s infrastructure. A flag in the event stream is what lets you take machine opens out of a report, a segment or a re-engagement trigger — but the flag does nothing until somebody changes the report.
Do next: Find the segments and flows that treat an open as engagement, starting with the sunset policy. One that counts a machine open will keep mailing people who have not looked at you in a year, and will report that as success.
Only changes that touch deliverability, consent, classification or a number you report are listed. Braze ships far more than this; a builder getting a new toolbar is not a change to what is true about your programme. Missing something dated? corrections@emailrules.today.