World is now on Opti ID! Learn more

Ronil Rangaiya
Jun 21, 2019
  28
(0 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

Please login to comment.
Latest blogs
Make Global Assets Site- and Language-Aware at Indexing Time

I had a support case the other day with a question around search on global assets on a multisite. This is the result of that investigation. This co...

dada | Jun 26, 2025

The remote server returned an error: (400) Bad Request – when configuring Azure Storage for an older Optimizely CMS site

How to fix a strange issue that occurred when I moved editor-uploaded files for some old Optimizely CMS 11 solutions to Azure Storage.

Tomas Hensrud Gulla | Jun 26, 2025 |

Enable Opal AI for your Optimizely products

Learn how to enable Opal AI, and meet your infinite workforce.

Tomas Hensrud Gulla | Jun 25, 2025 |

Deploying to Optimizely Frontend Hosting: A Practical Guide

Optimizely Frontend Hosting is a cloud-based solution for deploying headless frontend applications - currently supporting only Next.js projects. It...

Szymon Uryga | Jun 25, 2025

World on Opti ID

We're excited to announce that world.optimizely.com is now integrated with Opti ID! What does this mean for you? New Users:  You can now log in wit...

Patrick Lam | Jun 22, 2025

Avoid Scandinavian Letters in File Names in Optimizely CMS

Discover how Scandinavian letters in file names can break media in Optimizely CMS—and learn a simple code fix to automatically sanitize uploads for...

Henning Sjørbotten | Jun 19, 2025 |