Now, after learning how to create an experience, you can start capturing interaction information using the Analytics feature of Intuiface. This will enable you to identify the preferences and - when relevant and available - the context of these preferences and the demographics of those who use your experience.
With Analytics you can log information about virtually any event. In this tutorial you will learn how to log information about custom events, retrieve raw data using the Analytics Data console, and then view a prebuilt set of charts based on that data.
Add the Data Tracking Interface Asset
- We are going to add an Interface Asset (IA) to our experience. Interface Assets enable Intuiface experiences to communicate with external data sources, business logic, and devices. In this case, we're enabling this experience to use the Data Tracking Interface Asset, the IA responsible for collecting event data.
- Use the blue ribbon to display the Interface Assets Panel. Click the "Add an Interface Asset" button and select "Data Tracking" from the list
- Click on "Add". The Interface Asset will now be present in the IA panel
Add automatic scene navigation tracking
- Select the Data Tracking Interface Asset from the Interface Assets panel to the left of Composer and then display the Properties Panel by pressing the "Properties" button on the blue ribbon.
- Check the "Include scene navigation events" check-box
- The Data Tracking Interface Asset will now record every time scene navigation occurs. In addition, dwell time per scene will be measured and reported.
Add a custom event
- Select the "Biography" scene, the same scene we created in the first part of this tutorial.
- Let's track every time a page in the PDF is turned. This will help us identify the popularity of this document and how far visitors tend to read it.
- From the Scene Structure panel, select the Document Asset (Timothy Burton Bio), right click on it and select "Add a Trigger".
- In the Triggers and Actions panel, select the Document from the trigger category, then select "Page is changed" as the actual trigger. This translates into "when the document's page is changed".
- Click to add an action and select Interface Assets. We want to add an action on the Data Tracking IA.
- Select Data Tracking from the action category and "Log event" as the action parameter
- We should give our event a name so that we will be able to identify it among other logged events. We will call this event "Biography document"
- Now, we will add a parameter to the event. While you can add any number of parameters to a logged event, we will add only one here in the tutorial. We'll name this parameter "Doc Page"
- Next, we willbind the value of the "Doc Page" parameter to the document's current page number. Thanks to binding - that is, thanks to our ability to get the value from the document and store it in this parameter - we can track which page of the document our users are reading.
- Let's see what we've created! Play the experience and browse the document to log some events.
Retrieve data collected for the specified events
- In Composer, open the "Help" menu and select "Consult Data Tracking dashboard"
- Your system's default Web Browser will open up displaying the Analytics Data console.
- Expand the Excel connector option and click on the "Download Data Points" button.
- An Excel workbook containing the recorded data should now be downloaded. Open it to see the recorded data.
- View prebuilt charts based on the collected data
- Head over to the Analytics Dashboards console. Here you'll see a set of prebuilt charts within a dashboard named "My First Dashboard".
- Look for the "Average Dwell Time per Scene" chart. Here you'll see the data collected because of the "Include scene navigation events" selection you made in Step 2 above. Note how the chart contains an ExperienceName drop-down, useful if you collected data for more than one experience.
Build your own charts to track how often the book is read and how far page turners get in the book. With this information you can learn things like which locations have the most readers and whether the book length is too long for the average visitor.