Access data points in Google Analytics
Table of Contents
Data points transferred from Composer and Player to the IntuiFace Data Tracking Hub can be forwarded directly to one or more Google Analytics properties.
Google Analytics, originally created by Google to monitor website performance, was enhanced in 2016 to accept and analyze data generated by mobile applications. It is thanks to this enhancement that IntuiFace can upload data points generated by any number of Composers and Players to one or more Google Analytics properties for analysis.
- Google Analytics is premised on the notion of real time monitoring. As a result, it will not accept data points more than four hours old. If it is necessary for you to collect data points offline and upload them to the IntuiFace Data Tracking Hub more than four hours after their collection, you cannot use Google Analytics.
- IntuiLab has no formal relationship with Google and does not provide support for their offering.
When creating a Google Analytics property for the purposes of capturing and analyzing IntuiFace-generated data, on the "New Property" screen:
- Specify "Mobile app" for the question "What would you like to
- Select the "Google Analytics Services SDK" tracking method.
Take note of the Tracking ID for this property as it is the identifier used by IntuiFace when uploading data points.
To forward data to a Google Analytics property, IntuiFace needs to know that property's tracking ID.
To get the tracking ID for a specific property, follow the directions maintained here by Google.
The tracking ID is a string like UA-000000-01.
- Open the Data Tracking
- Expand the Google Analytics Connector option
- Click the button "Add Connector for Google Analytics
- Enter any name you wish in the Name field (any
value will do but we recommend use of your Google Analytics
property name) and, in the Tracking ID field,
paste the tracking ID for your Google Analytics property (see
- Clicking the "How to find a Tracking ID" link will take you to
a Google page explaining where to find the tracking ID for a
- Clicking the "How to find a Tracking ID" link will take you to a Google page explaining where to find the tracking ID for a property.
- Click the Save button.
- Repeat Steps 3 thru 5 for each additional Google Analytics property.
Once a connector exists for a Google Analytics property, the connector can be toggled on and off using the slider labeled "Send data points to this connector".
- OFF: From the moment this slider is toggled to OFF, no new data points arriving at the Data Tracking Hub will be forwarded to this particular Google Analytics property.
- ON: From the moment this slider is toggled to ON, new data points arriving at the Data Tracking Hub will be forwarded to this particular Google Analytics property.
Google Analytics does not permit the creation of custom fields so all information collected by IntuiFace must be mapped to existing fields. The mapping is explained below.
- DeviceName: The name of the device running Composer/Player
- App Version: The name and version of the IntuiFace
application running on the device. Product names can be any one of
- IntuiFace Composer
- IntuiFace PlayerForWindows
- IntuiFace PlayerForTablets
- IntuiFace PlayerForKiosks
- Client ID: The license key for the IntuiFace product on each device. Client IDs enable the grouping of all sessions on a given device.
- OS Version: Contains the name of the operating system and the version of the operating system on each device running Composer/Player.
- App Name: The name of the IntuiFace experience that generated this data point.
- Screen View: The name of the scene in which the data point was generated.
- Event Category: The name of the event either automatically created by IntuiFace or specified by the Log Event action.
The following fields only appear if the logged event contains one or more parameters:
- Event Action: All parameter names for the specified Event Category, separated by the pipe (|) character.
- Event Label: All parameter values for the specified Event Action, separated by the pipe (|) character.
For example, for the following event logged by IntuiFace:
- Event Category:
- Event Action:
- Event Label (i.e. sample value for each parameter)
Google automatically assumes the first data point it sees is the start of a new session. It will also assume the current session has ended if no data points are detected over a span of 30 minutes. (This length of time is configurable. See this section to change it.) After Google automatically ends a session, it will start a new one upon receipt of the next data point.
The IntuiFace Start new session action can be used to indicate when a session has started based on your personal criteria. By calling this IntuiFace action, you end the session automatically started by Google.
The IntuiFace Stop current session action will stop the current session whether that session was started by Google or by the IntuiFace "Start new session" action.
NOTE: If using the IntuiFace "Start new session" action, the associated session ID needs to be anonymous or it will be rejected by Google and subsequent actions will be merged with the preceding session. If specifying your own session ID, use a name that can not be construed by Google as indicating a specific user (e.g. don't use an email address). If you leave the "Session ID" field blank for the "Start new session" action, IntuiFace will randomly generate a string for the session ID that will satisfy Google.
To filter data in Google Analytics by session ID, you must create and use the "User ID" view within Google Analytics. This is the only view in Google Analytics where sessions can be filtered and/or sorted by their ID.
All other views in Google Analytics do not indicate session IDs. They order sessions by time and by Client ID (i.e. by device).
As mentioned above, Google assumes the current session has ended if no data points are detected over a span of 30 minutes. Perhaps you would like to change this value to either 1) avoid having to use IntuiFace to differentiate sessions, or 2) to eliminate the likelihood that Google creates sessions among those you create using IntuiFace.
To change the session timeout length:
- Open the Admin panel for your Google Analytics account.
- Open "Property Settings" - in the Property column - and select
the item Tracking Info -> Session
- Increase the "Session timeout" to a value that will never be
reached for a session in your deployed experiences.
For all views, filtering by one or more "segments" gives you the ability to filter by any of the fields associated with a data point.
Views of interest:
- Real Time view: Use this view to, for example, see how many
active sessions there are at that moment in time. Click the
following image to enlarge.
- Audience view: Use the "User Explorer" subview to look at
individual devices via the Client ID field (recall that the "Client
ID" is the IntuiFace license key on each device). Information about
each device will be ordered by session. Click the following image
- Behavior view: Use the "Behavior flow" subview to view the
scene order visited during each session. Click the following image
- It can take up to five minutes for data transmitted from the IntuiFace Data Tracking Hub to appear in the Real Time view and up to 60 minutes for data to appear in all other views. This delay is imposed by Google and thus cannot be controlled or accelerated by IntuiFace.
- If a Parameter value - the value of a parameter associated with the Log Event action - contains only numbers and one more 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.
- Tip of the Month: Getting Answers To Your IntuiFace Questions
- Tip of the Month: Little Known Features of IntuiFace
- Tip of the Month: Experience Design Choices to Optimize Performance
- Tip of the Month: Using Out-of-the-Box Interface Assets to Incorporate Real-time Information
- Tip of the Month: Use Design Accelerators to Improve Appearance and Functionality
- View all (6 more)