Overview

Every time an event is logged by the Data Tracking Interface Asset, a data point is created. This data point is then forwarded to the Intuiface Analytics Data Hub. If this data point is processed by the Hub - i.e. made available for use in charts and/or forwarded to third-party tools via connectors - then it will be counted against a Platform plan storage limit.

• 28-day Trial
  Equivalent to the storage limit for Platform Enterprise with one Player. See the section below for details.
• Active Platform subscription
  Equivalent to the storage limit for the active Platform plan tier, a limit that depends on the number of Players in the account.

Data point processing can be turned on and off. Data points sent from Player to the Data Hub are NOT counted against a Platform plan storage limit. It is only if the data point is processed by the Data Hub that it gets counted against the limit. For additional background:

• How a data point is created.
• How data point processing can be stopped.
• How a data point is structured.

How to generate a data point

[NOTE: A data point does not count against a Platform plan's storage limit until it is processed by the Data Hub. This section describes how a data point is created in Composer, not how it is processed.]

Data points are created through the use of the Data Tracking Interface Asset. Creation can occur in one of four ways:

1. Each time the Log Event action is triggered. A Log Event action comprised of multiple parameters is still considered one data point. You decide when to call the Log Event action. For example, every time an image is touched, a video is played, a scene is visited, a form is completed, and so on.
2. Every time an experience is started or stopped. These two data points are generated automatically by Intuiface. ever, you can choose to prevent these events from being logged.
3. Every time a scene is entered or exited. These two data points are automatically generated for each scene by Intuiface. However, you can choose to prevent these events from being logged.
4. Every time a session is started or stopped. You decide whether and when to start/stop a session.

Example scenario

Let's say you have an experience. In it are two scenes, an Intro scene and a Video scene. The video scene contains five videos. You've configured the videos so that when any one of the videos is played, a Log Event action is called.

• Experience is run.
  Two data points are created:
  • Experience Started is automatically logged.
  • Scene Entered is automatically logged for the Intro scene.
• Visitor approaches and touches the Intro scene, causing navigation to the Video scene.
  Two data points are created.
  • Scene Left is automatically logged for the Intro scene with a value for Elapsed Time.
  • Scene Entered is automatically logged for the Video scene.
• Visitor plays video #3.
  One data point is created.
  • Log event action identifies that the 3rd video was run.
• Visitor walks away. After a predetermined time, the experience automatically returns to the Intro scene.
  Two data points are created.
  • Scene Left is automatically logged for the Video scene with a value for Elapsed Time.
  • Scene Entered is automatically logged for the Intro scene.
• After some time, you stop the experience.
  Two data points are created.
  • Scene Left is automatically logged for the Intro scene with a value for Elapsed Time.
  • Experience Stopped is logged with a value for Elapsed Time.

Platform Plans and their data point storage limits

NOTE

• 28-day Trial
  Equivalent to the storage limit for Platform Enterprise with one Player. See below for details.
• Active Platform subscription
  Equivalent to the storage limit for the active Platform plan tier, a limit that depends on the number of Players in the account. See the table below.
• In both cases, Composer-generated data points are also counted against the storage limit.

The following are the various Platform plans and their associated data point limits.

Essential	2k data points of storage per Player in the account. As Platform Essential is limited to two Players, the max data point storage limit for Essential is 2 Players x 2k data points per Player -> 4k data points. This is a limit for the account as a whole. Individual Players are not limited to 2k data points each.
Premier	10k data points of storage per Player in the account. If the account has 10 Players, that would translate into a 100k data point storage limit. This is a limit for the account as a whole. Individual Players are not limited to 10k data points each.
Enterprise	30k data points of storage per Player in the account. If the account has 10 Players, that would translate into a 300k data point limit. This is a limit for the account as a whole. Individual Players are not limited to 30k data points each.
28-day Trial	30k data points of storage - similar to Platform Enterprise. Trials are typically limited to a single Player.

 

NOTE:

• If you hit your Platform plan limit, the oldest data points will be removed from the Data Hub as new data points are added. Remember, you can export data points for offline storage and then delete those data points you no longer require.
• Additional Analytics data point storage - raising your Platform plan limit - can be purchased online.

Keeping track of your data point limit and consumption

At any time, visit the Analytics Data console to see the number of data points stored vs. your storage limit.

Stopping data point processing

Analytics gives you the ability to prevent the processing of collected data, meaning collected data will not be made available for analysis.

There are two options for pausing data point processing

• at the account level
  Best used to prevent collection during periods of installation testing, where the data does not accurately reflect real use.
• on a per-Player basis
  Best used to limit processing to those devices for which you are interested in data collection.

Stopping data point processing at the account level

In the upper right of the Analytics Data console is a slider labeled "Data point processing". Turn it off to stop data point processing on the Hub.

• OFF: Data points forwarded from Composer and Player to the Analytics Data Hub will not be processed. As a result, those data points will not be accessible in any chart or via any connector.
• ON: Data points forwarded from Composer and Player to the Analytics Data Hub will be processed. As a result, those data points will be accessible in any chart or via any connector.

Notice that regardless of whether processing is set to ON or OFF, Composer and Player will continue to send data points to the Data Hub. The only way to prevent data transfer from Composer and Player to the Data Hub is to either call the "Pause logging" action of the Data Tracking Interface Asset or to remove that interface asset completely from the experience. This has to be done for each and every instance of the running experience.

Stopping data point processing on a per-Player basis

Head to the Player Dashboard, select a Player, and look for the "Data Point Processing" toggle.

Each individual Player has its own toggle switch.

Deleting data points

You may wish to delete data points as you approach the storage limit for your Platform plan. Recall that all processed data points - up to your Platform plan limit - are stored on the Data Hub. 

Deletion will reduce the number of data points stored on the Data Hub, helping you to stay below a plan's storage limit.

1. Open the Analytics Data console.
2. Scroll to the bottom of the page
3. Apply filters to specify which data you wish to delete.
   
   
   • Date (UTC)
     By default, the From field is set to the very first day available in the Data Tracking Hub and To is set to the very last day. Change these dates to narrow your focus.
   • Include Secondary Account data points
     This checkbox will appear if you have one or more secondary accounts. Check this box if you wish your deletion to include data collected by all secondary accounts associated with the primary account used to access the Analytics Data console.
   • If Include Secondary Account data points is not selected, other filter options are available:
     • Devices
       Choose between all devices or a specific device. The device list is alphabetized. Can be combined with the Experience Name and/or Event Name fields. If including Secondary Account data points, this option will not be available.
     • Experience Name
       The name of one particular experience. Can be combined with the Devices and/or Event Name fields. If including Secondary Account data points, this option will not be available.
     • Event Name
       The name of one particular event. Can be combined with the Devices and/or Experience Name fields. If including Secondary Account data points, this option will not be available.
4. Click the Search button. The resulting number of qualifying data points will be displayed.
5. Click the Delete Data Points button that has appeared to delete the qualifying data points.

Consequences of exceeding your plan's data point limit

Exceeding your Platform plan limit will result in the removal of the oldest data points to make room for the newest data points. Your experiences will still run without any change in performance. Player (and Composer) will even continue to send data points to the Hub. The older data points will just be deleted as necessary to make room for the new data points, rendering them inaccessible via any Analytics connector or Intuiface chart.

Additional packs of 250k data points can be purchased online, raising your Platform plan storage limit. These data point packs are renewed on a monthly basis.

We'll let you know long before a limit is reached. Plus, you can export data points for offline storage and then delete those data points you no longer require. Both methods will reduce the number of stored data points.

For additional details, visit the Analytics Plans FAQ.