At a glance: Measure the quality of your users throughout their user journey by recording these suggested in-app events for your eWallet app.
eWallet
eWallet apps enable users to make digital payments or purchases from their devices. The typical events that we suggest recording include adding funds, viewing content, selecting merchants, viewing promotions, and completing transactions.
Recording these events can help you determine:
- What type of content and promotions are popular with users, and then offer them similar or related products
- What are the most popular types of services users use eWallet for when making bill payments
- Which merchants are the most popular
Important!
- Make sure to read the instructions for marketers about implementing in-app events.
- To streamline the implementation process, use our In-app event generator. This tool includes all of the typical in-app events described in this article and lets you modify the events according to your business needs. Once complete, share the file with your developer.
- For each recommended event included in this article, there are code samples for iOS, Android, and Unity developers.
- Detailed instructions for your developer can be found in the AppsFlyer developer hub.
For more information about recording in-app events, see the In-app events guide.
Recommended structures for predefined events
The following section provides a list of event structures that are typical to the eWallet vertical. Each structure includes a predefined event name and the suggested event parameters to use. Note that in-app events can include any event parameters that meet your business needs.
Complete registration (af_complete_registration)
Purpose
Learn how many users installed the app and completed the signup process and what signup methods your users prefer.
Trigger
When the user completes the signup process
Event parameters
Name | Description | Example value |
---|---|---|
af_registration_method | Type of signup method | Email, Facebook, Google |
Login (af_login)
Purpose
Understand the retention of your registered users
Trigger
When the user successfully logs in
Event parameters
Can be sent without any additional parameters
Content view (af_content_view)
Purpose
Determine the view rate of specific content. This event can help you:
- Understand what type of content is most popular with your users, and then try to optimize your marketing campaigns
- Correlate item views with merchants
Trigger
When the user views a specific item or category content
Event parameters
Name | Description | Example value |
---|---|---|
item | Type of item | cinema ticket |
merchant_name | Name of merchant | cineplex |
Recommended structures for custom events
The following section provides a list of event structures that include custom event names and the suggested event parameters to use. Note that in-app events can include any event parameters that meet your business needs.
Wallet complete top-up (wallet_complete_topup)
Purpose
Top-up funds can be used to buy any package or any other service offered inside the app. Record this event and compare it with other data to learn more about your users. For example, you can learn what amounts users are willing to deposit into their accounts and then use the top-up amounts to target them with customized campaigns within their budgets.
Trigger
When the user completes the top-up from their bank or credit card to the eWallet app
Event parameters
Name | Description | Example value |
---|---|---|
top_up_amount | Amount of payment | 100 |
top_up_method | Type of payment method | bank transfer |
Payment transaction completed (payment_transaction_completed)
Purpose
This event can help you:
- Highlight users who completed payment on a transaction.
- Identify large transactions, and then retarget users who top-up with a large sum of money.
Trigger
When the transaction of a specific purchase is completed
Event parameters
Name | Description | Example value |
---|---|---|
item | Item paid for | prepaid card reload |
quantity | Amount paid | 1 |
transaction_amount | Amount of the transaction | 50 |
Bill payment success (bill_payment_success)
Purpose
This event can help you determine the most popular type of service users use eWallet for when paying bills (for example, water bills, electricity bills, or credit card balances).
Trigger
When the user is using eWallet to make payments, such as bills, or credit card statements, or cinema tickets
Event parameters
Name | Description | Example value |
---|---|---|
merchant_name | Name of merchant | Electricity provider |
payment_amount | Amount paid | 100 |
category | Type of service | Electricity |
Promo (promo)
Purpose
This event can help you determine:
- Whether the promotion being offered is popular with users
- Whether the promotion helps with cross-selling additional products to users
Trigger
When the user selects the promotion available within the app
Event parameters
Name | Description | Example value |
---|---|---|
promo_type | Type of promotion being offered | 30% off |
Voucher redeem (voucher_redeem)
Purpose
This event can help you determine:
- How many users redeem promotional codes
- What sort of vouchers and discounts users prefer
Trigger
When a user promotion code is redeemed
Event parameters
Name | Description | Example value |
---|---|---|
voucher_ID | ID of the voucher | 1735103 |
merchant_name | Name of merchant | cineplex |
Select merchant (select_merchant)
Purpose
This event can help you determine which merchant is the most popular and then use this data to try and get similar merchants to join the eWallet service.
Trigger
When the user selects a merchant from the list of available merchants
Event parameters
Name | Description | Example value |
---|---|---|
merchant_name | Name of merchant | cineplex |
type | Type of business | cinema |
amount | Currency used by the advertiser | USD |
merchant_ID | Specific ID attached to a business that tells the payment processing systems involved in a transaction where to send which funds | 123456 |
Scan barcode success (scan_barcode_success)
Purpose
This event can help you:
- Understand when a user completes a specific transaction with a merchant
- Determine which merchants are the most popular
Trigger
When the user scans the QR code from each merchant that they visited using the eWallet app
Event parameters
Name | Description | Example value |
---|---|---|
merchant_name | Name of merchant | cineplex |
merchant_ID | Specific ID attached to a business that tells the payment processing systems involved in a transaction where to send which funds | 123456 |