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 1568

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

enable optimizely node sdk to work behind proxy

If sdk is meant to be initialised in air tight environment and you are meant to use proxy for security and audit reasons, then its impossible to do so with createInstance method from neither react nor node SDKs. Datafile wont be fetched, App will ...
12 months ago in Feature Experimentation / SDKs & Agent 0 Future consideration

Feature Flag Lifecylcle Analytics

One of my goals as an administrator of feature flags is to understand the lifecycle of our feature flags. When it was created and the various data points for it's rollout. I struggle to maintain the lifespan of our flags without alot of manual work.
over 2 years ago in Feature Experimentation / Feature Flagging Workflows 1 Future consideration

GCP Cloud Functions + Edge SDK

Since we are now on Google Cloud a customer has asked us about the possibility of Edge functions similar to AWS Lambda for GCP
11 months ago in Feature Experimentation / SDKs & Agent 0 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

Support setting userAttribute through Optimizely agent environment variable.

We have an enhancement request for https://github.com/optimizely/agent?tab=readme-ov-file#configuration-options. We want to be able to add a property or an environment variable so that we can add a key-value pair for the userAttribute mentioned in...
4 months ago in Feature Experimentation 0

Allow results metrics to measure conversions per session

Optimizely FX customers should have the option to be able to measure their conversions (and revenue) against the number of user sessions, rather than just against unique visitors. This could potentially work similarly to how Personalization Campai...
6 months ago in Feature Experimentation / Project / Account Configuration / Settings 1 Future consideration

Logger having error categorised into types

The Optimizely logger indicates different types of errors. Our client suggests to divide the different types of errors by type. Example use case: our client is currently using a Regex to identify the error messages received for the error "not in d...
over 1 year ago in Feature Experimentation / SDKs & Agent 1 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

Optimizely should use standard v3 Nuget feed.

We raised a support ticket regarding Optimizely Nuget feed v2 not being compatible with Artifactory which support the industry standard v3 feed by default. Our use case was explained that for security reasons we cannot download new nuget packages ...
over 2 years ago in Feature Experimentation 1 Future consideration