This topic describes how to get started with installation and configuration of tracking for Episerver Commerce and CMS data to any source. For tracking of data to Profile Store, the Episerver Customer Data Platform, see Install and configure tracking for Profile Store.
How it works
Use tracking to provide personalized product, content and search recommendations, and to visualize data for business intelligence purposes. You can track data to Episerver Profile Store, to the recommendation service for Commerce products and CMS content, or to any business intelligence store, as described here.
As part of the onboarding for the tracking service, Episerver sends the required subscription keys and tracking URLs to the technical contact for your project. Use the keys to configure the tracking for your websites. Contact Episerver for questions regarding the onboarding process.
See Installing Episerver about installing NuGet packages for your site.
Depending on your setup (CMS/Commerce), add NuGet packages as listed below.
- EPiServer.Tracking.Core. Generic package for all tracking.
- EPiServer.Tracking.Cms. Base classes for tracking of CMS data.
- EPiServer.Tracking.PageView. Native integration for tracking of CMS data.
- EPiServer.Tracking.Commerce. Native integration for tracking of Commerce data.
The Tracking.Core package contains this:
- Interfaces to define tracking data interceptors, tracking services, tracking adapters, tracking configuration, and tracking validation.
- A default implementation of tracking service configuration, and tracking data interceptor.
- Classes representing JSON objects used for tracking.
Depending on your setup (CMS/Commerce), continue to adding tracking configuration.
- See Scopes for more information about the scope concept.
- See Tracking API about using the generic tracking API.
- See Page view tracking about configuring data tracking for a CMS site.
- See Product tracking about configuring data tracking for a Commerce site.
Last updated: Sep 27, 2018