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 1879 of 1879

Post-Submission Email Tracking Feature for Episerver Forms

Over the past few months, we've noticed an occasional issue wherein emails are not being sent after form submissions within Episerver Forms. While we understand that SMTP issues may sometimes be the cause, we believe that having a post-submission ...
11 months ago in Content Marketing / CMS + CMP Publishing 0

Make "Website" a rule type in the rules engine

Within the rules engine, user can select "customer fields" and "custom property fields" but are not able to select a website. Examples of where this would be useful: Promotions - use rules to make promotions applicable to one of many websites Prod...
almost 2 years ago in Configured Commerce / Misc. 1 Investigating

More Intuitive New Version Button

We rely heavily on versions when working on assets, but we often run into issues when users accidentally use the "+ Add Content" button, creating a new piece of content within the task, thus breaking the version history for that asset. Subsequentl...
almost 2 years ago in Content Marketing / Tasks, Campaigns, and Events 1 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.
almost 3 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 ...
almost 3 years ago in Feature Experimentation / SDKs & Agent 0 Future consideration

Enable Text Compression on the Pages

Opti configured commerce needs to enable text compression in the pages. It will improve the performance and improve the digital marketing scores.
11 months ago in Configured Commerce / Technical 5 Investigating

Abandoned Cart Reminders

Like the B2B product, can we get the ability to send abandoned cart email reminders to customers
11 months ago in Commerce Analytics 0

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 ...
almost 3 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...
almost 3 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...
almost 3 years ago in Web Experimentation / APIs 4 Future consideration