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 Subscribe
Status Future consideration
Product Web Experimentation
Categories Developer Experience
Created by Guest
Created on May 13, 2022

RELATED FEEDBACK

Provide a better editor for "custom javascript conditions" for the audience builder.

Hi!


As an Optimizely editor, I would like to have a better developer experience when using the "custom javascript condition" when building an audience.

Not only is the editor showing plain text while it could be an editor such as is presented when creating a custom Analytics Integration in the "Settings > Integration"-view of a Project (which has syntax highlighting, line numbers, ...), BUT also the custom javascript in the current editor for custom javascript conditions for audiences can not use the "return"-syntax. In fact, using the "return"-syntax breaks the whole condition for the audience, without even showing a warning!


Thank you in advance and please let me know if there are any questions!


With the kindest regards,

Matthias

  • Post comment
  • Optimizely
    Jett Sy
    Reply
    |     Oct 20, 2023

    Hi Matthias, this feedback has been heard and taken into account. We understand that it's painful for developers to use Optimizely's custom code editor today and plan to improve this in the near future. We'll look into adding this for next year's roadmap.

    1 reply
  • Guest
    Reply
    |     Dec 28, 2022

    Hi,


    Another request for this custom javascript editor: can we make it possible to use ES8's async await function?


    With the kindest regards,

    Matthias

  • Guest
    Reply
    |     Aug 26, 2022

    Hello,


    To add to this topic I'd like to report that console.log statements are also breaking the custom javascript condition of the audience builder. Without warning.

    In my opinion, this input field can not be changed quickly enough to an editor field with all the bells and whistles. Or at the very least, trigger warnings whenever a developer enters faulty code in this field.


    With the kindest regards,

    Matthias