NoteAirbridge events come in two types, Standard Events and Custom Events. Use a Standard Event if one matches the user action you want to track. If no Standard Event matches, define a new Custom Event.
Standard Events
Standard Events are events Airbridge has predefined for major user actions. Only the category is predefined in the event components. You can define the action, label, value, and attribute. Each Standard Event appears in the dashboard with its predefined name.List of Standard Events
List of Standard Events
The event category is the identifier used when forwarding events to ad channels or third-party platforms. Each destination displays it under its own mapped name.
Standard Event Examples
Sign-up (airbridge.user.signup)
Sign-up (airbridge.user.signup)
Event Definition Example
If you support social login or one-click paymentIf your app supports social login (e.g., Naver, Kakao) or one-click payment (e.g., Naver Pay, Kakao Pay), set the trigger to when the confirmation screen appears. Sending the event before the confirmation screen loads may cause the event to fail to reach Airbridge.
Sign-in (airbridge.user.signin)
Sign-in (airbridge.user.signin)
Event Definition Example
NoteSend the event only when the user successfully signs in. This must be distinct from failed sign-in attempts. Otherwise, both successful and failed sign-ins may be collected in Airbridge.
Order Complete (airbridge.ecommerce.order.completed)
Order Complete (airbridge.ecommerce.order.completed)
What you can trackMeasure revenue from users acquired through ads. Use this data to calculate LTV (Lifetime Value) and ROI (Return on Investment), or optimize ad campaigns.Event definitionCollect the purchase method using action and label. Collect the purchase amount as value to sum revenue. Use semantic attributes to capture additional order details.
Important
- Always send
eventData.goal.semanticAttributes.currency. - If your app supports social login (e.g., Naver, Kakao) or one-click payment (e.g., Naver Pay, Kakao Pay), set the trigger to when the confirmation screen appears. Sending the event before the confirmation screen loads may cause the event to fail to reach Airbridge.
Send events to the Airbridge serverTo view event data in reports, your Airbridge SDK must send collected events to the Airbridge server. Share the guides below and your event taxonomy with your developer and ask them to implement in-app event tracking. Airbridge supports Android, iOS, Flutter, React Native, and more โ check the developer guide list for all available platforms.
Custom Events
Custom Events are events you define to track user actions beyond Standard Events. Define all event components to fit your service.Custom Event Examples
Game Play (play_game)
Game Play (play_game)
What you can trackAnalyze detailed retention for users who play the game after installing the app.Event definitionThe trigger timing varies by genre. For RPG games, collect the event when the user taps the Start Game button. For puzzle or arcade games, collect it at the start of each stage.
Claim Bonus (claim_bonus)
Claim Bonus (claim_bonus)
What you can trackAnalyze users who claim bonuses in your game. Track which in-game actions lead to bonus claims.Event definitionIf your game distributes multiple reward types through bonuses, use the action or label to capture the reward type.
Send events to the Airbridge serverTo view event data in reports, your Airbridge SDK must send collected events to the Airbridge server. Share the guides below and your event taxonomy with your developer and ask them to implement in-app event tracking. Airbridge supports Android, iOS, Flutter, React Native, and more โ check the developer guide list for all available platforms.