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. available for use in charts or forwarded to third party tools via connectors - then it is counted against a plan.

• Intuiface Composer - including Composer Free - can have an unlimited number of data points processed by the Data Hub.
• Intuiface Player
  • Licensed: Can have as many data points process by the Data Hub as the selected Analytics plan permits for a subscription month. See section below for details.
  • Unlicensed: Will not generate data points and thus no data point processing will occur.

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

• To understand how an event is logged, jump down to this section.
• For a look at how a data point is structured, see this article.

How to create a data point in Composer

[NOTE: A data point does not count against an Analytics plan's 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 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.

Analytics Plans and their Data Point Storage Limits

NOTE

• There is no data point storage limit for Intuiface Composer. Only Intuiface Player has a data point storage limit determined by the selected Analytics plan. See below.
• An unlicensed (free) Player will not generate data points. If you wish to use the Analytics feature with Player, Player must have an active license.

In addition to a free Analytics plan, Intuiface offers three annual Analytics plans and one monthly plan for Intuiface Player. Each is characterized by a limit on the number of data points that can be stored by the Analytics Data Hub over the life of the subscription.

NOTE:

• A "soft limit" means you can exceed the limit but a fee may be levied in light of our storage costs. We'll let you know long before a limit is reached. Plus, you can always offload old data points via one of our connectors and then delete them from the Data Hub.
• A "hard limit" means no exceptions will be made.
• In all cases, "month" refers to a subscription month, not a calendar month.

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 over the life of your subscription. Those with the Analytics Free plan can also use the console to see how many data point have been processed.

Stopping Data Point Consumption

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.

Deleting Data Points

Processed data points are stored on the Data Hub and stored data points can be deleted. You may wish to delete data points as you approach the three-year storage limit for paid Analytics plans.

Deletion will reduce the number of data points stored on the Data Hub, helping you to stay below a plan's soft storage limit. It will not help Analytics Free plan holders to reduce their data point processing count.

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
     By default, the From field is set to the very first day available in the Data Hub and To is set to the very last day. Change these dates to narrow your focus.
   • Devices
     Choose between all devices and a specific device. The device list is alphabetized.
   • Applications
     Choose which Intuiface applications you would like to focus on. For example, you may want to exclusively select Composer to delete test analytics generated while building your experience.
4. Click the Delete Data Points button.

Consequences of Exceeding Your Plan's Data Point Limit

Exceeding the hard Free data plan limit prevents the processing of additional data points by the Data Hub. Your experiences will still run without any change in performance. Player (and Composer) will even continue to send data points to the Hub. Those additional data points just won't be processed and thus won't be accessible via any Analytics connector or Intuiface chart.

Exceeding the soft paid plan limits is supported, contingent on potential payment of a storage fee. No one has come close to our storage limits so the cost of additional storage - if any - cannot yet be estimated. We'll let you know long before a limit is reached. Plus, you can always offload old data points via one of our Analytics connectors and then delete them from the Data Hub.

For additional details, visit the Analytics Plans FAQ.

Consequences of Surpassing the 3 Year Storage Limit

For each day after the 3 year storage limit has passed, the oldest day of data will be deleted.

It is recommended that you occasionally archive old data points via one of the Analytics connectors and then delete those archived data points from the Data Hub.