The Gigya Reports service provides extended reporting capabilities to widgets using the Gigya platform, allowing developers to easily track widget usage patterns.
The service supports tracking of interaction and activity times as well as sending custom event reports, appropriate for the specific widget. For example, a recipe widget could send a "recipe viewed" event report and later get reports based on that event.
Interaction reports can be viewed under the Interaction Reports section available on the Gigya website.
Event reports can be viewed by creating personalized charts on the Custom Reports section on the Gigya web site.
Types of reports
Event reporting is used to count the occurrence of different application generated events during the runtime of the widget. The widget developer can identify any number of interesting events that occur during the lifetime of the widget and call the reportEvent() method to report them to Gigya servers. These event reports will be aggregated by Gigya and made available in the reporting section of the Gigya website.
For example, a recipe widget could send a "recipe viewed" event report and later get reports on how many recipes have been viewed. These reports may also be correlated with other Gigya tracking elements, such as widget installs, so it will be possible to calculate the ratio between installs and recipe views to estimate the effectiveness of the widget.
Interacted views counting
Interacted views are defined as loads of user interaction with the widget. User interaction is defined as a click or mouse hover for over 5 seconds anywhere on the widget.
Interacted views are automatically counted after calling the startTracking() method.
Exposure time tracking
Exposure time is the total time in which the widget was loaded on a web page (whether visible or not). Exposure time is measured automatically after calling the startTracking() method.
Interaction time refers to the total time users spend interacting with the widget. Interaction time can't be measured automatically because only the application knows what should be counted as interaction time. For example, a music player widget may wish to count the time a song is being played as interacted time even if the widget wasn't visible the entire time. Use interactionStarted() and interactionStopped() to indicate when interaction time measurements should start and stop.