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

Feature Experimentation

Showing 74 of 1827

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...
about 1 year 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...
almost 2 years 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 2 years 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 ...
about 3 years ago in Feature Experimentation 1 Future consideration

Streaming Datafiles

Offer an option to consume datafiles immediately when updated via websocket or other streaming architecture. This would enable faster updates to flags and bring us into parity with competitors.
over 3 years ago in Feature Experimentation / SDKs & Agent 0 Future consideration

Roku SDK

No description provided
over 3 years ago in Feature Experimentation / SDKs & Agent 0 Future consideration

Manage Collaborators via API

Customers wants to manage collaborators via REST api, so that they can programmatically grant permissions via their existing permissioning tool that they've created. They do this because it's far more convenient for them to manage this in a centra...
over 3 years ago in Feature Experimentation 0 Future consideration

Event tags to segment results and create metrics- Segment integration

Customers wants to create Optimizely events via Segment. They do this because they already have evnts in Segment and then data is nicely aligned. They wish that Optimizely had the option to filter results by event tags and use the atgs to create m...
over 3 years ago in Feature Experimentation 0 Future consideration

Enhance efficiency of UserProfileService with decideAll()

When calling decideAll() with a User Profile Service (UPS), the method looks up the UPS for each flag. The request is that the SDKs be updated to default to just one lookup for all flags.This will prevent unnecessary resource consumption for custo...
3 months ago in Feature Experimentation / SDKs & Agent 0

Apply Audience Automatically At The Project Level

As an experimenter I would like to be able to have an audience auto populate for an entire project. The bot filtering provided within Optimizely does not exclude additional bots that we need to remove from testing as an organization, and therefore...