Heap captures server-side events through integrations or by directly sending data to our server-side APIs. You can easily find a user and/or session with server-side events by leveraging either Users or Sessions view depending on your specific need.
Users with server-side events
To find users with server-side events, navigate to the Users page. Click Add filter and select the behavorial property Users who have done. From this filter selection you can then select any server-side event defined within your Heap account.
For example, the following filter would display any user who opened a Marketo email in the past 7 days.
In addition to filtering for a specific server-side event, you can also filter for individual users based on their user_id or identity. Within the user’s profile view, server-side events will appear within any session based on the timestamp of the server-side event. This means sessions could have a mix of events captured by one of Heap client SDKs (web or mobile) or via server-side source (integration or http API).
Server-side events that cannot be associated with an existing client-side session and events will be displayed in a user’s profile within a separate session for any server-side events captured within 30 minutes of the first server-side event.
Sessions with server-side events
To find sessions with server-side events, navigate to the Sessions page. You can filter the sessions list based on a server-side event by selecting the event from the Filter by event dropdown.
Additionally, you can filter to find sessions for a specific user by selecting user_id or identity from the Filter by user dropdown. This will show all sessions for a single user including those sessions from which tracking originated by both client-side and server-side events.
Session Filtering Limitations
Filtering by a server-side event will only show sessions that originated tracking from a Heap client-side SDK (web or mobile). Server-side events which cannot be associated with client-side sessions will not be displayed as separate sessions within the list.
Filtering by a user property instead of a specific user_id or identity will only return sessions that originated tracking from a client-side event.