For embedding instructions please visit our documentation (iOS / Android).

You might already be familiar with Events from other analytics platforms, but it’s important to understand the use-cases for Events in Appsee, as these are different.

“Events” in Appsee are complimentary Timeline Datatypes which are not “Screen Views” or “Actions” (as these are tagged automatically by the SDK). Events should represent singular occurrences in business processes that you have an analytical interest for. Events can also have properties.

Events are defined by you and implemented in your code, Appsee does not predefine Events automatically. The Events are then attached to your session’s timeline when they are triggered during runtime of the app. Events are denoted by a flag, and their properties are denoted by cog-wheels:

Events Use-Cases

1. Help you find videos of sessions that contained a particular event.

For example, an “Order Failed” Event can help you quickly filter the sessions to find ones that contained it.

2. Create powerful Funnels and Cohorts where Events are utilized as core steps.

For example, by using the “NewUser” Event as the last step in the Onboarding Funnel you could analyze sessions of users that clicked on “Create an Account” in screen “Login” but have never triggered the “New User” Event.


Or for example measure the Time To First Purchase KPI:

3. Advanced recording conditions.

For example, you can set a “Payment Declined” Event as a recording condition in order to make sure that if it was triggered in a session, this session will also have a video recording.

4. Analytics – Appsee counts Events and displays their properties’ distribution.

For example, an “Item Added to Cart” Event with the properties of ItemID, Brand, Quantity. This Event and its properties could be analyzed under Analytics > Events.

5. Encapsulating an “OR” condition – If you have 2 screens from which a payment can be made then by triggering a “Payment Attempt” event when the user taps on a button “pay now” in screen 1 OR screen 2 you will be able to create a Funnel which includes users that did that in either of these screens.

It is important to define events well, as they provide you an analytical degree of freedom to track, measure and model any process or KPI you like.

Please see our API reference (iOS / Android) for technical instructions on implementation.

Please refer to our list of recommended events per vertical for some ideas for Events.

* It is recommended to trigger events by using the ScreenDetected notification (iOS / Android) when an event is triggered upon the appearance of the screen.