After  creating a personalization segment and personalized widgets when trying to "View as" that segment in the Personalization console, it doesn't work the personalized content is not showing. Its the default non-personalized content.

 

A client-side problem caused by script conflicts. Conflicts between the Personalization console scripts and the scripts loaded on the page/page template of the page being previewed.

The scripts block the personalization console functionality.

The solution to the problem involves two steps:

1. To identify which script/scripts trigger a conflict in the personalization console
2. To skip loading those scripts when using the personalization console.

--------------------

Step 1: Identify the problematic script. Remove components of the .cshtml file (the page template encountering a problem) and after each removal test if the personalization console starts working. With this approach keep removing scripts until the functionality of the personalization console is restored. Using this approach will be possible to identify the problematic script.

Step 2: Skip loading the problematic script/s.

Don`t load the conflicting scripts when using the personalization console. To conditionally load scripts modify the .cshtml file (being a widget template or page template) to skip loading those scripts on url: marketing/personalization/personalization-console (The url of the personalization console) 

@{
  var currentUrl = Context.Request.Path.ToString();
}

@if (currentUrl.Contains("marketing/personalization/personalization-console"))
{
  Don`t load the scripts
}
else
{
  load the scripts.
}