Tracking Server Side Usage Data
Currently the tracking SDK automatically tracks every user event but over time usage tracking goes beyond ui user interaction. Products very often build and expose APIs and integration modules. Tracking the usage of these capabilities which are also considered 'sticky' features can indicate adoption like any other ui based features. Collecting data should normally be either in real-time and event based or periodically via a data collector that can also collect internal production data that may be used for engagement by Gainsight PX.
Tracking Backend Aggregated Data
Any data outside the UI can be pushed into Gainsight PX via secured REST API. There are couple of options to store these metrics into Gainsight PX:
Tracking daily aggregated backend events
Usage trends over time can be tracked using custom events via the REST API and passing the metric name and the aggregated values as part of the payload.
// Track an aggregated metric
aptrinsic('track', 'myAggregatedMetric', {"apiCalls":10,000,"Category":"Admin","subscriptionName":"Netflix"});
Populating the aggregated value under the User and account attributes
Gaining visibility to the most recent values and allowing you to trigger in-app engagement
- Using Gainsight PX REST API
- Using the Java SDK
- Using the data loader
There are many useful data-collectors that can be used or tools like Mulesoft, Boomi, Zapier that can be used as well.
Analyze the Data
Any data that is being pushed into Gainsight PX whether it is via the auto-tracking javascript sdk or via external data collectors will be matched against your product mapper and will be visible in audience explorer user deep view, adoption analysis, retention analysis, query analyzer and path analyzer. Incase of a user or account attribute push you will see the data in audience and account explorers.
To learn about all frequently asked questions, refer Analytics FAQs article from the Additional Resources section.