Release 2.1.0

[2.1.0] - November 8, 2024

Enhancements

• Batch Processing for User Profile Service (UPS): Added support for batch processing in decideAll and decideForKeys, enabling more efficient handling of multiple decisions in the User Profile Service. (#394)

• Optimized Logging: Reduced log verbosity in the Decision flow by shifting info-level logs to debug. This change will significantly reduce the volume of logs at the info level, improving readability and performance for applications with high decision-making activity. (#390)

Release 2.0.0

[2.0.0] - January 22th, 2024

New Features

The 2.0.0 release introduces a new primary feature, Advanced Audience Targeting enabled through integration with Optimizely Data Platform (ODP) (#350, #353, #354, #355).

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:

• New API added to OptimizelyUserContext:

  • FetchQualifiedSegments(): this API will retrieve user segments from the ODP server. The fetched segments will be used for audience evaluation. The fetched data will be stored in the local cache to avoid repeated network delays.

  • When an OptimizelyUserContext is created, the SDK will automatically send an identify request to the ODP server to facilitate observing user activities.

• New APIs added to OptimizelyClient:

  • SendOdpEvent(): 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:

• Advanced Audience Targeting

• Server SDK Support

• Initialize Go SDK

• OptimizelyUserContext Go SDK

• Advanced Audience Targeting segment qualification methods

• Send Optimizely Data Platform data using Advanced Audience Targeting

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.
• Minimum golang version changed from 1.13 to 1.21.0. (#369, #380)
• Module name has been changed to github.com/optimizely/go-sdk/v2.

Bug Fixes

• Logged correct error message in HTTP requests. (#374)
• Stopped all tickers to prevent goroutine leak. (#375).
• Client is closed gracefully to dispatch queued events. (#376)
• Convert warning into error log for SyncConfig failure. (#383)

Functionality Enhancement

• Github issue template is updated. (#379)
• Helper function for passing notification center is added. (#381)
• OpenTelemetry tracing support is added. (#385)
  • New ClientOptionFunc WithTracer() is added to initiate OptimizelyClient with OpenTelemetry tracer.
  • New method WithTraceContext() is added to OptimizelyClient to set the trace context before calling APIs.

Release 1.8.5

[1.8.5] - October 5th, 2023

• Fixed a bug in the HTTP Requester logging. Now correct error message is logged. (#374)

Release 2.0.0-beta

[2.0.0-beta] - April 27th, 2023

New Features

The 2.0.0-beta release introduces a new primary feature, Advanced Audience Targeting enabled through integration with Optimizely Data Platform (ODP) (#350, #353, #354, #355).

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:

• New API added to OptimizelyUserContext:

  • FetchQualifiedSegments(): this API will retrieve user segments from the ODP server. The fetched segments will be used for audience evaluation. The fetched data will be stored in the local cache to avoid repeated network delays.

  • When an OptimizelyUserContext is created, the SDK will automatically send an identify request to the ODP server to facilitate observing user activities.

• New APIs added to OptimizelyClient:

  • SendOdpEvent(): 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:

• Advanced Audience Targeting

• Server SDK Support

• Initialize Go SDK

• OptimizelyUserContext Go SDK

• Advanced Audience Targeting segment qualification methods

• Send Optimizely Data Platform data using Advanced Audience Targeting

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.
• Minimum golang version changed from 1.13 to 1.19. (#369)

Release 1.8.4

[1.8.4] - March 10th, 2023

• We updated our README.md and other non-functional code to reflect that this SDK supports both Optimizely Feature Experimentation and Optimizely Full Stack. (#366)

Release 1.8.3

[1.8.3] - October 12, 2022

New Features

• Add option to set custom http.Client on HTTPRequester. (#335)

Bug Fix

• Fixes issue with visitor where dispatch timestamp was used instead of userEvent creation timestamp. (#345)

Release 1.8.2

[1.8.2] - September 1, 2022

Bug Fix

• Add additional validation for numeric attribute types when building an event object. (#341)

Release 1.8.1

[1.8.1] - August 29, 2022

Bug Fix

• Add validation for user attribute types when building an event object. Only allow primitive types (#339)

Release 1.8.0

[1.8.0] - January 12, 2022

New Features

• Add a set of new APIs for overriding and managing user-level flag, experiment and delivery rule decisions. These methods can be used for QA and automated testing purposes. They are an extension of the OptimizelyUserContext interface (#324, #326, #328):

  • setForcedDecision
  • getForcedDecision
  • removeForcedDecision
  • removeAllForcedDecisions

• For details, refer to our documentation pages: OptimizelyUserContext and Forced Decision methods.

Release 1.7.0

New Features

• Add new public properties to OptimizelyConfig. (#322, #312)
  • SdkKey
  • EnvironmentKey
  • Attributes
  • Audiences
  • Events
  • ExperimentRules and DeliveryRules to OptimizelyFeature
  • Audiences to OptimizelyExperiment
• For details, refer to our documentation page: https://docs.developers.optimizely.com/full-stack/v4.0/docs/optimizelyconfig-go.

Deprecated

• OptimizelyFeature.ExperimentsMap of OptimizelyConfig is deprecated as of this release. Please use OptimizelyFeature.ExperimentRules and OptimizelyFeature.DeliveryRules. (#322)