Data point counting and plan limits

    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 Data Tracking Hub. If this data point is processed by the Hub - i.e. made accessible via any of the available data tracking connectors - then it is counted against IntuiFace Player's Data Tracking Plan limit.

    • IntuiFace Composer - including Composer Free - can have an unlimited number of data points processed by the Data Tracking Hub.
    • IntuiFace Player can has as many data points processed by the Hub as the selected Data Tracking plan permits for a subscription month.

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

    • 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 Player's Data Tracking Plan limit until it is processed by the Data Tracking 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 a 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. It is not possible to prevent these two 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.

    Data Tracking Plans for IntuiFace Player and their Data Point Limits

    (REMINDER: There is not data point limit for IntuiFace Composer. Only IntuiFace Player is governed by the selected Data Tracking plan.)

    IntuiFace offers six Data Tracking plans for IntuiFace Player. Each is characterized by a limit on the number of data points that can be processed by the Data Tracking Hub during a subscription month.

    • Free: 1000 data points/month and storage for only the last 30 days
    • Project: 25k data points/month and unlimited storage
    • Growth: 100k data points/month and unlimited storage
    • Business: 500k data points/month and unlimited storage
    • Premium: Unlimited data points/month and unlimited storage
    • Custom: Unlimited data points/month and unlimited storage

    In all cases, the "month" refers to a subscription month, not a calendar month.

    Keeping Track of Your Data Point Limit and Consumption

    At any time, visit the Data Tracking Dashboard to see your monthly plan limit and the number of data points already processed by Player.

    Stopping Data Point Consumption

    In the upper right of the Data Tracking dashboard is a slider labeled "Data point processing". Turn it off to stop data point processing on the Hub, preserving the remaining amount of data points you have available below your limit.

    • OFF: Data points forwarded from Composer and Player to the Data Tracking Hub will not be processed. As a result, those data points will not be accessible via any connector.
    • ON: Data points forwarded from Composer and Player to the Data Tracking Hub will be processed. As a result, those data points will be accessible 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 Hub. The only way to prevent data transfer from Composer and Player to the 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 Tracking Hub and can be deleted. Deletion will not reduce your data plan consumption, it will just reduce the number of records stored on the Hub.

    1. Open the Data Tracking dashboard.
    2. Expand the Excel Connector option.



    3. Optionally apply filters to specify which data you wish to delete.

      • Filter by date
        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.
      • Filter by device
        Choose between all devices and a specific device. The device list is alphabetized.
      • Filter by application
        Choose which IntuiFace applications you would like to focus on. For example, you may want to deselect Composer to avoid downloading test analytics generated while building your experience.
    4. Click the Delete Data Points button.

    Consequences of Exceeding Your Data Plan Limit

    Exceeding your data plan limit means one and only one thing - the inability to have additional data points processed by the 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 connector.

    For additional details, visit the Licensing for Data Tracking - FAQ.