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 1796

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

Wordpress Integration - Support Gutenberg Editor

Gutenberg editor is activated by default on Wordpress new versions which means most client use it in one way or another. We need to support it in order to integrate.
over 2 years ago in Content Marketing / Integrations 0 Investigating

Supporting Custom Javascript or some inbuilt functions in the Audience Builder

We would like to be able to perform some minimal data manipulation before matching when creating audiences. Either supporting custom javascript in Audience Builder in the Full Stack version, or accommodating common Javascript or optimizely custom ...
over 2 years ago in Feature Experimentation / SDKs & Agent 0 Future consideration

Unable to adjust visibility of individual commerce pages

We are unable to adjust the visibility of individual commerce pages. Commerce pages inherit their visibility settings from their parent category, unlike CMS pages which can have their visibility changed individually. This is a big problem for us. ...
10 months ago in Content Management / Content Manager 0

Restrict design drafts and workflows

Designers need to be able to post drafts for creative review and feedback. Requestors should not be able to see that workflow, feedback or drafts until a draft is shared with them.
over 1 year ago in Content Marketing / Tasks, Campaigns, and Events 1 Future consideration

Better integration of Product Recs with CMS/Commerce

Synchronise the testing on CMS and Product Recs. For example: When a user starts a placement test on CMS, we can start the test on the Product Recs and toggle a button to sync it directly to the CMS test, or Starting a test in CMS automatically st...
over 1 year ago in Product Recommendations 0 Investigating

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

Content Expiring/Expired event in CMS

Like the PublishingContent / PublishedContent event in the IContentEvents interface, we require a content is expiring / expired event in the CMS. If any content is expiring or already expired event is available in CMS, this is quite beneficial bec...
over 1 year ago in Content Management / Technical 0