Last updated: Sep 27 2018

Episerver Tracking Developer Guide

Tracking in Episerver is used to personalize content and product recommendations, and for segmented marketing actions.  You can track data in Episerver to any source. This section describes the core tracking functionality and APIs. 

How it works

The tracking component tracks site visitor behavior, and returns content and product recommendations, and personalized search results. Tracking also collects visitor profile information, for storing in Profile Store, and uses it with Episerver Insight for marketing segmentation. However, with the tracking in Episerver you can track data to any source outside the Episerver platform.

The tracking service includes product-specific tracking for Episerver CMS and Commerce, to support data visualization with different output platforms. To get tracking running for a site, you need to configure access to the tracking API. There are separate integration methods to connect with the tracking service, and separate native integrations depending on the product for which you are configuring tracking.

Getting started

Tracking consists of a service and a set of NuGet packages for the client-side tracking. As part of the onboarding, Episerver sends the required configuration keys and credentials to the technical contact for your project.

Installation and configuration

See Install and configure tracking about adding tracking to CMS and Commerce sites. 

Tracking API

See Tracking API about working with the generic tracking API.

Product-specific tracking configuration

Do you have feedback on this documentation? Send an email to documentation@episerver.com. For development-related questions and discussions, refer to our Forums on https://world.episerver.com/forum/