Johan Björnfot
Jun 1, 2018
visibility 3448
star star star star star
(3 votes)

Disable Visitor Group personalization

In EPiServer.CMS.Core.11.8.0 we released a feature (that is somewhat related to GDPR) which is the ability to turn of Visitor Group Personalization for all/some requests. We have not changed the default behavior which is that Visitor Group personalization is enabled but made it possible to control it by registering a component implementing IPersonalizationEvaluator in IOC container. The interface has a single method and looks like:

/// <summary>
    /// Signature for a component that determine if personalization should be performed or not for the current request
    /// </summary>
    /// <remarks>
    /// Registration of an implementation is done by register the implemenation in IOC container
    /// </remarks>
    public interface IPersonalizationEvaluator
    {
        /// <summary>
        /// Determines if current request should be personalized or not
        /// </summary>
        bool Personalize();
    }

There is an builtin implementation for "Do Not Track" header that can be registered. One thing to be aware of for custom implementations is that the implementation is likely to be called once for all request (we cache the request so it is only done once for each request) so any implementation should preferably be fast since it will affect the time on all requests.

Read more at Disable visitor group personalization
 

Jun 01, 2018

Comments

error Please login to comment.
Latest blogs
Automated Search & Navigation to Graph Migration with Claude Code

A Claude Code plugin that scans your S&N codebase, applies Graph SDK transformations, and validates the result. Install once, run one command. CMS ...

Connor Fortin | Jun 24, 2026

Migrating from Find to Graph: Lessons Learned from a Real CMS 13 Project

While migrating a search solution from Optimizely Search & Navigation (Find) to Optimizely Graph in CMS 13, I encountered several issues that were...

Binh Nguyen Thi | Jun 24, 2026

Optimizely: Upgrade Opti-ID and .NET 10 in CMS 12

Many Optimizely customers are planning their roadmap around a future migration to Optimizely CMS 13. As a result, upgrades such as Opti ID adoption...

Madhu | Jun 23, 2026 |

Understanding Optimizely Graph: Caching, Webhooks & Avoiding Stale Content (Optimizely SaaS CMS)

📌 Scope: This post covers Optimizely CMS (SaaS) only — using the official @optimizely/cms-sdk and @optimizely/cms-cli packages with Next.js 15. If...

Kiran Patil | Jun 23, 2026 |