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.

ADD FEEDBACK

All feedback

Showing 1766

Timekeeping

Need to allow team members to add time entries for all work on projects for reporting purposes; would like system to close time entry access at a certain time at the end of each week.
over 1 year ago in Content Marketing / Tasks, Campaigns, and Events 0 Future consideration

Proofing & Versioning Button - More Prominent

The Pencil icon for Proofing & Versioning seems to get overlooked, often by collaborators needing to review a piece of content. I suggest a more prominent button that includes text so that it is more visible. Bonus to also include a little red...
over 1 year ago in Content Marketing / Tasks, Campaigns, and Events 0 Future consideration

Ability to rename the "Holdback"-variation (and generate a preview URL for that)

Hi! As an Optimizely editor, I would like to be able to rename the "Holdback"-variation of a personalization campaign. We now have to create an additional variation (acting as the Holdback without changes) and rename that instead. In addition, it ...
over 2 years ago in Experimentation Analytics 2 Investigating

"Exclude" from Results using the Segment dropdown (instead of only being able to "include")

Hi! It would be nice to be able to use the "Segment"-dropdown in the "Results"-view of an experiment/campaign in such a way that we're able to choose certain items/options on which to exclude/filter from the results. At this moment, it is only pos...
over 2 years ago in Experimentation Analytics / Results Page 3 Investigating

Filter active audiences on GET Audiences API & Remove an audience

Hi! As an Optimizely editor, it would be nice to be able to remove an audience. Archiving is not enough, as archived audiences are also returned in the GET Audiences API (see https://library.optimizely.com/docs/api/app/v2/index.html#operation/list...
over 2 years ago in Web Experimentation / APIs 4 Future consideration

Unique User Identifier

We need to find an element or variable that we can use to uniquely identify the ContentOne users. The best value would be an email address as this is always completely unique for everyone. However, it can also be something else like a company spec...
over 1 year ago in Content Marketing / Miscellaneous 0 Future consideration

Improve possibilities to group larger quantities of items under the same node without affecting the URL segment

I want to be able to group content in "buckets" without affecting the URL. Container pages have been used, but this is not ideal since they add a URL segment and we want to try and avoid to remove this by tweaking into some central parts of routin...
about 4 years ago in Content Management / Editing 0 Future consideration

Significance notifications

Customer wanted notifications when a test hit significance instead of having to check all the time
over 2 years ago in Experiment Collaboration and Management / Notifications 0 Planned

Track changes on briefs

Brief templates should have a tracked changes/review feature on the toolbar.

Rewrite CustomerContext to a service with interface

I would be happy to see the CustomerContext class turned into a class with an interface, and no usage of the CustomerContext.Current singleton. This way it can be overwritten or intercepted for customization. In the same way, the logic of Mediacha...
over 1 year ago in Customized Commerce / Customer Services 1 Future consideration