Overview

Data points transferred from Composer and Player to the Intuiface Analytics Data Hub can be downloaded directly into an Excel spreadsheet.

This process is only supported on Windows PCs.

Download Data Points into Excel

1. Open the Analytics Data console.
2. Expand the Excel Connector option.
   
   
3. Optionally apply filters to the data that will be downloaded to Excel.
   
   
   • 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 the download 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 and a specific device. The device list is alphabetized. Can be combined with the Experience Name and/or Event Name field.
     • Experience Name
       The name of one particular experience. Can be combined with the Devices and/or Event Name field.
     • Event Name
       The name of one particular event. Can be combined with the Devices and/or Experience Name field.
4. Click the Search button. The resulting number of qualifying data points will be displayed.
5. Click the Download Data Points button that has appeared to generate an Excel spreadsheet that will be downloaded to your PC.

Structure of the Excel File

The following fields appear in all downloads:

• TimestampUTC: Contains the timestamp at the moment the Log Event action occurred.
  The date is formatted as [day]/[month]/[year]. The time recorded is for the UTC standard, equivalent to Greenwich Mean Time (GMT).
  NOTE: Be sure to verify that the time and time zone are properly set on each device running Player.
• TimestampLocalTime: Contains the timestamp at the moment the Log Event action occurred.
  The date is formatted as [day]/[month]/[year]. The time recorded is for the local time zone of the device running Composer/Player.
  NOTE: Be sure to verify that the time and time zone are properly set on each device running Player.
• DeviceName: The name of the device running Composer/Player
• Application: The name of the Intuiface software running on the device. Values can be any one of
  • Composer
  • PlayerForWindows (used for Player on Windows devices)
  • Player (used for Player on all other platforms)
    • Legacy Analytics users: This field used to be represented by two values: PlayerForTablets and PlayerForKiosks.
  • Webpage (used for web and Progressive Web App deployments)
• ApplicationVersion: The version of the Intuiface application identified in the previous field.
• PlayerTags: A list of all tags assigned to this instance of Player. If multiple tags exist, they will be separated by the pipe symbol: '|'.
• OS: The name of the operating system on the device running Composer/Player. Values can be any one of:
  • Windows
  • iPad
  • Android
  • ChromeOS
  • SSSP [for Samsung SMART Signage Platform]
• OSVersion: The version of the operating system identified in the previous field.
• ExperienceName: The name of the Intuiface experience that generated this data point.
• SessionID: Contains the Session ID if specified by the running experience. Could be blank.
• SceneName: The name of the scene in which the data point was generated.
• EventName: The name of the event specified in the Log Event action.
• ElapsedTime: Contains a value only for the automatically recorded events "Scene Left", "Session Stopped" and "Experience Stopped". In all other cases this field will be blank.

The following fields only conditionally appear:

• Value: Only appears if using Intuiface Version 5.1 or earlier.
• Comment: Only appears if using Intuiface Version 5.1 or earlier.
• [Parameter Name]: Only appears if a parameter is associated with the event represented by this data point.
  • There will be as many columns as there are unique parameters across all data points downloaded to Excel.

Translation of Parameter Values

The value of a parameter as recorded in Composer/Player may be represented differently in Excel.

Below, the parameter value is on the left, the representation of that value in Excel is on the right.

• Foo -> Foo (as text)
• "Foo" -> "Foo" (as text)
• 'Foo' -> 'Foo' (as text)
• 1234 -> 1234 (as number)
• 12.34 -> 12.34 (as number)
• 12,34 -> 1234 (as number)
• 12,34,56 -> 123456 (as number)
• 12,34,this -> 12,34,this (as text)
• 12,34, is my text -> 12,34, is my text (as text)
• "1234" -> "1234" (as text)
• True -> true (as boolean)
• False -> false (as boolean)
• 1234/12/12 -> 1234/12/12 (as date)
• 1234-12-12T12:34:56 -> 1234-12-12 12:34:56 (as date)

Additional Notes

• If a Parameter value - the value of a parameter associated with the Log Event action - contains only numbers and one or more commas, the commas are deleted by Composer/Player before data point transfer. If the comma is meant to indicate decimal notation, use a binding converter to change the comma into a period.
• The order of columns in the Excel file can vary from one download to the next. This is because each data point can introduce its own unique parameters, each of which is assigned its own column.