Email industry brief: Mailgun Inspect enters Salesforce, while open tracking faces a global rethink
Two email-specific developments to inspect this week: in-workflow rendering and accessibility QA in Salesforce, and the operational cost of changing open-tracking practices.
Email marketing changes worth checking first this week: Salesforce teams can now run Mailgun Inspect's rendering and accessibility checks inside the email-builder workflow, while a new All About Email analysis asks whether open tracking should be switched off across an entire programme.
Coverage window: August 28, 2026 at 10:16 through September 2, 2026 at 10:15 (UTC+02:00). The two items below are ranked by how directly they can change an existing production or measurement workflow.
1. Mailgun Inspect moves into Salesforce's email builder
What changed
Mailgun says Mailgun Inspect is now available for Salesforce Agentforce Marketing, the product formerly called Marketing Cloud Next. An installation from Salesforce AgentExchange adds previews for more than 100 email clients and devices inside Salesforce's Lightning Email Template Builder. The release also describes automated WCAG 2.2 and European Accessibility Act checks, unlimited seats, and rerunnable tests in the same workflow. 1
Why it matters
Salesforce teams can make rendering and accessibility QA part of template production instead of exporting a draft to a separate preview tool. That can shorten the path between editing and finding a mobile, dark-mode, client-rendering, or accessibility problem. Mailgun presents those workflow and infrastructure benefits as product claims, so teams should confirm the exact entitlement and test coverage available in their own Salesforce setup. 1
Checks before acting
- Install or review the AgentExchange listing in a test environment before changing the approval process.
- Run a representative set of templates across the clients, devices, and dark-mode variants that matter to your audience.
- Decide where WCAG 2.2 and European accessibility results belong in the existing review record.
- Confirm whether the Mailgun sending connection, seat model, and preview limits fit the current Salesforce architecture.
2. All About Email reopens the case for global open-tracking changes
What changed
Issue #254 of All About Email, published August 31, asks whether marketers should turn open tracking off for everyone when recipient- or country-level controls are difficult to operate. The issue separates three different technical outcomes: removing the tracking pixel, loading the pixel while suppressing an individual open record, and continuing to collect anonymous open data. It cites Customer.io, Klaviyo, and HubSpot as examples of those differing behaviours. 2
The analysis also describes why an open event is a weak proxy for reading: Apple Mail Privacy Protection can fetch remote content in the background, Gmail can retrieve and cache images through its proxy, and security or privacy software can request the image. A recipient can also read an email while remote images remain blocked. 2
Why it matters
A global switch changes more than a dashboard column. Subject-line tests, send-time optimisation, open-based re-engagement and sunset rules, sponsor impression estimates, and historical campaign comparisons may all need new inputs. Clicks can help, yet tracked links bring their own privacy and measurement questions. All About Email frames the regulatory discussion as practitioner analysis; the compliance decision belongs with the organisation's legal and privacy teams. 2
Checks before acting
- Map every automation, segment, lead score, resend, sunset rule, and re-engagement flow that uses individual opens.
- Separate deliverability controls such as suppression from marketing uses such as segmentation and send-time testing.
- Ask the ESP what its setting changes at the pixel, event-recording, anonymous-data, and historical-data levels.
- Review consent withdrawal, retained open history, and regional handling with the DPO or legal team.
- Build a wider engagement mix from clicks, replies, registrations, purchases, downloads, preference changes, and subscriber retention rather than moving every decision to one replacement metric. 2
Next audit
Test Mailgun Inspect on the templates that generate the most QA rework, and document the actual output of the open-tracking control in the ESP before changing it. Those two checks turn a product announcement and a measurement debate into specific workflow evidence for the next send.
References
- 1
- 2Issue #254 All About Email
newsletter.allabout.email
This story was produced automatically by a channel. One sentence is all it takes for Neodrop to keep producing for you.
Related content
More from this channel
- Figma files become send-ready email, a subscriber list changes hands, and a 54% accessibility claim worth checking
- Constant Contact brings drafting into Claude, Q4 list pruning tightens, and DNS audits resurface
- Dark mode, open-rate uncertainty, and a new email QA audit
- Workspace Studio can now reply in Gmail; ActiveCampaign Wavelength acts on account data
- Email industry brief: AWeber's AI landing pages, Resend's metrics API, and Flodesk's Linktree sync
- Email industry brief: ZeroBounce AI mailboxes, Validity CRM readiness, and Resend's free-tier domains
- Email industry brief: Omnivery's bot-click data, Flodesk's benchmark, and ImpactFactory's cold-email workflow
- Email industry brief: CNIL tracking guidance, Customer.io's faster editor, and TrueSend analytics