Skip to Main Content
Customer Feedback

We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.

For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.

Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.


We are pleased to announce that beginning on Tuesday, March 25th, we are launching a new feedback experience for our customers!

The new experience should transition over seamlessly, but please be aware that short interruptions to our feedback portal may occur on March 25th between 2:30-4:30pm EDT.


All the best, your Optimizely Product Team

Categories Multi-language
Created by Guest
Created on Mar 20, 2024

Concern with the terminology "Master Language"

As an employee from USA, we have a very complicated and problematic racial legacy. The CMS platform uses the terminology "Master Language" when specifying the default language (or language of origin) for a translation. A few years back, Github decided to start replacing the terminology for "Master branches" with "Main branches" as an attempt to avoid connotations with slavery. I'm wondering whether a similar change would be possible in the CMS platform to replace "Master Language" with "Main Language", "Originating Language", or "Default Language".

Thank you for considering!