AppsFlyer provides a service for mobile campaign download attribution, allowing mobile app publishers to identify which downloads came from specific marketing and ad campaigns, and which are organic downloads. AppsFlyer has a unique method for user identification.

The AppsFlyer-CoolaData integration allows you to track activation, retention and other behavioral analyses and link them to the campaigns identified by AppsFlyer allowing you to optimize your campaigns by quality of customers via customer lifetime value (LTV) and virality scores as well as quantity of installs.

Example Business Questions:

  • Cohort by Users who did: Install and also did: Purchase, breakdown by Campaign Name
  • Path with pillar events: Install, Start Game, Invite Friend
  • Power KPI – track number of installs, number of active users
  1. AppsFlyer tracks downloads via the AppStore or Android Store, Google Play etc. – events that happen outside of network.
  2. AppsFlyer does unique user identification.
  3. CoolaData can combine events across an entire lifecycle of a customer from download through activation and ongoing use (retention).
  4. CoolaData does not do user identification, but needs a user ID.
  5. CoolaData uses the AppsFlyer ID as the unique user ID, saving implementers from managing and combining separate user IDs.



The integration uses a combination of standard and custom CoolaData properties. To ensure that AppsFlyer is able to send the user_id, the app developer must set the custom user ID in the app initialization stage.

  1. Log in to the AppsFlyer Dashboard
  2. Select the app you want
  3. Click on “Integrated Partners” in the Configuration menu:
  4. Search for CoolaData:
  5. In the first tab of the configuration window (“Integration parameters”) under token insert your CoolaData app key (found in Project-settings in CoolaData)
  6. Check the Enable checkbox
  7. Click Save & Close

After this initial setup, install events will be automatically sent to Cooladata.


According to Facebook and Twitter T&C, Appsflyer are unable share user level data with any 3rd party. As a result, all Facebook and Twitter installs are sent to Cooladata as organic.

How it works

The main usage scenario is tracking the Install event, captured by AppsFlyer and sent to CoolaData. When the user installs the app, an AppsFlyer event is triggered to CoolaData, containing the properties listed in the JSON below as event properties:

    "user_id”: ”{custom_user_id}”,
    "event_timestamp_epoch": "{epoch_timestamp}",
    "event_name": "install",
    "media_source”: ”{media_source}",
    "campaign_name": "{campaign_name}",
    "appsflyer_id": "{appsflyer_id}",

Event Name: Install 


  • event_name
  • user_id
  • appsflyer_id
  • event_timestamp_epoch
  • session_dua
  • session_app_id
  • session_ip
  • media_source
  • campaign_name
  • build_version

You can now start creating your widgets in CoolaData to use the events and properties sent by AppsFlyer.


 Sending in-app events

You could also postback Appsflyer in-app events to Cooladata. To set this up:

  1. In the integration configuration window go to the second tab: “In-App events”
  2.   Send In-App events to Cooladata – choose and make sure the token contains the Cooladata same app key:
  3. In the “In App Events Mapping” section – map the event names you want to send to Cooladata (“Cooladata events” column contains the event_name sent to Cooladata). Select “send value” if you also want to send the events custom properties along with the in-app events:
  4. Click on “save and close” to save the configurations. In app events are now sent to Cooladata and can be viewed in the “Live events” view.
Print Friendly, PDF & Email