Changes to Chrome Browser: What you need to know

 In Best Practices, Current Trends, Demand Generation Best Practices, Lead Management, Marketo, News

In October 2017, with the release of Chrome 62, the browser will start showing a “Not Secure” warning on all HTTP pages containing forms. The impact on form conversions; however unknown at this time, could significantly reduce your form conversion. The warning might dissuade some visitors from entering data on your site.

This change affects all forms hosted on HTTP web pages and not only Marketo hosted landing pages. If you embed Marketo forms on a secure 3rd party page, such as your company website, then your visitor’s will not see the warning. If you use iframed Marketo landing pages on a secure 3rd party page, then your visitor’s will see the warning.

What you should do?

To avoid having Chrome display a warning message to your site’s visitors, we recommend the following:

  • To convert any HTTP pages used to gather form data to HTTPS pages.
    • If your company site is currently not secure, acquire SSL certificate for your website and contact your web hosting provider to implement the certificate on your corporate site.
    • If you currently do not have SSL Landing Page Security Package and the Tracking Link Security Package for your Marketo, contact your Marketo Sales Rep for pricing to enable SSL for your Marketo landing pages.

If you include a Marketo landing page on a secure website using an iframe, you will need to load the secure version of the landing page, otherwise the end user will get a security warning.

How Demand Spring can help?

You will experience a brief availability issue when your landing pages switch to SSL. Demand Spring can help you:

  • Pause all engagement programs during the change window.
  • After the transition, update:
    • All references to external resources within your landing pages and templates (images, stylesheets, javascript, etc.) will be updated to refer to their HTTPS counterparts.
    • HTTPS pages require that all included assets be loaded over the same protocol (or better) as the page itself, otherwise the page is not considered secure and the browser warnings will persist.
    • Re-approve all landing pages

If you still have questions about the Chrome browser update, let us know. We’d be happy to discuss it with you and to recommend solutions.

How can I learn more?

To learn more, see:

If you’re a technically inclined DIYer, you can get started using the instructions at Enabling HTTPS on Your Servers.

Resources: message/172905-re-chrome- security-warnings#comment- 172905 docs/DOC-5168-upcoming- changes-to-the-chrome-browser docs/DOC-4742-ssl- certificates-and-marketo-faq# jive_content_id_Which_vendor_ should_you_buy_your_SSL_ certificate_from_

Recommended Posts