BIMI
BIMI is the email standard - short for Brand Indicators for Message Identification - that lets a verified brand display its logo next to its messages in supporting inboxes (Gmail, Yahoo, Apple Mail). The promise is recognisability and trust at the inbox level. The reality is that BIMI sits on top of a deeper deliverability stack, and most companies asking about it aren’t ready for it.
What BIMI actually requires
Three things, none of them optional:
DMARC enforcement at policy quarantine or reject. Not just a DMARC record in p=none mode - actual enforcement that tells receivers to act on failures. This is where the bulk of BIMI implementations stall, because most companies’ DMARC is monitoring-only and tightening it without breaking real email is non-trivial work.
An SVG of your logo in the SVG Tiny PS profile (a specific subset, not any vector file). Hosted on your domain, referenced in a DNS TXT record.
A Verified Mark Certificate (VMC) for Gmail to display the logo. Issued by certificate authorities (DigiCert, Entrust) after they verify you actually own the trademark on the logo. Costs roughly $1,500-$2,000/year. Apple Mail accepts a Common Mark Certificate (CMC) as a cheaper alternative for unregistered marks, with smaller display impact.
What BIMI actually does for you
One thing: the recipient sees your logo in the avatar slot next to your sender name. That’s the entire user-facing benefit. It doesn’t improve deliverability. It doesn’t change spam filtering. It doesn’t move you out of the Promotions tab.
What it does is harder to measure: a small uplift in recognition, a marginal reduction in “is this real?” hesitation. Brand teams at banks, airlines, and marketplaces report subjective wins on phishing-perception reduction. Useful, real, not transformational.
The honest sequence
1. Run DMARC in monitoring mode and clean up your sending infrastructure until reports show no legitimate mail failing.
2. Move DMARC to p=quarantine, then p=reject, fixing breakage along the way.
3. Produce the SVG, get the VMC issued, configure DNS.
Steps 1 and 2 are the actual work. Step 3 is a few hours once the foundation is solid. If you’re being pitched BIMI as a quick win without anyone asking about your DMARC policy, you’re being sold icing on a cake nobody’s baked.
An example of how this plays out
I worked with a 50-person B2B SaaS whose marketing director had read about BIMI and wanted “the logo thing.” Discovery call established: DMARC at p=none, three ESPs sending under their domain, none aligned to SPF/DKIM properly, and a quarter of transactional volume would have been quarantined the moment DMARC was enforced.
Actual project: six weeks of deliverability cleanup, ESP alignment, SPF flattening, DKIM rotation, and DMARC reporting analysis before a single line of BIMI configuration was touched. SVG and VMC took half a day. Logo appeared in Gmail. Open rates ticked up roughly 1.4% - but the cleanup work was where the actual value came from: lower spam-folder rate, fewer support tickets about missing email marketing sends.
If you don’t have DMARC enforcement, BIMI isn’t your problem yet
BIMI is the visible tip of an unsexy iceberg. Get the email-auth stack right (SPF, DKIM, DMARC enforcement) for the deliverability wins. The logo is a cosmetic cap on top of that work, not a reason to start.
Related terms
- Email Marketing - the channel BIMI’s brand benefit lives inside
- Brand - the asset BIMI’s logo display is meant to reinforce in the inbox
- Email List - the asset that benefits more from underlying deliverability work than from BIMI itself
- Spam - the failure mode the email-auth stack BIMI sits on actually addresses
- Welcome Email - the high-engagement touchpoint where logo recognition matters most