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.

Status Already exists
Categories APIs
Created by Guest
Created on Jun 20, 2023
Merged feedback
This idea has been merged into another idea. The merged idea is not visible in this portal.

Publish variation code without required `weight` or `name` properties Merged

As Staff Engineer at Cro Metrics I work on our engineering build tools, which we use to service all of our Optimizely Web customers. I would like to be able to submit variation code to an experiment (using the https://library.optimizely.com/docs/api/app/v2/index.html#tag/Experiments/operation/update_experiment API) without having to specify the variation `name` or `weight` values. It would be ideal if I only need to specify the `variation_id` number and `actions` array in order to make code changes.
Having to specify the weight value causes issues and confusion for our team in situations where the account management team modifies the variation weight distribution (say 100% to v1) then our engineer pushes code changes to the experiment and it unwittingly overwrites the traffic distribution back to whatever we have stored along with the code (usually 50/50 split). This scenario can lead to mistakenly launching experiments with the wrong traffic allocation, costing our team (and the client) time and energy. Making the weight field optional would solve this issue by simply leaving the weight unchanged, allowing it to remain untouched with whatever value is currently set.
Additionally, and less importantly, the `name` field is also required by the API, although it's not marked as "required" in the API documentation. Trying to submit the data without the variation name returns an error. It would be ideal if we had the option to leave this value alone when making changes to the variation code.

  • Optimizely
    Jett Sy
    Reply
    |
    Jun 29, 2023

    Thanks for sending in this feedback, Andrew. I'm merging this to a similar feedback item we're received in the past that's currently under investigation.