Packages [expand] [collapse]
Released in version
1.24.0
1.23.0
1.22.0
1.21.0
1.20.0
1.19.0
1.18.1
1.18.0
1.17.0
1.16.0
1.15.0
1.14.0
1.13.1
1.13.0
1.12.0
1.11.0
1.10.0
1.9.1
1.9.0
1.8.0
1.7.2
1.7.1
1.7.0
1.6.0
1.5.0
1.4.0
1.3.2
1.3.0
1.1.0

Release notes for Optimizely updates

This topic lists Optimizely updates, delivered as NuGet packages and services. You decide which updates apply to your project; see Installing Optimizely updates (CMS 11 and Commerce 13).

To upgrade to Content Cloud (CMS 12), see Upgrading to Content Cloud.

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
PROF-7847
  Time and count metrics for filter definitions

Marketers can now set the time or/and count metrics when creating a segment based on event filter definitions, and reuse the same filter definition in combination with the time period and the number of event occurrences.

EPiServer.Profiles.Client 1.24.0;
Mar 30, 2021
PROF-7904
  Display UI warning when the time and occurrence metric may be incompatible with a specific filter definition

An indication/warning is now displayed in the user interface when a metric is not applicable with the selected filter definition.

EPiServer.Profiles.Client 1.24.0;
Mar 30, 2021
PROF-7988
  Hide shared filter definitions that depend on Commerce events in the UI on CMS site

Only shared filter definitions compatible with currently installed products are displayed.

EPiServer.Profiles.Client 1.24.0;
Mar 30, 2021
PROF-7781
  Out of the box filter definitions for Commerce

A default set of filter definitions are now included out of the box in Visitor Intelligence. Marketers can create segments based on Commerce events and profiles without asking developers to create their own filter definitions.

EPiServer.Profiles.Client 1.24.0;
Mar 30, 2021
PROF-7089
  Improvements when deleting events by TrackId

You can delete an event or all events by specified TrackId. The deleted event is no longer available through the API or UI (until a new event with this TrackId is tracked).

After deleting the event by specific TrackId, you can track a new event using the same TrackId. You also should use newly tracked events in segments.

EPiServer.Profiles.Client 1.22.0;
Nov 06, 2020
PROF-7090
  Improvements when deleting profiles

You can delete a profile and all related events. The deleted profile events are not available anymore through API or UI.

After deleting the profile and related events, you can track a new event from the same devices. You should create a new profile when processing these new events. You also should use newly tracked events in segments.

EPiServer.Profiles.Client 1.22.0;
Nov 06, 2020
PROF-7507
  Product name updated (Insight to Visitor Intelligence)

The product name Insight was updated to Visitor Intelligence in the user interface.

EPiServer.Profiles.Client 1.22.0;
Nov 06, 2020
PROF-6635
  Upgrade CMS UI dependencies in the Visitor Intelligence UI

Episerver products need a more consistent look, so it feels like one platform when you switch between products.

EPiServer.Profiles.Client 1.16.0;
May 04, 2020
PROF-6456
  Let customers use all previously-tracked events for segmenting

You can use all previously-tracked events for segmenting visitors based on historical data.

EPiServer.Profiles.Client 1.15.0;
Apr 14, 2020
PROF-5397
  Use new Platform Navigation component

A new navigation UI is available for accessing and working in Visitor Intelligence (Insight). This UI is consistent with other Episerver products.

EPiServer.Profiles.Client 1.14.0;
Mar 10, 2020
1 2 3 Next