Gigya’s cross-platform analytics deliver interaction and traffic data, including details by platform and sharing type. Graphic reports are available in the Gigya Console under the Reports tab (you must be logged in to access this page). See Available Reports for descriptions of the various reports and how to use them. Most reports can be filtered by site, time range and context ID: see the Filtering Reports by Context section for more information.
Other information and tools are also available:
- Under the Reports tab, you can also access the Identity Query Tool - an intuitive, dynamic tool for searching and retrieving users' profile data, which enables you to create search queries using simple dropdown menus, with no database knowledge required.
- In addition to the graphic reports, Gigya provides REST API methods for retrieving report data in CSV format: refer to the Reports API reference for more information. RaaS users should see note below.
- If you are using a third-party analytics tool in your site, such as Google Analytics or Adobe Analytics, refer to the Analytics Integration guide to learn how to add Gigya's social data to third-party reports. For information about Gigya's ETL platform, see IdentitySync.
Watch an Instructional Video
If you have a Gigya Academy membership, you can watch instructional videos about this and other Gigya products. To access Gigya Academy content, you should first make sure you are logged into the Gigya Console.
Click on the report categories or on specific reports to see what you can learn from each report:
- User Identities Reports
- Syndication Reports
- Community Reports
- Game Mechanics Reports
- Other Reports
Filtering Reports by Context
Most of the reports can be filtered by date and Context ID using the dropdown selections at the top of the page.
The "Context ID" combo box lets you filter the report data by site/application context:
For complex websites, the Context ID dropdown list may not display all relevant choices. The size limits for the dropdown list are:
- Context ID (all reports) - 100 entries
- Category ID (for Comments) - 50 entries
- Bar ID (for Reactions) - 50 entries
- Button ID (for Reactions) - 50 entries
- Challenge ID (for Gamification) - 50 entries
The entries in the list are sorted in descending order by the number of event in each ID (except for Challenge IDs). IDs with equal number of events are sorted alphabetically by name.
Defining Context ID (cid)
You can define a context ID for different pages or widgets in your site/application by using the cid parameter.
The cid parameter is a string of maximum 100 characters length. This string is used to associate categories with transactions to which a parameter is passed, for use in generating reports. You should not use more than 100 different CID strings.
The cid may be defined per page/widget, by defining it in the page's/widget's global configuration object. For example:
The cid may also be defined per transaction (API method call), by defining it in the method's specific params object.
If the cid parameter appears both in the global configuration object and in the method's params object, then the value set in the params object overrides the value set in the configuration object. This can be useful for defining a global default in the global configuration object, and overriding the default in some methods, by setting a different value in the method's params object.