AppsFlyer

If you have the integration with AppsFlyer, you can view data from this tracking platform on Affise too. You don't need to switch between platforms to analyze all the information.

Connect Affise and AppsFlyer

To get statistics from AppsFlyer, you need to connect it with Affise.

To start with AppsFlyer, enable the plugin in Marketplace > AppsFlyer.

You need to insert the AppID and Token, which you get on the AppsFlyer side.

  • AppID: an ID of the application to get the statistics for.

  • Token: your API token used to connect Affise and AppsFlyer via API.

If you have the AppID like id123456789 (for App Store) or com.hoteltonight.android.prod (for Google Play Market), insert them as they are. If you have several AppIDs, separate them with a comma.

Plugins _ AppsFlyer _ Buzzworx - Google Chrome 2022-09-07 at 6.06.18 PM

If something is wrong with AppID and/or Token, you receive a notification with the error message. To clarify the message, address AppsFlyer Support.

Plugins _ AppsFlyer _ Buzzworx - Google Chrome 2022-09-07 at 6.07.24 PM

On the AppsFlyer side, you need to have access to Pull API. Do the following:

  • to be registered in AppsFlyer as an agency or an agency&network.

  • to be allowed to get data by API from your advertiser (they should allow API usage).

If you are an agent in AppsFlyer and don't see the data on Affise, ask the advertiser to provide you access to aggregate organic data and raw data reports.

Annotation_on_2021-04-01_at_14-29-22

Once you set up everything, the AppsFlyer statistics appears the next day at 00.00 UTC (00.00) approximately on Affise. The system updates statistics once a day.

AppsFlyer Statistics

โš ๏ธ The AppsFlyer statistics is available only for certain plans. Contact your Affise account manager to get the feature.

It is a copy of AppsFlyer statistics. The system pulls it from the Raw data report in AppsFlyer.

Statistics is located in Statistics > AppsFlyer.

Appsflyer _ Thing Or Two - Google Chrome 2022-09-07 at 7.39.20 PM

You can see the following slices:

  • Date

  • Event name

  • Media source

  • Campaign

  • Country

  • City

  • Language

  • Platform

  • App ID

  • Adset

It has the following filters:

  • Date range: the date range within which you want to see statistics.

  • Timezone: the timezone according to which you want to see statistics.

  • Countries: GEO defined by the database used by AppsFlyer.

  • App ID: a unique case-sensitive identifier that appears in the URL address of a store app page (Bundle ID, Application ID in the App Store or Google Play Market).

  • Campaign: an ad set (one or more).

  • Event name: a name of an event (goal).

  • Media source: the media source attributed to an event. Here you can learn more.

  • Platform: an OS of a device: iOS, Android, Windows Mobile.

  • Device Type: for example, iPhone, Samsung, etc.

  • Adset: the set of ads (contains one or more ads): used to define targeting, budget, schedule, bidding, and placement.

The statistics table contains the following columns:

  • Clicks: user engagement (within a media source) that redirects the user to an advertised page or app activity. The system depicts this type of data only in the following slices: Date, Media source, Campaign.

  • Impressions: the act of viewing an ad by an app user or website visitor. The system depicts this type of data only in the following slices: Date, Media source, Campaign.

  • Install Organic: mobile app installs that occur without any direct effort by an advertiser. Read this article to learn more.

  • Install Non-Organic: mobile app installs that AppsFlyer attributes to a paid or owned marketing activity. Check this article to learn more.

  • Events number: the number of conversions.

  • Events revenue: earnings for different events.

  • Unique users: here you can read which users are considered unique.

See how to manage and sort columns in the table here.

๐Ÿ“ƒ Related topics


Please contact the Affise Customer Support team regarding all raised questions via the e-mail: [email protected].

Did this answer your question?