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

Feature Experimentation

Showing 68 of 1560

Ability to customize the logger

Sixt has thousands of users and optimizely currently logs in unstructured manner. We would like to include some custom fields for each request that comes into our servers in order to facilitate easier logging, review and optimizely logs search. As...
over 1 year ago in Feature Experimentation / SDKs & Agent 1 Future consideration

Clinets request a way to differentiate experiment state (active, paused, archived, invalid)

This has been requested via FS swift-sdk github issues (https://github.com/optimizely/swift-sdk/issues/291) Currently SDK provides an error experimentKeyInvalid which says "Experiment key ((key)) is not in datafile. It is either invalid, paused, o...
over 1 year ago in Feature Experimentation / SDKs & Agent 0 Future consideration

Batch Decisions for Bulk User IDs

Customers who desire to use Full Stack as part of their experimentation program for batch activities such as email sends, SMS, or push notifications would benefit from having a single method call in the SDK that can accept an array or list of user...
over 1 year ago in Feature Experimentation / SDKs & Agent 0 Future consideration

add filter option in the "List Experiments" endpoint

Vistaprint: Add support for filtering "archived" in the List Experiments endpoint. we already have to paginate to get all active experiments even though we only have less than 10 active, I can see this being a problem as time goes on."
almost 2 years ago in Feature Experimentation / APIs 3 Future consideration

Full Stack tests show as an ID number instead of Experiment Name.

Expected Experience Full stack tests should be reported using Flag Names and not flag id numbers on https://app.optimizely.com/v2/accountsettings/account/usage . Makes review difficult. Actual Experience (please describe what you see): For the acc...
almost 2 years ago in Feature Experimentation / Project / Account Configuration / Settings 1 Future consideration

Handle the error the occurs when copying rules from another environment

When one environment already has an experiment in it, and you try to add a new rule by copying over the rules from another environment, the UI throws a confusing error that says "Updating production ruleset for flag <flagKey> failed. {"Inval...
almost 2 years ago in Feature Experimentation / Feature Flagging Workflows 1 Future consideration

Bounce/exit metrics in Optimizely Full Stack

Bounce and exit rate are key metrics for our business, as they often reach statistical significance and are crucial for us as an indication of experiment performance. At present, these metrics are only available in the Optimizely Web product and n...
almost 2 years ago in Feature Experimentation / Other 1 Future consideration

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 2 years ago in Feature Experimentation / SDKs & Agent 0 Future consideration

When adding multiple audiences to a rule, don't default to matching ANY

When you add multiple audiences to a new rule, the default is to match ANY of the selected audiences. We always want to match ALL of the selected audiences, but our users often forget to change ANY to ALL. They put their experiment live and don't ...
about 2 years ago in Feature Experimentation 0 Future consideration

Add possibility to define Variations directly within a Rule

Currently, Variations are created separately. It should be similar to Page targeting settings in Web, which also can be defined separately and reused, OR defined directly in the experiment
about 2 years ago in Feature Experimentation / Experiment Authoring 1 Future consideration