Analyzing Production Usage Data

Updated 3 weeks ago by Michael Alon

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 aptrinsic.

Tracking Production Data

Any data outside the UI can be pushed into Aptrinsic via secured REST API. There are couple of options to store these metrics into Aptrinsic:

  • In case these events are time based and you'd like to analyze trends over time it is recommended to use custom events API and pass the name and relevant properties you would like to track which are associated with the event. These events should be associated with a user id.
  • User and account level metrics can also be pushed into a corresponding attribute or custom attribute

There are many useful data collectors that can be used or tools like Mulesoft, Boomi, Zapier that can be used as well.

Here is an example of using aptrinsic's API to feed user attributes

Analyzing The Data

Any data that is being pushed into aptrinsic 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.

How did we do?