Johan Björnfot
Jun 1, 2018
  3362
(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

Please login to comment.
Latest blogs
From Prompting to Production: Optimizely Opal University Cohort and the Future of Agentic MarTech

Most organizations today are still playing with AI. They experiment with prompts, test ideas in isolated chats, and occasionally automate a task or...

Augusto Davalos | Apr 28, 2026

Six Compelling Reasons for Upgrading to CMS 13

Most software updates ask you to keep up. Optimizely CMS 13 asks something different — it asks whether your digital strategy is built for a world...

Muhammad Talha | Apr 28, 2026

Optimizely CMS 13 breaking changes: GetContentTypePropertyDisplayName

When upgrading from CMS 12 to 13, resolving property display names may not work as before. Here’s what changed.

Tomas Hensrud Gulla | Apr 27, 2026 |

Accelerate Optimizely DAM Adoption: Unlocking Business Value with Metadata Bulk Import

Accelerating Optimizely DAM Adoption How a Metadata-Driven Bulk Import Utility Unlocks Real Business Value Executive Summary For enterprises runnin...

Vaibhav | Apr 27, 2026