Roll out BIMI across marketing and transactional email

Inventory messages, not just software subscriptions

List newsletters, password resets, receipts, account alerts and human support replies. For each stream, record its owner, platform, visible From domain, approximate business importance and a way to send a test. Include systems purchased by teams outside marketing.

A fictional retailer’s newsletter and order receipt may both use shop.example while a support tool uses a vendor-owned address. That difference matters more to the rollout than the platforms’ brand names.

Check a real message from each stream

Inspect received messages to establish how SPF and DKIM relate to the visible From domain. DKIM’s signing domain is carried in its d= value; a successful signature alone is not the same as DMARC alignment. Follow each platform’s current custom-domain setup instructions.

Record the receiver’s authentication result and the date of the test. Do not close the entire authentication task because one newsletter passes. A transactional system configured years ago can have a different sending identity and owner.

Use one rollout matrix

Add your actual asset URLs, certificate coverage and receiver test cases to the worksheet. Keep customer data out of shared screenshots and examples.

Make platform changes part of maintenance

When a team changes provider, recheck its sending identity before assuming the previous result still applies. Moving a platform can change the return path, DKIM signature or From domain even when the email template looks identical.

Keep the test matrix with your ordinary email change process. Require a fresh message sample for a newly added system and name the person who updates the inventory. This turns BIMI from a one-time marketing launch into a manageable part of email operations.