In-app events raw data report

  • Advertisers
  • Agencies


The main place to find hidden gems in your users' data is the in-app events raw data report on the Export data page. This report contains all the actions performed by your non-organic users, which were sent to AppsFlyer from the SDK or via the server to server API or via native web view.

This report is the equivalent of rough uncut diamonds for mobile marketers, which can be used for countless marketing and user behavior insights.

The in-app events raw data report is also the main source for activity data, i.e. accurate chronological breakdown of the actions performed by your users.

This report is also the only source on the dashboard for specific event values information (except for the Audiences premium feature), excluding revenue related information.

This article discusses several topics about the in-app events report and how to use it best for your purposes.


the in-app events report is premium feature. It can be accessed via the Export data page

Raw data reports structure

To make it easy to combine installs with in-app events data AppsFlyer's installs and in-app event raw data reports have the same structure.

Therefore, every in-app event in the raw data also contains the full original attribution data, just like the install event does.


What is the average time between the download or first launch of your app and until the first purchase/registration/completion of tutorial etc.? Each in-app event entry has all this information and more for your convenience.


for the full breakdown of available parameters in AppsFlyer's raw data reports please go here.

Choosing specific events

You can filter out events that don't match your current query needs from the generated reports.

Here is how:

  1. On the raw data reports section there's a drop box, which contains all the non-organic events received by the system.
  2. You can select one or many events to appear in the generated report.
  3. Click outside the box once you've finished selecting the events.



1. "Off the wagon" - select af_add_to_cart and af_purchase events to see the users that added items to the shopping cart, but didn't go through with it. A good retargeting campaign with a personalized offer may convert these users to buying users.

2. "Search and despair" - select af_search and af_content_view events to find out the users that searched for content on your app, but did not consume any content (or else they would have also had af_content_view). You can learn a lot about the most failing search keywords in your app.

3. "One at a time" - some apps have such large audiences that even one day's worth of events exceeds their CSV files size limitation. Using the events filter to download files per single event types is a good solution for these app owners.


You can get the same reports directly and fast using AppsFlyer's pull API

Event values

AppsFlyer's in-app events are called rich in-app events, as they contain value parameters in addition to the basic event name. The in-app events report is where these parameters values can be seen and used for analysis.

The file contains a column titled "Event value", which holds strings of the JSON structured event values.



Reporting revenue

All the revenue and ROI data available on AppsFlyer come from af_revenue in various events.

When the af_revenue parameter is sent with any in-app event, AppsFlyer adds its value to the total revenue of the user and its media sources. On the in-app events report this value shows up under the event_revenue column.


Only use af_revenue parameter with in-app events that describe real generated revenue. For other events that involve sums of money, but are not final (eg. add_to_cart) use other parameters like af_price.

How to follow a user's journey?

There are many insights you can draw out of observing the different customer journeys your users have from the initial launch of the app, and throughout their lifetime.

The combination of installs and in-app events raw data reports contains the full life time actions performed by your users.

If you'd like to see your users' journeys follow these instructions:

  1. Download both installs and in-app events data for the same periods of time.
    Note - you can download up to one full month of in-app events at a time. For the reports' limitations click here.
  2. Combine the CSV files into a single file.
  3. Sort or filter the file according to AppsFlyer device ID column.

The result is a group or groups of events performed by each of your users.

What is the "is primary attribution" value?

The report contains a column titled "Is Primary Attribution", which is only relevant to apps running and measuring retargeting campaigns.

During the re-engagement window, which happens after a user engages with a retargeting campaign, AppsFlyer attributes events to both the original media source (prior to the re-engagement) and to the retargeting media source.

During this window the original media source is not considered to be the primary attribution for the user's events ("false" value), while the retargeting media source is considered as primary("true").

After the re-engagement window closes down, the original media source returns to be the primary and only attribution.

What are the "is retargeting" & "is primary attribution" cases?

The example below shows a general re-engagement scenario.

The following table shows where and when in-app events appear in raw data report, following user acquisition and retargeting conversions:

  When User acquisition in-app events report Retargeting in-app events report
Events from acquired users (installs) during user lifetime Yes, primary No
Events from re-engagements during re-engagement window Yes, not primary  Yes, primary
Events from re-attributions during user lifetime No Yes, primary


  • Using the regular in-app events report you can filter in only primary results ("Is Primary Attribution" is true) to see only the regular (non retargeting) events.
  • Using the regular in-app events report you can filter in only non-primary results ("Is Primary Attribution" is false) to see only the retargeting events. Note that the media sources in these events are the original sources, and not the retargeting ones, which are actually attributed with the events.

Why is af_app_opened event missing?

The af_app_opened Event is automatically generated upon every successful launch of AppsFlyer's SDK.

af_app_opened is mainly used by AppsFlyer as a tool for calculating retention data. It is also used for notifying some media sources with launch data directly via postbacks from AppsFlyer.

Therefore, and also due to the vast number of these events, which would "drown" all other events, the af_app_opened Event is not included in the in-app events raw data report.

Which Geo do events belong to?

AppsFlyer sets the user location parameters, i.e. country, city, DMA etc. according to the user's IP address on install time.

However, human users tend to move around and perform in-app events from different locations and IP addresses than during their original installs.

AppsFlyer's raw data, and consequently also the aggregated data, displays the actual location of the user during the performance of the event, and not the original location during the install.

The reasoning behind this is to help with analyzing data for user behavior. In some verticals the location of users may have greater effect on their actions than their original install location. Analyzing the relative performance of locations can help advertisers focus on relevant retargeting campaigns to increase their users engagements.


Luber, a hail ride travel app, identified a relatively large number of ride events taking place in Springfield. To maximize its users' engagements Luber sends a retargeting push notification to any user that arrives to Springfield.


In case the IP address during the in-app event's performance cannot be resolved, the IP address during the install is displayed in the raw data

Contributor and Google play data in in-app events reports

Contributor data and Google Play data doesn't appear in raw in-app events reports. All other fields are populated if they are available on the install data.


Was this article helpful?
2 out of 2 found this helpful

Page Contents: