Releases: optimizely/agent
Release 4.0.0-beta
[4.0.0-beta] - May 11, 2023
New Features
The 4.0.0-beta release introduces a new primary feature, Advanced Audience Targeting enabled through integration with Optimizely Data Platform (ODP) (#356, #364, #365, #366).
You can use ODP, a high-performance Customer Data Platform (CDP), to easily create complex real-time segments (RTS) using first-party and 50+ third-party data sources out of the box. You can create custom schemas that support the user attributes important for your business, and stitch together user behavior done on different devices to better understand and target your customers for personalized user experiences. ODP can be used as a single source of truth for these segments in any Optimizely or 3rd party tool.
With ODP accounts integrated into Optimizely projects, you can build audiences using segments pre-defined in ODP. The SDK will fetch the segments for given users and make decisions using the segments. For access to ODP audience targeting in your Feature Experimentation account, please contact your Optimizely Customer Success Manager.
This version includes the following changes:
-
FetchQualifiedSegments()API has been added to the/decideendpoint. This API will retrieve user segments from the ODP server. The fetched segments will be used for audience evaluation. Fetched data will be stored in the local cache to avoid repeated network delays. -
SendOdpEvent()API has been added with the/send-opd-eventendpoint. Customers can build/send arbitrary ODP events that will bind user identifiers and data to user profiles in ODP.
For details, refer to our documentation pages:
Breaking Changes
- ODPManager in the SDK is enabled by default. Unless an ODP account is integrated into the Optimizely projects, most ODPManager functions will be ignored. If needed, ODPManager can be disabled when OptimizelyClient is instantiated. From Agent, it can be switched off from config.yaml or env variables.
Release 3.0.1
[3.0.1] - March 16, 2023
- Update README.md and other non-functional code to reflect that this SDK supports both Optimizely Feature Experimentation and Optimizely Full Stack. (#369).
Release 3.0.0
Release 2.7.1
[2.7.1] - December 20, 2022
- Add support for asynchronous
SaveusingrestUPS by settingasyncboolean value insideconfig.yaml(#350).
Release 2.7.0
[2.7.0] - April 6, 2022
- Add
UserProfileServicesupport. Out of the box implementations includein-memory,restandredis. In-memory service supports bothfifoandlifoorders. For details refer to our documentation page: UserProfileService (#326, #331). - Add more detail in documentation for sdk key. (#332)
- Add support to remove sdkKey from logs (#329).
- Update JWT library to
https://github.com/golang-jwt/jwtto fix security warnings since the previous library was no longer maintained
(#334).
Release 2.6.0
[2.6.0] - Jan 13, 2022
-
Introduce
Forced Decisionsproperty into thedecideAPI for overriding and managing user-level flag, experiment and delivery rule decisions. Forced decisions can be used for QA and automated testing purposes (#324, #325).- For details, refer to our API documentation page: https://library.optimizely.com/docs/api/agent/v1/index.html#operation/decide.
- Upgrade to use Go SDK v1.8.0. This adds support for Forced Decisions.
Release 2.5.0
[2.5.0] - Sep 24, 2021
- Add new fields (sdkKey, environmentKey, attributes, audiences, events, experimentRules, deliveryRules) to
/configendpoint (PR #322)
Release 2.4.0
[2.4.0] - March 3, 2021
-
Introduce
/decideendpoint as a new primary interface for Decide APIs, that is for retrieving feature flag status, configuration and associated experiment decisions for users (#292).- For details about this Agent release, refer to our documentation page: https://docs.developers.optimizely.com/full-stack/v4.0/docs/optimizely-agent.
- Upgrade to use Go SDK v1.6.1. This adds support for OptimizelyDecision.
Release 2.3.1
[2.3.1] - November 17, 2020
- Add "enabled" field to decision metadata structure
Release 2.3.0
[2.3.0] - November 2, 2020
- Introduce Agent interceptor plugins
- Adding support for upcoming application-controlled introduction of tracking for non-experiment Flag decisions