If you’re using a framework such as NativeScript or Unity, you can set this up by using our server-side track API to send events and associated properties into Heap. Once sent into Heap, the events will automatically be routed to the appropriate user based on the value passed to the required ‘identity’ argument in the API call.
If no user exists with the ‘identity’ value passed, a new user will be created. If you’ve already installed Heap and identified users elsewhere (e.g. on your website) be sure to use consistent identifiers across installs to consolidate cross-platform data for a user under a single profile.
While session-based analysis will be restricted, you can set a time restriction (e.g. within an hour) on reports to serve as an approximation.