Joakim Platbarzdis
Optimizely
Apr 9, 2018
visibility 7300
star star star star star
(9 votes)

Episerver Advance launched!

It is with great joy I announce the general availability of our content personalization service Advance, enabling you to track visitor behavior across all your touchpoints, in order to use machine learning to determine the relationship between that behaviour and your content, showing the content that is most suitable for your visitors at any given time.

Image Advance overview.gif

You are now able to order Advance via your sales representative. Demo accounts are not available at this time but we will post information here once that has resolved.

Meanwhile you could have a look at the sample recommendations block that we have added to Github, and the new nuget packages EPiServer.Tracking.PageView and EPiServer.Personalization.CMS

Advance is featured in our roadmap updates, so stay tuned for upcoming functionality there!

Apr 09, 2018

Comments

Aug 11, 2018 03:29 PM

Love the animation above, is there a video with an explaination?

Arild Henrichsen
Arild Henrichsen Oct 3, 2018 07:33 AM

Any updates on the availability of demo accounts?

error Please login to comment.
Latest blogs
Unit-Level Promotion Exclusions: Updated Behaviour and Developer Guide

Introduction Since Commerce 13, Optimizely Commerce Connect has supported two modes for promotion exclusion: order-level and unit-level. Order-leve...

Viet Anh Nguyen | Oct 23, 2026

Virtual Opticon 2026: Where AI Can Improve DXP Delivery

Consider a campaign whose first draft takes ten minutes to generate but then waits five days for review. Faster drafting has helped one task. The...

Augusto Davalos | Oct 21, 2026

The Low-Level API Is Not Automatically Fast. Part 4: Counting Round Trips

The low-level Commerce DTO API is not automatically fast: counting the database round trips per imported row, and four fixes I would apply first.

Stanisław Szołkowski | Oct 21, 2026 |

The Migration Bugs That Actually Caught Us Out

The less obvious issues we hit migrating Optimizely CMS 11 to CMS 12 and .NET 8, including routing changes, JSON model binding, package dependency...

Dom Reilly | Oct 20, 2026 |