Disclaimer: This website requires Please enable JavaScript in your browser settings for the best experience.

HomeDev GuideAPI Reference
Dev GuideAPI ReferenceUser GuideLegal TermsDev CommunityOptimizely AcademySubmit a ticketLog In
Dev Guide

Remove dependencies on Visitor Intelligence and Profile Store

Prepare your solution for the deprecation of Visitor Intelligence and Profile Store by removing dependencies on them.

❗️

Deprecated

Visitor Intelligence and Profile Store are deprecated and no longer supported. For migration options to Optimizely Data Platform (ODP), contact your sales representative or customer success manager.

See the following to remove dependencies on Visitor Inelligence and Profile Store.

Use the following list to remove dependencies, ensuring you are prepared for the deprecation of Visitor Intelligence and Profile Store.

  • Remove visitor groups personalization based on Visitor Intelligence segments – Remove all personalization that is based on CMS visitor groups and Visitor Intelligence “Member of Segment” criteria in your CMS and Commerce solution.
  • Remove custom implementation depending on Visitor Intelligence and Profile Store – Remove the code in your solution that depends on Visitor Intelligence and Profile Store. For example, anything that depends on Visitor Intelligence and Profile Store NuGet packages or any code that uses Tracking API, Profile Store API, or Visitor Intelligence (Insight) API.
  • Uninstall packages – Uninstall the following NuGet packages in your application:
    • EPiServer.Insight.UI
    • EPiServer.Insight.Cms
    • EPiServer.Profiles.Client
    • EPiServer.Profiles.Client.Common
  • Remove configuration – Remove the following app settings for Visitor Intelligence and Profile Store in the config file of your application:
    - <add key="episerver:profiles.InsightApiBaseUrl" value="" />
      <add key="episerver:profiles.InsightApiSubscriptionKey" value="" />
      <add key="episerver:profiles.InsightApiTimeoutSeconds" value="" />
      <add key="episerver:profiles.CloudUIBaseUrl" value="" />
      <add key="episerver:profiles.TrackingApiBaseUrl" value="" />
      <add key="episerver:profiles.TrackingApiSubscriptionKey" value="" />
      <add key="episerver:profiles.ProfileStoreTrackingEnabled" value="" />
      <add key="episerver:profiles.Scope" value="" />
    
  • Do not remove general tracking configuration – Do not remove general tracking configuration and app settings like episerver:tracking.Enabled or episerver:tracking.IgnoreDNT. These may be used for tracking in other systems, like Product Recommendations.