To effectively analyze user behavior in Airbridge, it is essential to have appropriate event definitions and event taxonomies tailored to the specific industry of the service. Consult the recommended event taxonomy for the finance services.
Note
Before you continue reading on, you may need a basic understanding of Airbridge events. Refer to the following articles for more information.
The following article from the developer guide is for developers.
Users of financial apps conduct real-time buying and selling of stock shares or explore newly launched financial products. With the rise of super apps, user behavior in financial apps has become more diverse than before. Collecting the recommended Airbridge events for financial apps will help answer the following questions:
What ads did the user engage with before installing the app?
What stock shares or financial products are the users interested in?
How is the performance of ads in terms of generating new accounts or new credit card applications?
How many financial products were sold?
Below is the recommended event taxonomy for finance apps. The event taxonomy may vary depending on the intended user actions.
The Install, Deeplink Open, and Open events don't require any taxonomy setup for Airbridge to collect them, as the events are automatically collected once the Airbridge SDK is installed.
For the full list of Standard Events, refer to this article.
You can identify the users who signed up after installing the app and measure their user retention.
You may define the Action or Label to collect the platform from which the user signed up.
Event Component |
Description |
|---|---|
Category |
|
Action, Label | {The platform from which the user signed up} |
Value | - |
Attribute | - |
Trigger | When the 'sign-up complete' message is displayed |
You can identify the users who signed in and measure their user retention.
You may define the Action or Label to collect the platform from which the user signed in.
Event Component |
Description |
|---|---|
Category |
|
Action, Label | {The platform from which the user signed in} |
Value | - |
Attribute | - |
Trigger | When the user completed sign-in |
You can identify the product item lists viewed by the users who opened the app through ads.
You may define the Action or Label to collect information on the financial product item list the user viewed.
Event Component |
Description |
|---|---|
Category |
|
Action, Label | {The product item list the user viewed} |
Value | - |
Attribute | - |
Trigger | When the user viewed the product item list |
You can identify the stock items or finance product items viewed by the users who opened the app through ads.
You may define the Action or Label to collect the information on the stock items or the finance product items.
Event Component |
Description |
|---|---|
Category |
|
Action, Label | {The name of the stock item or the finance product item the user viewed} |
Value | - |
Attribute | - |
Trigger | When the user views the stock item of the finance product item |
You can identify the stock items or finance product items searched for by the users who opened the app through ads and learn which items the users are interested in.
You may define the Action or Label to collect the search keywords.
Event Component |
Description |
|---|---|
Category |
|
Action, Label | {Search keyword} |
Value | - |
Attribute | - |
Trigger | When the search results are displayed to the user |
You can measure the revenue generated by users acquired by different ads. Based on the aggregated revenue data, you can also measure metrics such as LTV and ROI or optimize your ad campaigns.
You may define the Action or Label to collect information on the payment method or the category of the purchased stock item or finance product item. To measure sales performance, the purchase amount shall be collected as Value. You can also use the Semantic Attributes to collect more information about the purchase.
Event Component |
Description |
|---|---|
Category |
|
Action, Label | {Payment method}, {Category of the purchased item} |
Value | {Purchase amount} |
Attribute | Currency, Transaction ID, Product name, Product ID |
Trigger | When the user makes the purchase |
To accurately calculate the revenue amount, the refund amount must be subtracted from the total purchase amount.
You may define the Action or Label to collect information on the payment method and the category of the purchased item that is canceled. The canceled amount shall be collected as Value.
Event Component |
Description |
|---|---|
Category |
|
Action, Label | {Payment method}, {Category of the purchased item that is canceled} |
Value | {Purchase amount that is canceled} |
Attribute | Transaction ID, Currency, Product ID, Product Price, Product Quantity |
Trigger | When the purchase amount is refunded after order cancelation |
Attention
The Order Cancel event (
airbridge.ecommerce.order.canceled) shall be defined so that the Transaction ID is collected as semantic attributes. The Transaction ID of the Order Cancel event must match the Transaction ID of the Order Complete event (airbridge.ecommerce.order.completed).For more details on defining the Order Cancel event, refer to this article.
You can identify the stock items or finance product items added to the wishlist by the users who opened the app through ads and learn which items the users are interested in.
You may define the Action or Label to collect information on the stock items or finance product items the users added to their wishlists.
Event Component |
Description |
|---|---|
Category |
|
Action, Label | {The category of the stock item or finance product item that are added to the wishlist} |
Value | - |
Attribute | - |
Trigger | When the items are added to the wishlist |
If necessary, define additional Custom Events other than the events listed below to collect them.
You can identify the stock items sold by the users who opened the app through ads.
You may define the Action or Label to collect the information on the stock items.
Event Component |
Description |
|---|---|
Category |
|
Action, Label | {The name of the stock item sold} |
Value | - |
Attribute | Price, Product name, Product ID |
Trigger | When the user clicks the sell button |
You can identify the stock items bought by the users who opened the app through ads.
You may define the Action or Label to collect the information on the stock items.
Event Component |
Description |
|---|---|
Category |
|
Action, Label | {The name of the stock item bought} |
Value | - |
Attribute | Price, Product name, Product ID |
Trigger | When the user clicks the buy button |
You can identify the accounts opened by the users who opened the app through ads. Collecting this event is helpful if your key metric is the number of new accounts.
You may define the Action or Label to collect the information on the account type that is opened.
Event Component |
Description |
|---|---|
Category |
|
Action, Label | {The type of the account opened} |
Value | - |
Attribute | - |
Trigger | When the user opens the account |
You can identify the credit card types by the users who opened the app through ads. Collecting this event is helpful if your key metric is the number of credit card applications.
You may define the Action or Label to collect the information on the credit card type.
Event Component |
Description |
|---|---|
Category |
|
Action, Label | {The type of the credit card applied for} |
Value | - |
Attribute | - |
Trigger | When the user applies for a new credit card |
このページは役に立ちましたか？