TLS encryption for CDN traffic in Optimizely

  • Updated
This topic describes how to:
  • QA and debug Optimizely Web Experimentation experiments and campaigns
  • Check goal firing with the network console

Optimizely Web Experimentation uses Transport Layer Security (TLS) for 100% of its CDN traffic to protect against Man In The Middle attacks and meet customers’ compliance requirements. This article provides an overview of how Optimizely manages the security and performance aspects of TLS.

Performance and security

Optimizely Web Experimentation acts to minimize the impact of TLS on both CPU and performance. For more details, visit the article on TLS has exactly one performance problem: it is not used widely enough.

Optimizely Web Experimentation TLS encryption is highly secure, maintaining an A grade from SSLLabs.


Optimizely Web Experimentation's CDN will send the HSTS header. This header will inform clients to connect to over HTTPS regardless of whether it is using the http:// or https:// URL. Performance impact should be negligible, due to the TLS optimizations in use (described at


Customers who have PCI-enabled accounts and load their assets from have all of their assets served over TLS.


Ciphersuites are reviewed at least annually and updated to address security risks and meet PCI compliance requirements for TLS.

Opting out of TLS

Optimizely Web Experimentation has an alternative CDN available at for customers who wish to opt-out of TLS. This domain will point to Optimizely Web Experimentation's same primary CDN but will not send the HSTS header. To transition to this CDN, change your // URLs to point to // Optimizely will commit to supporting this cdn-s-optional URL until at least April 30, 2019.

For information on how to change your URLS to cdn-s-optional, please see our Knowledge Base article on implementing the Optimizely Web Experimentation snippet and change <script src="// to <script src="//

If you have any questions, contact your Customer Success Manager.