Defining In-App Events

Before you integrate the Singular SDK, learn how to decide which in-app events you want Singular to track.

For SDK integration instructions, see Getting Started with the Singular SDK/S2S.

See also: Ways of Measuring Events (Cohort vs. Actual, Unique, First).


Why Track In-App Events?

By tracking in-app events, you get the ability to measure the success of your organization's marketing efforts through the KPIs that are important to you. Therefore, before your organization starts integrating the Singular SDK or S2S, it's important to think of the KPIs you want to measure and define the list of in-app events that will help you measure them.

Singular customers commonly track the following events:

  • Login
  • Registration
  • Tutorial completed
  • In-app purchase

But depending on the nature of your app and your organization's goals, there may be other events you need to track.

Creating a List of Events

We recommend putting together a list of events and their attributes as follows. This will be a useful guide in the process of integrating the Singular SDK as it will let you or your developers know exactly which in-app events to report to Singular and what attributes to send with each event.

  Description Example
Event Type What kind of event is it? 
  •  Authentication
Event Name What do you want to call your event?
  • Login
Attribute Names What attributes does your BI team need? Event attributes are only reported on the user level (via export logs or postbacks). Some attributes are automatic (like device ID, timestamp). Think of what unique attributes are relevant for you. 
  • Level up
  • Product
  • City
Attribute Description  Describe the attributeץ
  • Level the user has reached
  • Product Name
  • User City
Attribute Values  What's the format of the attribute?
  • 3
  • Game 5
  • New York City

Sample Event Table

We've put together a sample event table you can use as a template.

Was this article helpful?