Packages [expand] [collapse]
Released in version
3.1.0
3.0.0
2.6.10
2.6.9
2.6.8
2.6.7
2.6.6
2.6.5
2.6.4
2.6.3
2.6.2
2.6.1
2.6.0
2.5.12
2.5.11
2.5.10
2.5.9
2.5.8
2.5.7
2.5.6
2.5.5
2.5.4
2.5.3
2.5.2
2.5.1
2.5.0
2.4.5
2.4.4
2.4.3
2.4.2
2.4.1
2.4.0
2.3.1
2.3.0
2.2.3
2.2.2
2.2.1
2.2.0
2.1.0
2.0.0
1.2.0
1.1.0
1.0.6
1.0.5

Release notes for Optimizely updates

This topic lists Optimizely updates, delivered as NuGet packages and services. You decide which updates apply to your project.

Select a product, package, or service in the left menu, and then select one of the following filters from Item type and click Filter.

  • Bug. Display bug fixes.
  • Critical bug. Display only critical bug fixes.
  • Feature. Display only new features (all features).
  • UI Feature. Display only end-user (user interface) features.

Note: NuGet packages listed here may not be immediately available in the Optimizely NuGet feed.

Latest changes

Item type
Filter on date
Items/Page
Area ID Type Description Released
MAR-1258
  Add GDPR Cookie compliance using CMS APIs

CMS has built-in support for GDPR cookie compliance. This needs to be integrated into AB Testing. That is, if a user has not agreed to cookie usage, we should not allow the user to be part of a test, and cannot create cookies for that user. This is supported as documented here.
https://world.episerver.com/documentation/developer-guides/CMS/personalization/disable-visitor-group-personalization/

The solution is to call the IAggregatedPersonalizationEvaluator.Personalize and, if any of the implemented return false, the user is not included in the test, and no cookies will be created.

EPiServer.Marketing.Testing 2.5.11;
Nov 21, 2019
MAR-1253
  ABResponseFilter does not respect page encoding when injecting a script

Currently, the ABResponseFilter injects KPI scripts, assuming the page is UTF 8 only. But this is not always the case, so the class should use the encoding type container in the response.

EPiServer.Marketing.Testing 2.5.11;
Nov 21, 2019