Event Tracking

The administration page for event tracking enables you to quickly enable or disable collection for specific types of web events. If you deactivate an event type on this page, any rules or configurations that are defined for that type are not used. In addition, you can add rules to the Data Collection Exclusion Rules section to exclude specific types of web and mobile events from being monitored.

1. Navigate to Administration Tasks. Then click Event Tracking in Digital.

2. Activate or deactivate an event type to control data collection for that type. These are the event types that you can manage:
   • Click events: collect and monitor click events. If you disable these events, you cannot collect any information that is derived from them, such as document downloads and loading times for pages.

     CAUTION

     Make sure that links do not contain personally identifiable information (PII). The data in link URLs is stored in the database tables and is used to populate reports. Do not include any data or text in links that should not be stored in the data tables.

   • Content change: trigger events based on changes to a page's content. These events include modified page attributes, added or removed page elements, and so on.
   • Field interactions: collect and monitor values that are entered in forms before they are submitted. If you disable these events but enable Form Submit events, you collect only the field values that are submitted.
   • Form submits: collect events and values from forms when they are submitted. These events are different from Field Interaction events, which monitor values that are typed into form fields but not the final values or the Form Submit events themselves.
   • JavaScript variable change: collect and monitor changes in JavaScript variables. These events include both global variables and variables that are members of JavaScript objects.
   • Load event on URL changes: collect load events when the URL changes. This setting affects load events that are captured when the URL changes but not the page itself. Load events are always collected when the page changes.
     Note: This feature is not implemented for the deprecated version of the SAS tag (ot-all.min.js).
   • Media: collect and monitor events related to multimedia on your site. If you disable these events, you cannot monitor events in which a user starts playing a media type but does not finish it.
   Note: By default, Field Interactions and Form Submits are not enabled. If you want to collect data from these types, enable these options and review the settings on the Data CollectionForm Fields page. For more information, see Form Fields.
3. (Optional) Add rules to the Data Collection Exclusion Rules section to exclude specific types of events from being monitored. For example, you can set exclusion rules to ignore traffic from specific locations, IP addresses, or browser types.

   Be aware of these implementation details:

   • Exclusion rules apply to all events in the session.
   • Data exclusion happens on the server side rather than through the client (such as the web browser or mobile app).
   • Exclusion rules are case insensitive, and double-byte characters are not supported. If a URL contains double-byte characters, use the ASCII-encoded URL path instead.
   • The SESSION_DETAILS table contains entries that you can review for possible values to exclude.

   Here are some examples of data-exclusion rules:

   • Location Data. This example excludes data from being collected from users in London, England:

     Location Examples for Data Exclusion

     Exclusion Option	Operator	Value
     Geo Location: City	Equals	London
     Geo Location: Region/State	Equals	England
     Geo Location: Country	Equals	Great Britain

     For some locations, there might be multiple values that evaluate to the same end result. For example, São Paulo can be both the city or state in Brazil.

   • IP Address. This example excludes data from being collected from a set of users that are on a sample local area network (LAN):

     IP Address Example for Data Exclusion

     Exclusion Option	Operator	Value
     IP Address	Starts With	192.168.1

   • User Agent. This example excludes data from being collected from a set of users on the Google Chrome browser:

     User Agent Example for Data Exclusion

     Exclusion Option	Operator	Value
     User Agent	Contains	Chrome

     TipUser agent strings can vary based on the browser type, version, and so on. Use the Contains operator or a regular expression to match a known set, instead of trying to match an exact string.