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 APIs
Created by Guest
Created on May 13, 2022

RELATED FEEDBACK

Filter active audiences on GET Audiences API & Remove an audience

Hi!


As an Optimizely editor, it would be nice to be able to remove an audience.

Archiving is not enough, as archived audiences are also returned in the GET Audiences API (see https://library.optimizely.com/docs/api/app/v2/index.html#operation/list_audiences for more info). This means more and more paginated requests are required to fetch all audiences when more and more audiences are inevitably created (regardless of archiving others), slowly but surely decreasing the efficiency.


Alternatively/additionally, it would be nice to be able to use a filter on that GET Audiences API so that only unarchived audiences are fetched. Otherwise, a lot of filtering is necessary by the consumers of the API (after a lot of network requests).


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


With the kindest regards,

Matthias


  • Post comment
  • Guest
    Reply
    |     Oct 31, 2023

    Hi Jett,


    Thank you for the follow-up. I can understand and agree the ability to delete (when archiving is supported) is not necessary.

    I hope the alternative I talk about in my original post is something that instead can be implemented? To be able to fetch only audiences that are not archived?


    Let me know if you want me to create a new feedback item or somehow adjust this one.

    Wkr,
    Matthias

  • Optimizely
    Jett Sy
    Reply
    |     Oct 20, 2023

    Today, we don't have the ability to delete (only support archiving) any components including audiences. I'm looking to better understand the reason for that and if it's something we can support in our stack. I'll post an update here once I know more.

  • Optimizely
    Jett Sy
    Reply
    |     Feb 22, 2023

    Hey Matthias, we haven't gotten to this yet as we're currently tackling higher priority initiatives. However, we are aware of this existing issue and will address it as soon as we can. Thanks for your valuable feedback!

  • Guest
    Reply
    |     Feb 20, 2023

    Hi,


    Any news regarding this topic?


    Also, it would be nice to be able to use a sort on the GET Audiences API so that audiences can be fetched by their name in alphabetical order (A>Z), or their creation date (NEW>OLD).

    We currently need to fetch all the audiences and then sort them in the frontend application. This makes the paginated aspect of the API useless.

    Any additional sorting possibilities are nice to have.


    With the kindest regards,

    Matthias

1 MERGED

Filter active audiences on GET Audiences API

Merged
Hi! As an Optimizely editor, it would be nice to be able to remove an audience. Alternatively/additionally, it would be nice to be able to use a filter on that GET Audiences API so that only unarchived audiences are fetched. Otherwise, a lot of fi...
over 2 years ago in Web Experimentation / APIs / Developer Experience 1 Future consideration