How do I update my Gmail avatar with a logo after switching from SFMC to Braze?
Michael Ko
Co-founder & CEO, Suped
Published 20 Apr 2025
Updated 19 Aug 2025
7 min read
When you migrate email service providers, like moving from Salesforce Marketing Cloud (SFMC) to Braze, one seemingly minor detail can become a major headache: getting your brand's logo to appear correctly in Gmail. It's a common question, and many marketers find themselves scratching their heads, wondering why their carefully designed brand identity isn't showing up as expected.
The reason this can be tricky is that Gmail's system for displaying sender avatars and logos has evolved significantly over the years. What once relied on older methods, like Google+ profiles, now primarily depends on robust email authentication standards, particularly Brand Indicators for Message Identification (BIMI). Understanding this shift is crucial for ensuring your logo appears consistently for your subscribers.
Understanding Gmail's logo display mechanisms
Historically, individual Gmail users could set a profile picture that would appear next to their emails. This feature was often tied to Google+ accounts, which no longer exist. For consumer Gmail accounts, you can still update your profile picture, which acts as your avatar, by visiting your Google Account settings and changing your profile picture.
However, for businesses sending marketing or transactional emails, especially through platforms like Salesforce Marketing Cloud or Braze, the sender logo isn't controlled by a personal Google profile. Instead, it relies on sophisticated email authentication protocols that verify your sending domain. This is where BIMI comes into play as the modern solution for displaying verified brand logos.
BIMI allows organizations to display their official, trademarked logos next to their authenticated emails in supporting inboxes, including Gmail. This standard ties your logo directly to your domain's DMARC policy, providing a strong signal of authenticity. If your domain is not properly authenticated or if your BIMI record is misconfigured, your logo will not appear, or an older, cached avatar might show instead.
Why the switch from SFMC to Braze affects your logo
Switching email service providers from SFMC to Braze involves a fundamental change in your email sending infrastructure. Your emails will now originate from Braze's IP addresses and use their sending domains or your delegated sending domains configured within Braze. This transition can impact how email clients, including Gmail, recognize and display your sender information, including your logo.
Your sending domain's reputation is tied to the IP addresses it uses and its email authentication setup. When you move to a new platform, you typically need to "warm up" new IP addresses and ensure all your domain authentication records (SPF, DKIM, DMARC) are correctly configured for the new provider. A proper setup is vital for good deliverability and for Gmail to trust your emails enough to display your logo.
Even if your logo appeared correctly when you were using SFMC, the underlying technical mechanisms might have changed, or the previous display method (if not BIMI) may no longer be supported by Gmail for your new sending setup. Therefore, simply migrating your content and lists isn't enough; you must also update your domain's authentication records to reflect the change to Braze.
Old system considerations (SFMC)
Legacy methods: Might have relied on deprecated features like Google+ or cached sender identities.
Sender reputation: Established reputation with SFMC's sending IPs, which doesn't directly transfer.
Authentication setup: SPF, DKIM, and DMARC records configured for Salesforce infrastructure.
New system requirements (Braze)
BIMI adoption: Requires full BIMI implementation for verified logo display in Gmail.
New IP warming: Strategic warming of Braze's sending IPs to build trust with ISPs.
Updated DNS records: Adjust SPF, DKIM, and DMARC to reflect Braze as the new sender.
Implementing BIMI for brand logo display
To display your brand logo in Gmail after migrating to Braze, implementing BIMI is the most reliable approach. BIMI builds upon existing email authentication protocols, specifically DMARC. Your domain must have a DMARC policy enforced at quarantine (p=quarantine) or reject (p=reject). This ensures that your email sender is properly authenticated, which is a prerequisite for BIMI.
Key components of BIMI implementation
Strong authentication: Ensure your sending domain (the one in your email's "From" address) passes DMARC authentication with either Google or Yahoo Mail (Verizon Media Group) at an enforcement policy. This means SPF and DKIM must be correctly set up and aligned with your DMARC record.
Verified mark certificate (VMC): For your logo to appear in Gmail, you will need a VMC issued by a certified authority. This certificate verifies that your organization has the legitimate right to use the trademarked logo. Without a VMC, Gmail will not display your logo via BIMI.
SVG logo: Your logo needs to be in a specific Scalable Vector Graphics (SVG) format, meeting certain specifications, to be included in the BIMI record. For guidance on how to validate your BIMI SVG and certificate, see our detailed guide.
BIMI DNS record: Finally, you publish a BIMI TXT record in your DNS that points to your SVG logo and, if applicable, your VMC.
This comprehensive setup not only helps display your logo but also enhances your overall email security and deliverability. You can learn more about how to set up BIMI and Google Promotion Tab logos, including troubleshooting SVG issues.
Troubleshooting and considerations after migration
After implementing BIMI, it's not uncommon for the logo not to appear immediately. Several factors can affect its display. Gmail, like other email clients, might take some time to fetch and cache the new BIMI record. DNS propagation delays can also mean it takes up to 48 hours for changes to fully update across the internet.
If your logo still isn't showing, double-check your DMARC reports. Issues with DMARC alignment, even after switching from SFMC to Braze, can prevent BIMI from working. Make sure your DMARC policy is at enforcement (p=quarantine or p=reject) and that your SPF and DKIM records are correctly configured for Braze and passing alignment checks. You can check why your BIMI logo is not showing in Gmail if you're facing issues.
Remember that Gmail's display of brand logos can also be influenced by user engagement and sender reputation. Even with perfect BIMI setup, if your emails consistently land in spam or users mark them as unwanted, Gmail might opt not to display your logo. Maintaining strong sender reputation with Braze is critical, which involves sending relevant content, managing list hygiene, and avoiding excessive bounces or complaints.
Important for brand recognition
Ensuring your brand's logo appears in the inbox is vital for increasing trust and recognition among your recipients. A visible logo helps your emails stand out in crowded inboxes, reinforcing your brand identity and potentially improving open rates and engagement. BIMI (Brand Indicators for Message Identification) provides a standardized way for email clients, like Gmail, to display verified brand logos next to sender information.
This not only provides a visual cue but also serves as a strong indicator of email authenticity, helping recipients identify legitimate emails from your brand and reducing the likelihood of them being mistaken for phishing attempts. It's an essential step for modern email marketing and security.
Bringing your brand to the inbox
Updating your Gmail avatar with a logo after switching from Salesforce Marketing Cloud to Braze is less about a simple profile picture change and more about establishing robust email authentication through BIMI. While older methods might have worked for personal accounts, the modern standard for brand logos in email relies on verified brand identity and strong DMARC enforcement.
By ensuring your DMARC policy is correctly configured for your new Braze sending environment, obtaining a Verified Mark Certificate, and publishing a valid BIMI DNS record, you can successfully display your brand's logo in Gmail. This not only enhances brand recognition but also significantly boosts trust and deliverability for your email program.
Views from the trenches
Best practices
Prioritize DMARC enforcement: Ensure your DMARC policy is set to at least quarantine or reject before attempting BIMI, as it's a fundamental requirement.
Verify VMC validity: Confirm that your Verified Mark Certificate is current and issued by an accredited certificate authority to avoid display issues.
Monitor DNS propagation: Allow sufficient time for DNS changes to propagate globally after updating your BIMI record.
Common pitfalls
Relying on old G+ avatars: Expecting personal Google+ avatars to display for bulk sends after migration is a common misconception.
Incorrect SVG format: Using an SVG file that doesn't meet BIMI's specific size and formatting requirements will prevent logo display.
Weak DMARC policy: A DMARC policy set to p=none will not enable BIMI logo display in Gmail.
Expert tips
Test rigorously: Send test emails to various Gmail accounts to confirm the logo appears as expected after setup.
Consult documentation: Refer to official Braze documentation and Google's guidelines for the most up-to-date BIMI requirements.
Maintain sender reputation: Good deliverability and a positive sender reputation are key to consistent logo display in Gmail.
Marketer view
Marketer from Email Geeks says playing with the Google avatar was doable with G+, but it has since been removed.
2020-01-07 - Email Geeks
Expert view
Expert from Email Geeks says BIMI is the future for displaying brand logos in inboxes.
Salesforce Marketing Cloud (SFMC) to 
Braze, one seemingly minor detail can become a major headache: getting your brand's logo to appear correctly in Gmail. It's a common question, and many marketers find themselves scratching their heads, wondering why their carefully designed brand identity isn't showing up as expected.
Google or 
Yahoo Mail (Verizon Media Group) at an enforcement policy. This means SPF and DKIM must be correctly set up and aligned with your DMARC record.
