How does Chrome blocking mixed content affect Salesforce Marketing Cloud email deliverability?

Email marketer from Email on Acid says that while Chrome blocking of mixed content primarily affects websites, it's important to use HTTPS for images in emails to ensure they are displayed correctly in all email clients, not just those using proxies.

Email marketer from Reddit advises ensuring all images and links use HTTPS to avoid mixed content warnings. They suggest this improves deliverability, especially as email clients become more security-conscious.

Email marketer from Litmus says that while mixed content blocking mainly impacts web pages, email marketers should use HTTPS for all email assets as a best practice. Email clients are becoming more stringent about security, so using HTTPS helps ensure consistent rendering and deliverability.

Email marketer from Email Vendor Selection says that transitioning to HTTPS for all images and links is a crucial step in ensuring email deliverability and a positive user experience. Email clients will treat unsecure emails as spam.

Email marketer from EmailGeeks points out that modern email clients, like Gmail, may complain about mixed content in messages, especially if the sender isn't in the address book. While not as critical as website issues, it's still important to ensure universal TLS links.

Marketer from Email Geeks explains that email clients like the Gmail web one don't like mixed content, especially if the sender is not in the address book. But, it's not as big a deal if it's just a tracking link that re-directs to TLS on the sender's site.

Marketer from Email Geeks explains that mixed content warnings are about images loading over http, which doesn't impact links/click tracking in emails. Also, this issue won't appear in Gmail, Yahoo, AOL, or Outlook as they use proxies to load images over https.

Email marketer from SparkPost recommends ensuring all images and links in emails are served over HTTPS. While Chrome’s blocking focuses on web pages, email clients are becoming more vigilant about security, and using HTTPS is a general best practice for deliverability.

Email marketer from EmailGeeks raises concerns about unsecured click tracking domains affecting deliverability due to mixed content warnings in Chrome. While the immediate impact on email might be lower, having an unsecured click tracking domain could still raise red flags.

Marketer from Email Geeks shares there's really no excuse for ESP not to be wrapping all of their endpoint links in TLS these days.

Email marketer from Stack Overflow says Always use HTTPS for all URLs, including images and tracking links, to prevent mixed content errors and ensure deliverability. While Chrome's mixed content blocking primarily affects web pages, email clients increasingly favor secure content, making HTTPS a best practice.

Email marketer from Mailjet stresses that using HTTPS for all links and images in your emails is crucial for maintaining good deliverability. Although Chrome's blocking primarily targets web pages, email clients are increasingly sensitive to security, making HTTPS essential.

Expert from Email Geeks provides a detailed checklist for potential mixed content issues in SFMC: (1) Account Settings - look for a portfolio base that's https. (2) Landing Pages - update/convert old style pages to cloudpages. (3) Cloud Pages - ensure no links point to http versions. (4) Landing Pages/Cloud Page - ensure all images are https. (5) Hand-coded emails - ensure all images are https and upgrade http links to https if available.

Expert from Word to the Wise explains that while Chrome's mixed content blocking primarily targets web pages, it's crucial to use HTTPS for images in emails to maintain deliverability. Email clients may block or warn users about insecure content, impacting engagement.

Documentation from SFMC explains the importance of having a secure (HTTPS) portfolio base URL in Account Settings. This ensures that all hosted content, including images and landing pages, is served over HTTPS, preventing mixed content warnings.

Documentation from Mozilla Developer Network defines mixed content as when HTTPS sites load HTTP resources. Modern browsers block mixed content to protect users from security vulnerabilities. While focused on web development, it explains the underlying reason for Chrome's behavior, which can extend to how email clients handle content.

Documentation from Salesforce Help explains that mixed content warnings occur when a secure (HTTPS) page loads insecure (HTTP) resources. Chrome and other browsers block this mixed content to protect users. In SFMC, this primarily affects images and landing pages. Email content is less directly impacted, but insecure links can still trigger warnings.

Documentation from Google Developers explains that Chrome actively blocks mixed content to improve web security. This blocking affects various resource types, including images, scripts, and stylesheets. Though not explicitly focused on email, it highlights the broader push towards HTTPS and secure resources.