In-app Events

Amongst various post-install events, In-app Events can be defined as user activities related to marketing goals and performances. We can also track, compare, and analyze these In-app Events to learn which marketing channels the users originated from and the number of events generated. 

Examples) Sign-Ups, Add-to-Carts, Purchases, and more

Airbridge’s In-app Events can be divided into three main groups: Category, Action, and Label. By using the combination of these three groups, In-app Events can be created and tracked. Moreover, In-app Events configuration and setups can be customized based on the nature of your serviced app. 

 

Terms

  • Category (Mandatory): Value which refers to the In-app Event ‘name’. You must use this Category value when setting up your In-app Events. These Category values can also be used for the below purposes:  
    • Determining the existence of the first In-app Event
    • Setting up In-app Event Postbacks
  • Action / Label: You may optionally add additional information about the events by using Action or Label values. 

💡 When designing your Event Taxonomy 

YYou’re not obligated to fill out Event Action or Event Label values as they are optional values. However, you may use these two values if you would like to classify events on a more granular level. You can use Event Category (Event Names) only by itself without using Event Action or Event Label.

However, please note that the instruction on this page uses both values. 

 

E.g.) Composing In-app Events using Action and Label values

Category

Action

Label

Adding to Wishlist Clothing Jeans
Adding to Wishlist Accessories Ring
Adding to Wishlist Accessories Necklace

 

E.g.) Composing In-app Events without using Action and Label values

Category

Action

Label

Adding to Wishlist    

 

 

Types of In-app Events

Standard Event

The 10 most frequently used conversion events including “Sign-in,” “Log-in,” “Add-to-Cart,” and “Purchase” are provided as Standard Events.

Standard In-app Event

Standard In-app Event Category

Sign-up airbridge.user.signup
Sign-in airbridge.user.signin
Sign-out airbridge.user.signout
View Home airbridge.ecommerce.home.viewed
View Product List airbridge.ecommerce.productList.viewed
View Search Result airbridge.ecommerce.searchResults.viewed
View Detailed Product airbridge.ecommerce.product.viewed
Add to Cart airbridge.ecommerce.product.addedToCart
Purchase airbridge.ecommerce.order.completed
Order Cancel airbridge.ecommerce.order.canceled

 

Standard Events have fixed Category values as demonstrated above, allowing you to freely use Action and Label values. Below are examples of actual use cases. 

e.g.) Setting up Action and Label values in Standard Events 

Category

Action

Label

Sign-up New York Male
Sign-up San Francisco Female
Purchase New York Male

 

 

Custom Event

In addition to the Standard Events, you can add Custom Events that you would like to track depending on the nature of your service. You may freely use Category, Action, and Label when designing these Custom Events.  

e.g.) Custom Events settings for Music App Services

Category

Action

Label

Pop Like Justin Bieber
Pop Like Ariana Grande
Classic Follow Mozart

 

e.g.) Custom Events settings for Shopping App Services

Category

Action

Label

Nike Shoes 679421-480
Nike Shoes 488291-406
Adidas Hat 15008107_M

 

e.g.) Custom Events settings for Travel App Services

Category

Action

Label

Hotel Berlin 170318_170328
Hotel Paris 170505_170522
Flight Berlin 170910_170924

 

Registration of In-app Events

When you make a call to the Custom Events (which include Category, Action, and Label values) once conversions you wished to track in the Android or iOS SDK have occurred, the In-app Events will automatically be registered and recorded. 

The eight Standard Events can be tracked with a separate call method when installing SDK, and you can use these events without attaching any information to In-app Events as they are optional.  However, we recommend attaching the optional information as they may come helpful in discovering more accurate statistical results in remarketing campaigns and DSP integrations. 

Please refer to the following guidelines to register In-app Events for each operating system. 

Hybrid App/ In-App WebView Additional Settings

For hybrid apps, events such as “app installs” or “app-open” and “deep-link open” cannot be tracked with Web SDK only.  However, Airbridge allows hybrid apps to easily call In-app Events by configuring additional settings. Moreover, iOS SDK can send events on behalf of the Web SDK installed on the WebView website. Please refer to the links below for more details. 

 

Note

  1. As shown below, Category is the major standard value amongst the three values of In-app Events (Category, Action, and Label) that are used for running statistical data and features. Please take this into consideration when designing your In-app Event. 
    • Sending In-app Event Postback: In-app Event Postback will be sent using the Category value and not Action or Label values. 
  2. Word limit of Category, Action, and Label in Airbridge
    • Category
      • Alphabets (uppercase or lowercase), numbers
      • Special characters(_,,,.) are available
      • Up to 45 letters
    • Action, Label
      • Alphabets (uppercase or lowercase), numbers, 
      • Using spaces and special characters(?, !, ,, ., /, (, ), -, _) are available
      • Up to 128 letters
Was this article helpful?
0 out of 0 found this helpful