Hi,

I did run into an issue maybe similar to that, and after some investigation i found out that personalization did not work when "DNT" (Do Not Track) is in the header. I think that is reported (or maybe connected) as: Release note - AFORM-3224 (optimizely.com) (soon to be released). 

I did a quick test and removed that function and it started to work for me:

In Startup.cs

services.RemoveAll(typeof(IPersonalizationEvaluator));
services.AddScoped<IPersonalizationEvaluator, MyOwnPersonalizationEvaluator>();

And created my own implementation:

public class MyOwnPersonalizationEvaluator : IPersonalizationEvaluator
{
        public bool Personalize()
        {
            return true;
        }
}

With that it started to work... I found out that DNT is set by default in some organization controlled browsers and cannot be changed. In my case we are handeling that in another place.

Thank you Joakim for taking the time to reply.  Since our use of standard personalization and visitor groups work as expected in CMS 11, are you suggesting I can no longer rely on the out-of-the-box criterion types in CMS 12?  Your code seems to suggest a custom override is the fix.  I suspect maybe the way I presented my question may be misleading.  So...

Is there any documentation for migrating personalization and visitor groups to CMS 12?  Or is migration unnecessary?

Thanks, Kevin

We ended up contracting this in order to solve this