Capturing Analytics from IFRAME Embeds
Kaon apps and 3D product tours embedded on websites post messages to the embedding page for all user interactions. The hosting page can set up a listener, and then pass selected analytics information on to whatever web analytics package is being used.
Example listener code:
As the example shows, user actions are stored in an object called kaon which is an attribute of the message object.
The attributes of the kaon object indicate what user interaction took place.
Within a solution story, a single attribute "experience" will carry the information about what the user interacted with:
Name of the section viewed, collateral item clicked, etc.
Within 3D product models, a variety of attributes may be present:
Name of the action which took place (this will be "model" at load time)
Name of the product (this attribute is always present)
String with the name of the animation button the user selected
String with the text of the hotspot (truncated, since these are often quite long)
Object indicating that the user manually changed the view. This object will contain one or more of the following:
New field of view
New angle of view in degrees
New center of view offset
String indicating that the user entered "ar" or "vr" mode
The string "reset" indicating the user clicked the reset button
Distance measured by user (in centimeters)
The app will periodically send a message when the user moves into a new engagement level. There are 7 levels (numbered 0 to 6) corresponding to how long they have been using the experience (excluding idle time).
Number in the range 0 to 6 indicating the user's level of engagement
Text representation of the bucket value:
The following example is typical of how events should be recorded. The specifics depend on which analytics package you use.
This is a live jsfiddle showing how it works: https://jsfiddle.net/jesmith_at_kaon/ktLrs7ze/