AppsFlyer allows you to track any post-install event that you are interested in attributing to a media source and campaign.
For any event you can send AppsFlyer ANY related parameters and ANY values. However, AppsFlyer recommends using these rich event structures to enable automatic mapping of the event values to various partners.
You can track any relevant in-app event, such as:
- Register / Login
- Tutorial completed
- In-app purchase / Add to cart
- Ad watched
You can use AppsFlyer's rich in-app events to track general user behavior in your app.
However, the real purpose and functionality of using AppsFlyer's events, is to analyze the quality of your users coming from different sources.
We recommend starting with 3-5 events, that best reflect high quality KPIs of your users, e.g purchases, registration, sharing etc.
In general, there are a number of ways to track In-App Events:
SDK Originated Events
The main source for mobile users actions is the mobile app itself. You can send rich in-app events recording your users actions in the app using AppsFlyer's in-app events API at the SDK level.
For details on how to create in-app events, see AppsFlyer Rich In-App Events
Server to Server Events
For example, if you have a user who is active on both web and mobile interfaces, you can record all events from both mediums and attach them to the same user in AppsFlyer. It can be either in-app events or other events, such as website events, call-center events or purchases in your brick and mortar store.
See details and instructions here.
Validate Purchase Events
Events from Native Web view
Viewing In-App Events Data
The Events data anywhere in AppsFlyer is presented either as Life Time Value or as Activity data. The following article explains the difference between the two methods and where you can see them.
Revenue and In-App Events
In-app events are the only source of revenue data on AppsFlyer. You can attach a specific revenue value to each event, and view it on your app's dashboard.
Go here for more details about the monetizing parameters.