56 results found

1. Visibility into flag usage

   Depending on the number of teams operating in FX, tech debt accumulates quickly if not managed. Help customers determine how and when to consider tech debt in their FX endeavors.

   Some customers struggle with outdated flags that have not been used in a while, but it is hard for them to determine which ones are outdated.

   Help customers understand how their users are reacting to a new feature rollout.

   5 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   New  ·  3 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Workflow approval

   Clients wants to be able to have an approval workflow before a flag or test is started. They do this because they want to ensure that someone needs to get approval before changing the configuration of a flag to ensure a second pair of eyes before changes are made (similar to approving code changes.

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Gathering Feedback  ·  0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Serve previous revisions of datafiles from Optimizely CDN

   As a web developer I need to ensure that every point in a request lifecycle uses the same version of an Optimizely datafile to ensure a page is rendered correctly. This includes:
   * edge function logic
   * serverside render
   * clientside hydration
   If there is a mismatch in Optimizely datafile versions between edge function logic and serverside render, then the incorrect decision could be used to generate a page that is saved into the CDN cache. If there is a mismatch in Optimizely datafile versions between the serverside render and the clientside hydration, then hydration mismatch bugs will occur.
   Optimizely's current recommendation seems to be for customers to serialise the datafile during the serverside render into the HTML of the page so the client side can use the same version. But this results in page bloat.
   It would be better if the edge function could tell the serverside render which revision of a datafile it used, and then for server to fetch this specific revision of the datafile from the Optimizely CDN. And similarly for the server to tell the client which revision to fetch.
   For example, given a project ID of 12345, the latest version of the datafile is served at https://cdn.optimizely.com/json/12345.json
   Optimizely could also serve previous versions of this datafile from its CDN, for example https://cdn.optimizely.com/json/12345.json?revision=6, https://cdn.optimizely.com/json/12345.json?revision=5, https://cdn.optimizely.com/json/12345.json?revision=4,

   As a web developer I need to ensure that every point in a request lifecycle uses the same version of an Optimizely datafile to ensure a page is rendered correctly. This includes:
   * edge function logic
   * serverside render
   * clientside hydration
   If there is a mismatch in Optimizely datafile versions between edge function logic and serverside render, then the incorrect decision could be used to generate a page that is saved into the CDN cache. If there is a mismatch in Optimizely datafile versions between the serverside render and the clientside hydration, then hydration mismatch bugs will occur.
   Optimizely's… more

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Research & Design  ·  0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. How long to get statistical significance

   When the platform says another 50k users to reach significance, could a date be added? E.g. it has taken 3 weeks to get to 25k so give the date in 3 weeks as the date when the 50k will be reached

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   New  ·  0 comments  ·  UX  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. "Status Last Changed" Field

   Add a "status changed" date to the FX Flags overview page. Because currently, there is a "created" and "modified" column. However, "Modified" refers to any changes, and there is no easy way to see when a status was changed, so when a rule was changed to its current state (started/paused/concluded)... it would be valuable information for the customer just within the FX UI.

   Additional context: https://jira.sso.episerver.net/browse/DHK-2914?focusedId=2087943&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-2087943

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   New  ·  0 comments  ·  UX  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Support OpenFeature

   As a developer I want to be able to use an Optimizely provider for the CNCF OpenFeature project so that I don't have to learn a vendor-specific SDK to integrate my codebase with Optimizely resulting in faster adoption of Optimizely in my applications

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Gathering Feedback  ·  0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Rule Promotion/Copy

   As a rule administrator in feature experimentation, I want to be able to move a single rule between environments without have to copy all rules from one environment to another and having those all reset to draft in the target environment.

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   New  ·  0 comments  ·  UX  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Enhanced Search Functionality in Optimizely Experimentation

   Problem:
   Currently, the search function in Optimizely Experimentation only filters by a single word, even if multiple words are entered. For example, if a user searches for “Headers for PDP”, the results only return matches for “Headers”. This limits discoverability and forces users to rely on entering very specific single keywords.

   Proposed Solution:
   Update the search functionality to apply all words entered in the query, rather than restricting results to the first word only. This way, users can perform both broad and specific searches as needed.

   Reasoning / Business Impact:
   For customers running numerous tests, Efficiently searching and reviewing experiments is critical for both ongoing analysis and future reference. A fully functional multi-word search would save significant time and improve overall usability.

   In short, this is a fundamental search capability that users expect, but it currently does not work as intended.

   Problem:
   Currently, the search function in Optimizely Experimentation only filters by a single word, even if multiple words are entered. For example, if a user searches for “Headers for PDP”, the results only return matches for “Headers”. This limits discoverability and forces users to rely on entering very specific single keywords.

   Proposed Solution:
   Update the search functionality to apply all words entered in the query, rather than restricting results to the first word only. This way, users can perform both broad and specific searches as needed.

   Reasoning / Business Impact:
   For customers running numerous tests, Efficiently searching and reviewing experiments… more

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   New  ·  1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Allow changing project target URL without deleting changes

   In order to support testing of more complicated experiments that require server side code changes, in tandem with experiment JS/CSS changes, please allow the changing of a project target URL without deleting all the experiment changes.

   RapidX already has the ability to do this (they have a button that can bypass the change deletion behavior), meaning the use case is valid and the code has already been written. I'm not sure if it's an oversight or if there is a justifiable design reason why customers cannot do the same.

   Since we control both the experiment change selectors and the server side code, we can guarantee our server side changes are deployed before moving the experiment target to production.

   This will allow us to test that the server side code changes and the selectors for the experiment are working together correctly, without needing to deploy our server side code changes all the way up to production.

   Having to deploy server side code changes all the way up to production just to QA the experiment creates unnecessary risk, extra branch management complexity, extra deployment time, and more overall deployments.

   On the experimentation side, having the selectors be deleted when moving project target URLs creates extra work and risk of losing changes .

   An alternative suggested to us by support was to run the experiment with both test and production targets from the beginning, but this creates muddy statistics because test and prod traffic will be feeding in to the same metrics.

   In order to support testing of more complicated experiments that require server side code changes, in tandem with experiment JS/CSS changes, please allow the changing of a project target URL without deleting all the experiment changes.

   RapidX already has the ability to do this (they have a button that can bypass the change deletion behavior), meaning the use case is valid and the code has already been written. I'm not sure if it's an oversight or if there is a justifiable design reason why customers cannot do the same.

   Since we control both the experiment change selectors and the server… more

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   New  ·  0 comments  ·  UX  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Folder/Organization System

    I would like the ability to create folders within projects to organize our work. This would allow users to organize work by developer or by area of the site.

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    New  ·  1 comment  ·  UX  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Audience integrations

    To enable FX personalization, be able to pull audiences from other tools.

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    New  ·  0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Built-in attributes for frontend/client SDKs

    Similar to Optimizely Web, capture basic segmentation (browser, device, ...) out of the box.

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    New  ·  0 comments  ·  SDKs  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Product Feedback: Setting up "Average Time" or "Median Time" A/B Test

    requester jake.schlack@dat.com

    Type of issue: Feature Experimentation
    Jake Schlack sent a feedback.
    Description: Good afternoon,
    My team and I would like to run an A/B test that measures the median time that occurs between two tracking events in our product.
    Based on your documentation, it looks like we can create a "value" property that tracks the time between these two events (in the second, concluding event.
    My question is: How do we then set up a "Total Value" A/B Test that looks at a metric other than counts or sums? In this case, we want to use a median, but could use average if median is not possible.
    While your "Total Value" documentation suggests that Optimizely can be used to measure "Article page load time" and other similar metrics, it does not actually show how to set these metrics up. For "Article page load time", would one set up a "Decrease in total value per visitor for [event]" metric? What measure would Optimizely actually be using to measure that decrease: sum, average, median, etc.? Is there a way to change that in Optimizely, or is that something that our tracking needs to account for elsewhere?
    Apologies if this message is confusing. Please let me know if you have any clarifying questions. Also happy to jump on a call to explain what I am trying to do.
    User email: jake.schlack@dat.com
    User id: 5lxk1PjURheCWqJ17_nhTQ
    Account: DAT Solutions
    Account id: 57bf1781-7260-d3bf-a925-74d9d65f3cf0
    https://u44077338.ct.sendgrid.net/wf/open?upn=u001.UBmjMNjeoRXVAL5fZIj9r-2BwTWSmrIurBSeJzOMyEw1fTSPxXUpbKnEl0EWfaLcdzSWgPc6aRI2qA6TrfDDxAa0EaRMsM6VPM40QaFh5K7mILVG5eOsMA7zM3-2FIA4YGxIzsDVoJzEoj5Ha24-2F1NOv3fO1B2Ty8LBcbZzCiPFeCagAnLVSFrw1M0B8vYxG9NtD6eEaH-2FBvhN10FL-2BPYCspKj6qu751-2Fm-2BakCmn3FMuNcv8rVJPLaSK-2FXSjXEbqyY5m

    requester jake.schlack@dat.com

    Type of issue: Feature Experimentation
    Jake Schlack sent a feedback.
    Description: Good afternoon,
    My team and I would like to run an A/B test that measures the median time that occurs between two tracking events in our product.
    Based on your documentation, it looks like we can create a "value" property that tracks the time between these two events (in the second, concluding event.
    My question is: How do we then set up a "Total Value" A/B Test that looks at a metric other than counts or sums? In this case, we want to use a median, but… more

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Research & Design  ·  0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Product Feedback: Rollout functionality

    requester ahmet.atasoy01.ext@bbc.co.uk

    Type of issue: Feature Experimentation
    Description: Hi,
    We are using Feature Rollout functionality and having difficulties to enable/disable the feature for QA/Dev users.
    What we would like to have is that certain audience, could disable it completely but "Everyone" could be 100%. Looked at the documentation https://docs.developers.optimizely.com/feature-experimentation/docs/target-audiences#advanced-audience-information here and saw the following statement, which we could confirm that if you have an audience that is 0%, and "Everyone" was 100% - the feature for that audience becomes 100%.
    "For example, you cannot exclude all Brazilian users by simply dialing back to 0% traffic for that audience. That is because if you turn off audience evaluation for Brazilian users, they end up in the "Everyone" audience."
    We found a workaround but not entirely happy with it. If you could please advise.
    Workaround:
    "Everyone": -> 0%
    "ACustomAttribute": NOT "disabled" -> 100%
    If that customAttribute is not set, the user gets 100%, if you explicitly pass disabled - 0%.
    It is quite confusing to set this up and explain. Is there an alternative method we could be using?
    Thank you,
    A
    User email: ahmet.atasoy01.ext@bbc.co.uk
    User id: T4-Eqg5JR3uWcHNDlumW1A
    Account: BBC Account
    Account id: 32b642b2-8d5b-03af-35c5-901d059b0888
    http://notify.aptrinsic.com/wf/open?upn=Q6elNXBfOd1okuIEgGFEjVYK-2FQeJKmhJxBg4Gdoz-2BpoHYFLIZK2l4Z3cLM28FjN4RDwRYb0Egxon8CFPw0vKwQfBKTt3Khn3069Gzd6wSySAeoX9SFMObHoJdDDApgFQ4xTsg-2FH9Jd97G7c6ehUg1QNK-2BphD-2BWdOuTYMXzmLTk35m2vP27Kt8NZqqGjvd3bfzsW1zlK2n6JVYfqKYIhJ3fbqdZF178Ko0r1OB9nsessiDxc9nuHAed4Xuy-2FYXMQ8

    requester ahmet.atasoy01.ext@bbc.co.uk

    Type of issue: Feature Experimentation
    Description: Hi,
    We are using Feature Rollout functionality and having difficulties to enable/disable the feature for QA/Dev users.
    What we would like to have is that certain audience, could disable it completely but "Everyone" could be 100%. Looked at the documentation https://docs.developers.optimizely.com/feature-experimentation/docs/target-audiences#advanced-audience-information here and saw the following statement, which we could confirm that if you have an audience that is 0%, and "Everyone" was 100% - the feature for that audience becomes 100%.
    "For example, you cannot exclude all Brazilian users by simply dialing back to 0% traffic for that audience. That is… more

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Research & Design  ·  0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Product Feedback: Notifications Cover Up Key Action Buttons when editing feature flags

    requester chris.thompson@vividseats.com

    Type of issue: Product feedback
    Christopher Thompson sent a feedback.
    Description: When I am updating feature flags in app.optimizely.com, the cancel button is obstructed by the notification/feedback icon, and there's no way to ignore/clear the notifications.
    Can this be moved to another part of the screen so that I can clearly see which save/cancel/revert buttons are available? I would add a screenshot, but it doesn't look like this form will allow it.
    Thanks
    User email: chris.thompson@vividseats.com
    User id: vxrBU3yORCaFdlyq9VMemg
    Account: Vivid Seats
    Account id: d431d760-1424-9252-92b1-c84e8e5af9e8
    http://notify.aptrinsic.com/wf/open?upn=u001.UBmjMNjeoRXVAL5fZIj9r2FPj0g8IcH4DdrYL4fPfah4D3R0lViKImdF1fmAOOcaRyeBR6LSEO6zS6tfDSs06T0yQM35Eu1Jr879enrHEBNAHXCJKhTFnHNzUMsAFjD7gjT-2FT1kxN2GFM7nY2pW9Y87cdmadC7TDD6jFhFrzWp0VZN79SYBLgv2WzFJbvLXJhffi5iZ3LOGl1veJsJZl0VDQPDYKmVRTjee3IohbFMkW7Ku-2BBur8zt9szUI73Nyi

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Research & Design  ·  0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Product Feedback: New UI post-mortem ;-D

    requester chase@weedmaps.com

    Type of issue: Product feedback
    Chase Dutton sent a feedback.
    Description: When you guys launched the new UI, it confused the heck outta every developer at Weedmaps and we had many product incidents where a flag was misidentified as being off when it should have been on, or vice versa.
    This confusion wasn't due to any bugs in Optimizely or Weedmaps, just the new UI was visually confusing all who encountered it.
    Anyways we're doing much better now, but yea just wanted to share that feedback. If it confused 100% of our 60+ devs I'm sure it confused everyone that uses Optimizely haha. I wonder if crowdstrike uses Optimizely. LOL.
    Godspeed!
    User email: chase@weedmaps.com
    User id: CEUtJOyTTHGJSMQPxltMUQ
    Account: Ghost Management Group, LLC
    Account id: 0434dae6-7a34-6247-f1c5-e453164a7002
    https://u44077338.ct.sendgrid.net/wf/open?upn=u001.UBmjMNjeoRXVAL5fZIj9r2FPj0g8IcH4DdrYL4fPfah4D3R0lViKImdF1fmAOOcaRyeBR6LSEO6zS6tfDSs06eNmLZ8dCMCr7fnoGoioHb2HUUm61Gl1rfJMZa9Tn5hbgGiBDGe0Ristu-2FjHMBgt-2F-2FGH2k94sJeifL4bRCwztudLrCAbRMisQCr8sP7rkqgc-2BTJ03-2B5S1j2Tsuv3x520h-2BmAy-2FV2weP-2BMVHrTmUuDA6RmZGMZwfPqqnCCD2rJvQm

    requester chase@weedmaps.com

    Type of issue: Product feedback
    Chase Dutton sent a feedback.
    Description: When you guys launched the new UI, it confused the heck outta every developer at Weedmaps and we had many product incidents where a flag was misidentified as being off when it should have been on, or vice versa.
    This confusion wasn't due to any bugs in Optimizely or Weedmaps, just the new UI was visually confusing all who encountered it.
    Anyways we're doing much better now, but yea just wanted to share that feedback. If it confused 100% of our 60+ devs I'm sure it confused… more

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Gathering Feedback  ·  0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Product Feedback: Like to know more about the product on below items

    requester rineshgopal@gmail.com

    Type of issue: Feature Experimentation
    Description: Can you help to understand about the availability of features below
    1. Tracebility -
    a. Who created, updated, deleted?
    2. Scheduling
    3. RBAC
    a. Fine grained feature flag level access control
    b. Azure AD / Entra ID
    c. Domain specific segragation
    4. Export and import of feature flags
    5. Support for CI/CD ( Blue green / Canary 6. Beta Test ( User specific feature flags.
    a. Enable/Disable flags for testing in all environments, so that testers or developers can choose feature flags in both anonymous and authenticated flows
    7. Input validation on feature flag keys. like any specific naming conventions
    8. API driven - module wise, sdk support
    a. Real time UI flag update
    9. Better User experience
    10. Easy to migrate from the current setup
    11. Notification on any changes
    a. Custom alerts to the business
    b. Automated enable or disable flags based on the errors
    12. Approval flow ( workflow 13. Grouping of Feature flags ( parent-child relationship, dependency with flags
    14. Versioning of Feature Flags - Rollback
    User email: rineshgopal@gmail.com
    User id: ToHAG5qHT-eCgrjTMUDZzQ
    Account: Discovery's Account
    Account id: null

    requester rineshgopal@gmail.com

    Type of issue: Feature Experimentation
    Description: Can you help to understand about the availability of features below
    1. Tracebility -
    a. Who created, updated, deleted?
    2. Scheduling
    3. RBAC
    a. Fine grained feature flag level access control
    b. Azure AD / Entra ID
    c. Domain specific segragation
    4. Export and import of feature flags
    5. Support for CI/CD ( Blue green / Canary 6. Beta Test ( User specific feature flags.
    a. Enable/Disable flags for testing in all environments, so that testers or developers can choose feature flags in both anonymous and authenticated flows
    7. Input validation on… more

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Research & Design  ·  0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Product Feedback: Holdout Experiments

    requester ivan.njunjic@aura.com

    Type of issue: Feature Experimentation
    Ivan Njunjic sent a feedback.
    Description: I'd like to measure the effectiveness of our experimentation program through a quarter-long holdout experiment. Is there an easy, self-serve method to set up holdout groups (say, 5% of traffic that would not receive any experiment treatments during the quarter, or do we need to manage this in code via a separate flag? Thanks!
    User email: ivan.njunjic@aura.com
    User id: 3y-jacmkR2mDxmoPks63Vg
    Account id: 7e76915c-e202-a8ec-da88-eda5848b9576
    http://notify.aptrinsic.com/wf/open?upn=Q6elNXBfOd1okuIEgGFEjVYK-2FQeJKmhJxBg4Gdoz-2BpoHYFLIZK2l4Z3cLM28FjN48rQtYKJlQIVk6MrNwrilTz3oceTf5cdas3ShflIPI1NBLe8f3Ld5DuAwwhKHl3EazDUY6TP0JiEFq9GTDqeeJAT26dbbGSrZnzvQKBlYSviT35S8fQKPcHicRTQoGa4PU2MCDHNoxB-2BDxYsgBTJVnmqJ0NUeW43gFOgy0-2FNwQpr6bu1L3nCReD03QxBYZGIP

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Gathering Feedback  ·  0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Product Feedback: Experiment API, whitelist/allowlist

    requester ivan.kucheriavenko@printify.com

    Type of issue: Feature Experimentation
    Ivan Kucheriavenko sent a feedback.
    Description: Hello!
    We use in Full Stack project API to update a whitelist - https://docs.developers.optimizely.com/full-stack-experimentation/reference/update_experiment
    This API is not available in Feature Experiment - https://docs.developers.optimizely.com/feature-experimentation/reference/experiments
    Could you please advise if there is a possibility to manage allowlist in Feature Experiment via API?
    Thank you!
    User email: ivan.kucheriavenko@printify.com
    User id: ZwTZutqQSxS-pFtGogihmA
    Account: Printify, Inc.
    Account id: cb9a320a-43ad-02f0-0cf2-6b972153b9ad
    http://notify.aptrinsic.com/wf/open?upn=Q6elNXBfOd1okuIEgGFEjVYK-2FQeJKmhJxBg4Gdoz-2BpoHYFLIZK2l4Z3cLM28FjN4gMdnLml0HMdUs1OuWnMIriGQp81KpODHwPTjdlqY9yxnE5px8uoxtnut6NM2wrj6w-2BKpHaYI9bY3GQXGwciIXD1BMoYxyBN1oKEP9O0k-2BA-2FyyJmSdyG0YnSb2UKZYzqBMpg9-2FIzj-2BCBFZlx-2F1fh16CqJVbK8o132ovJFgYjapSvUnypIQCBip3kAcUmJsvYU

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Research & Design  ·  0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Option to change the variants order in Flags

    In Flags, it is not possible to change the order of variants and have a different "Baseline" variation by default in the Results Page.
    Regardless the possible workaround (change the baseline variation from the results page, the proper behaviour would be to being able to switch the order of the variants (and so decide what the default "Baseline" variant is directly in the Flags Page.

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Gathering Feedback  ·  0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating