Using the Data Tracking interface asset
The Data Tracking interface asset enables experience designers to log events and access the resulting data points in virtually any analytics, marketing automation or data warehousing tool on the market.
Up to 1000 data points can processed for free in every 30 day block following its first day of use. For additional data points, a Data Tracking plan must be purchased. For more about Data Tracking plans, see this article.
On the Interface Assets panel, click the "Add an Interface Asset" button. In the Select an Interface Asset panel that just appeared, select the Data Tracking option in the Analytics category and then click the "Add" button.
Two sets of events can be automatically logged if the Data Tracking interface asset is present.
- Experience Started and Experience Stopped
- The moment an experience is run in Composer or Player, the Experience Started event is logged. The moment an experience is stopped, the Experience Stopped event is logged. (If an experience crashes, the Experience Stopped event won't be logged.)
- By defaut, these events are logged. In Edit Mode, use the Properties panel or the X-Ray panel to turn their collection on or off. At runtime, you can turn this logging on and off using actions - see below for details.
- Scene Entered and Scene Left
- The moment a scene is entered, the Scene Entered event is logged. The moment a scene is left, the Scene Left event is logged.
- By default, these events are not logged as - for a large and/or active deployment - these events could generate a large number of data points. In Edit Mode, use the Properties panel or the X-Ray panel to turn their collection on or off. At runtime, you can turn this logging on and off using actions - see below for details.
Data points representing both Experience Stopped and Scene Left have an associated Elapsed Time value measured in seconds.
The Data Tracking interface asset introduces a set of actions that can be used with any trigger. If you are unfamiliar with the concept of triggers and actions, see this article.
- Specify the trigger you will use to log an event.
For example, perhaps you used a button to play a video.
- For an action, choose the Data Tracking interface asset as the target and "Log event" as the Action.
Continuing this example, we're using the button to both play the video and log this event
- Type a name for the event in the dropdown list. All previously used Event Names will be available for reuse. You can also use binding to specify a name.
For this example we call the event "PlayedServiceOverviewVideo".
- Optionally, specify one or more parameters. Use these parameters to add additional information about the event. The value of each parameter can be entered directly or accessed via binding,
Here we use the System Info interface asset to get the city name. We gave this parameter the name "Location".
Two sets of events are predefined. These events are not automatically logged - you must log them manually - but their names are predetermined.
- Session Started and Session Stopped
- See the session section below for details.
- Logging Paused and Logging Resumed
- See the next section for details.
The Data Tracking interface asset includes the actions Pause logging and Resume logging.
- Pause logging: Disables all automatic events - with one exception - and uses of the Log event, Start new session and Stop current session actions throughout the experience.
- Even if logging is paused, if the experience is stopped, Composer/Player will still record Scene Left and Experience Stopped events.
- Resume logging: Enables all automatic events and uses of the Log event, Start new session and Stop current session actions throughout the experience.
By default, the Log event action is enabled.
Additional actions enable you to control whether Experience Started/Stopped and Scene Entered/Left should be logged..
- Include experience started & stopped events: Data points will be created every time an experience is started and stopped. That is a max of two data points per run. Logging is turned on by default.
- Exclude experience started & stopped events: Data points will not be created when the experience is stopped.
- Include scene navigation events: Data points will be created every time a scene is entered or left. This is the default state. Will apply to all future navigation events until the Exclude action is triggered.
- Exclude scene navigation events: Data points will not be created whenever a scene is entered or left. Will apply to all future navigation events until the Include action is triggered.
The Data Tracking interface asset includes actions enabling the identification of a session. A "session" is a collection of events associated with a single, shared context. It could be a user, a time of day, a sales pitch, etc.. By identifying sessions you can identifying patterns across multiple sessions, patterns that can have business relevance.
For details about working with sessions, see this article.
- Unlicensed Players will not generate data points. This includes the share-by-URL feature: if a license is not granted, Player will run unlicensed and will not generate data points.
- Exception: Composer's Play Mode will generate data points even if Composer Free is being used.
- A compression rate of 98% is applied prior to data point transfer from Composer/Player to the IntuiFace Data Tracking Hub.This not only speeds data transfer but it minimizes the consumption of data plan limits imposed by 3G/4G service providers.
- If an experience crashes, data points collected over the previous 60 seconds could be lost.
- Data transfers from Composer and Player to the Data Tracking Hub occur over HTTPS.
- Nothing prevents you from collecting confidential information. Be careful about who has access to your collected data points.