Sitecore Experience Platform

Analytics tracking

Abstract

Identify and track contacts that come to your website.

Analytics tracking enables you to identify and track contacts so you can see all their activities on your website. You can use this information gathered by tracking contacts during current and past web sessions for personalization, reporting and optimizing your website.

The analytics tracker refers to the classes in the Sitecore.Analytics assembly that you use for tracking. When a contact triggers tracked events on a website, they are stored in the tracker during the active session and then saved to the interaction in xDB when the session ends.

To enable tracking, you need to register the activities that you want to track, such as goals, outcomes, or page events. To do this, you need to associate the activity with a content item. For example, you can associate a campaign with a specific page on your website. When a contact visits this page, the campaign is triggered and recorded in the interactions for the contact.

You can enable tracking:

  • Automatically

    You can use the Content Editor to associate goals, campaigns, page events or other activities to be triggered automatically and tracked in the system.

  • Programmatically

    You can associate goals, campaigns, page events or other activities to be triggered programmatically during a web session and tracked in the system.

The Sitecore.config file has a node called tracking/untrackedPages. Sitecore does not track files that are listed in this node. By default, these files are not tracked:

<tracking>
    <untrackedPages>
      <add path="/sitecore/default.aspx" />
      <add path="/sitecore/service/error.aspx" />
      <add path="/sitecore/service/Heartbeat.aspx" />
      <add path="/sitecore/service/keepalive.aspx" />
      <add path="/sitecore/service/nolicense.aspx" />
    </untrackedPages>
  </tracking>

Files are referenced by their relative URLs. There is also a tracking/untrackedPages node in the App_Config\Include\ Sitecore.Analytics.Tracking.config file. Sitecore merges the nodes when it read the config files.

The recommended way to add files is using patch files instead of editing the config files directly. This file describes the include file patch process.

If you remove entries from the list, Sitecore starts collecting data about these pages. The list consists of "service" pages that will not produce meaningful data.

If your Sitecore installation has other pages likes this, you can add these pages to the list and avoid that they create "noise" in the reports. Examples of such pages are “keepalive” pages, or pages you use for registering system events (error, user opened email, and so forth)

You can access the list of pages that are untracked in code by using the UntrackedPages property of the Sitecore.Analytics.Configuration.AnalyticsSettings class.

During each interaction the tracker collects data on all the trackable activities of the contact and holds this data in the current session. The tracked content is held in Tracker.Current.Interaction until the session ends.

You can use data collected during tracking in several different ways:

  • Personalization

    The tracker collects activities such as pages viewed and goals triggered that you can use for personalization during the current web session.

  • Historical personalization

    The Key Behavior Cache and the Contact Behavior Profile enables you to use tracked data from past web sessions to personalize content.

  • Retrieving marketing data programmatically

    You can use tracking data to retrieve data about contacts and the activities they triggered during a session, for example, to get information about all the goals triggered during the current interaction.

    You can retrieve data programmatically for all of the following activities:

    • Page events

    • Goals

    • Campaigns

    • Outcomes

    • Contact Behavior Profile

      Note

      Page events and Goals are both triggered in the same way programmatically.

You can track the following:

Trackable data

System enabled tracking

Content Editor/Programmatically enabled

Contacts

47E1324E34AC422FAE06EE640D402624.png

Interactions

CD8F1539BF27420A92EE3DA6B2EC1A23.png

Browser information (name and version)

FAD73A383BAC40E5B3B3764F9AD3CAF0.png

Campaigns

2100A61AC241420F85606FDD250AB132.png

Channels

356C9EEBA67E4282B5403F65080AA85B.png

Engagement value

AC31A936A75F45158040A58EE820F8ED.png

Goals

EB57A3348ACC41F1A3394E4CF545FF6B.png

IP Geolocation

13987B96FE694A90BDD9A84399F1E37C.png

Multivariate tests

28E5B17989E941E789745E64194368B9.png

Operating system

0FF8B4A559C34FDB80D6F3F78863E0B8.png

Page events

7EA4466587E34FDEB78531D5CF5E9F14.png

Pages viewed

95D009328129452693F381C8997709A7.png

Profile values

51266EAD509C49C19A3128A4D3155C51.png

Referrer

DD3F153F50CF48A8BD6DB5D7C43FABE7.png

Screen height/width (where available)

5EF5EC63EC10422CA7CA2FC8130713E3.png

Search keywords

7979470859244865ACD0D477963898A7.png

Start date/time and end date/time

19258E659746499786D361496039EF0B.png

User agent

6A232959DD6F47DBAB0720C4E8B8D09B.png

Outcomes

F71CD343EAF74D9BB99EF3DE2AB9535F.png

Engagement automation states

172C4F1F2F034991A4E18A52A6DA9EE4.png

Note

The system does not track programmatically enabled items by default. You must enable tracking in the code or in the Content Editor to gather information about these items.