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

SDKs & Agent

Showing 18 of 1810

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

Type check for userId in Javascript (Browser/Node) SDKs

The customer (Yuliyan Yordanov from Tesco Stores) suggested a failsafe solution to reject empty string userId upon activating/enabling an experiment/feature: "A simple check for (typeof user_id ===’string’ && user_id.length ) would fix the...
almost 2 years ago in Feature Experimentation / SDKs & Agent 1 Future consideration

JavaScript SDK handles large datafiles in a performant manner. It is possible to process large datafile initialisation on a web worker.

The javascript SDK client initialises the client form the datafile. When the datafile is large, processing the JSON takes a long time. P50 20ms and P75 already gives 70ms. This is significantly long when considering page load time. It would be ben...
almost 2 years ago in Feature Experimentation / SDKs & Agent 1 Future consideration

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

Set Seed of Experiment Allocation

It would be helpful to set the seed of traffic allocation so that you know the same user (same user ID) would be in the same variation on both experiments. Essentially the distribution of V1 vs V2 would be the same numbers (between 0-10000) in bot...
about 3 years ago in Feature Experimentation / SDKs & Agent 0 Future consideration

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