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 1836

Auto-complete step if Assignee does not act on it

When a step has an Assignee and Due Date assigned, would be great to be able to configure in the workflow for a step to auto-complete if the assignee does not act on it within a certain time (i.e.: 48 or 24 hours). This would benefit the workflow ...
over 1 year ago in Content Management / Content Manager 0 Future consideration

Add support for Indexing Events

as a developer I want to be able to cache code that uses Search & Navigation in logic, and depend on masterkeys. When content is changed in the index I want to invalidate the cache (remove masterkey from cache). I want to subscribe on changes ...
over 1 year ago in Search & Navigation 3

Method to return if user is bucketed into an experiment

Create a method that returns a boolean to check if a user is in an experiment or not. Something similar to isFeatureEnabled, but for the whole experiment (for server side SDKs). I know that it could be built with some code, but having a simple isI...
over 1 year ago in Feature Experimentation / SDKs & Agent 1 Future consideration

Limit number of visitors for an experiment

Add the option to set up an absolute number of customers for an experiment or a variation. For example, an experiment supposed to be run only for the first 10000 visitors (instead of using the percentage).
over 1 year ago in Feature Experimentation / APIs 1 Will not implement

Reports in CMS (12.18), use full width for result set.

Should be no need to breaking the broken link over five lines when there are so much space to use. So my suggestion is to use more width on the result grid to make the result more readable.
over 1 year ago in Content Management / Reporting 0 Future consideration

Custom Message for Sharing

When sharing assets or tasks, including a custom message written by the sender can help provide context to the recipient.
almost 2 years ago in Content Marketing / Miscellaneous 1 Future consideration

Allow Image libraries to be copied down from production for Customer who have multiple stage environments

For customers who have multiple environments, Dev, Stage, Prod. currently when you copy down content from Production to the other 2 environments you cannot copy down media. This is a problem and causes us to have to have to spend time manually upd...
almost 2 years ago in Configured Commerce / Technical 0

Have the stats page reflect when outlier smoothing will go in effect, through a warning message

Customer: one of our experimenters paused an experiment after 80 minutes when noticing the negative impact on Average Order Value. This was caused by some outliers. When does Optimizely starts applying the outlier smoothing? Maybe some copy around...
almost 2 years ago in Experimentation Analytics / Results Page 0

Sort 'Export data' alphabetically

As an administrator I want 'Export data' to be sorted alphabetically, so that it will be easier to find which content type to export. It is difficult to find wanted content types during an export as blocks, page templates and form elements are mix...
almost 2 years ago in Content Management / Content Manager 1

Using standard "off" variation multiple times.

This feedback is on behalf of Vistaprint. - Mauricio Acebal and Lukas Vermeer. This feedback is related to the special treatment of the standard "Off" variation. Vistaprint are happy they are capable of turning off a variation without changing tra...
almost 2 years ago in Feature Experimentation / Feature Flagging Workflows 0 Future consideration