Connector Improvement: Optimizely Support for Feature Experimentation Projects
AnsweredAfter migrating to Feature Experimentation from Full Stack on Optimizely, there were some endpoints that were deprecated - specifically the "Experiments" endpoint. After talking to our Optimizely support team, the "Experiments" endpoint is considered as part of the legacy API and is not longer supported going forward, except for the "Get Experiments Results" endpoint.
As a result of this deprecation, we lose important information, such as being able to sync a list of Experiments, Experiment variation, and other Experiment data.
Our Optimizely support team recommended that instead of using "Experiments", the "Flags" endpoint would be a good alternative since this endpoint retrieves the full details of experiments attached to experiment rules.
In the current state of the Optimizely connector, if teams/customers migrate over from Optimizely Full Stack to Optimizely Feature Experimentation, their syncs would no longer be obtaining experiment details.
Optimizely Documentation of its current API - https://docs.developers.optimizely.com/feature-experimentation/reference/feature-experimentation-api-overview
-
Official comment
Hi Rich,
Thanks for letting us know about this - and apologies for the delayed response.
We've added this to our roadmap. If there's any additional context or specific endpoints you'd like us to prioritize, happy to hear it. Otherwise I'll keep you updated here as we make progress.
Thanks,
Abdul
Please sign in to leave a comment.
Comments
1 comment