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 10 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

FILTER BY CATEGORY

Feature Experimentation

Showing 47 of 1007

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...
8 months ago in Feature Experimentation / SDKs & Agent 0

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 1 year ago in Feature Experimentation 0

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.
almost 2 years ago in Feature Experimentation 0 Investigating

Roku SDK

No description provided
almost 2 years ago in Feature Experimentation 0 Investigating

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...
almost 2 years ago in Feature Experimentation 0 Investigating

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...
almost 2 years ago in Feature Experimentation 0 Investigating

Option to remove percentage roll out for simpler flag management

We are exploring using Optimizely to manage critically important feature flags. Sometimes, a flag needs to be turned off instantly, out of hours or by Ops personnel eg in the event of an outage of service. In these instances, we want increased con...
3 days ago in Feature Experimentation / Feature Flagging Workflows 0

Introduce distinct lexicon to distinguish between flag status and rule status (don't use on/off for both)

It is currently confusing to use the same terminology for both flags and the rules that control flags. For example, I can have a rule that is 'flag:off' but the rule in the list shows as 'on'. Suggestion would be to have different lexicon for rule...
3 days ago in Feature Experimentation / Feature Flagging Workflows 0

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...
about 1 month ago in Feature Experimentation / SDKs & Agent 0

Normalizing metrics

Groupon experimenters are looking for ways to normalize certain metrics. We need to have an ability to change the denominator for each metric. e.g Deal View CTR (deal view/total unique impressions) Session CVR (units/session) Deal Purchase CVR (Un...
about 2 months ago in Feature Experimentation / Other 0