Ronil Rangaiya
OMVPPaaS CMS Developer CertificationSaaS CMS Administrator Certification +2
Jun 21, 2019
visibility 4190
star star star star star
(3 votes)

Visitor Intelligence and Personalization - enrich and use visitor profile data

Recently I've been working with Profile Store, specifically around enriching the profile with custom behaviourable data that can then be used for content personalisation. Here's a quick overview of the implementation. 

Tracking

Profile Store is Episerver's customer data platform for storing website visitor profile and behaviour data collected by tracking. There is detailed official documentation on how to install and configure tracking for Profile Store . The simplest way to start collecting tracking data is by using the [PageViewTracking] attribute. 

Enrich Profile data

First, a look at the structure of the profile data that is captured out of the box. 

"Name" and "Info" properties will be populated with user data if your website has sign-in capability. The key property here is the "Payload" which can be used to store any custom data. 

The Profile Store API makes it easy to query and update the visitor profiles. I started with a simple Payload model and a helper service with methods to retrieve and update the profile payload.

Note in the "AddPayloadToProfile" method, I'm overwriting the profile payload property however it can be made smarter to preserve the existing payload in case you have multiple processes that update the payload.

The Profile Store adds a request cookie "_madid", which is the DeviceId and is used to retrieve the profile. 

Personalization

Once the profile has been enriched, the next step is to create custom VisitorGroups to use for personalization.

I created a VisitorGroup to use for simple value comparison. Depending on your custom data, you can create visitor groups to suit different criteria requirements.

Now you can add VisitorGroup criteria and apply to your website content accordingly

Wrapping up

Been able to push custom data to the profile using the Profile Store API opens up endless possibilities to enrich the profile data for personalization purposes. It can be as simple as pushing data captured from a Form on your website or via a data insights tool that analyses and enriches profile data for improved customer experience.

Jun 21, 2019

Comments

Marcus B
Marcus B Jun 24, 2019 12:23 PM

Nice, Ron

error Please login to comment.
Latest blogs
Surviving a Dirty Feed. Part 3: Error Handling and Event Batching

Committing a 250,000-row Optimizely catalog import row by row, returning a per-row failure report, and coalescing catalog events into one per batch.

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

Building UI Extensions for Optimizely SaaS CMS

Introduction Developers have been extending the functionality of Optimizely PaaS CMS for years using addons built in C# and deployed as NuGet...

Mark Stott | Oct 15, 2026

Cheapskate AI Translator: Because Translation Should Not Require a Second Mortgage

There is a particular kind of software project that begins with a detailed architecture document, a product roadmap, and a carefully assembled...

Linh Doan Cuu | Oct 15, 2026

Computed Fields in CMS 13 Content Contracts with Optimizely Graph

Content Contracts in Optimizely CMS 13 allow different content types to share a common structure when querying Optimizely Graph. But what if the...

Mardy | Oct 14, 2026