Release notes for Optimizely CMS and Customized Commerce updates

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.

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

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

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.

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.

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.

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

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

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

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