Defining In-App Events

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

For SDK integration instructions, see the guide in the Developers Portal.

 

The goal of adding in-app events is to enable UA Managers to measure the success of their marketing efforts: this is how you will be able to measure retention and ROI. Think of what additional KPIs you would like to measure and make sure you define events to help you measure these. 

Therefore, this planning stage is critical for how you will measure and optimize your marketing efforts.

There are basics events:

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

But what are other events you should make sure to include? 

Event List Template

We recommend putting together a list of events as follows:

  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 doe 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

Examples

We’ve put together a sample template for you to review here

Was this article helpful?
0 out of 0 found this helpful