Get conversion data using AppsFlyer SDK

At a glance: Use conversion data to identify various conversion scenarios, customize user experience, and more.

Use conversion data to:

  • Send users to specific activities
  • Serve them with customized content

Due to the accuracy/latency tradeoff, conversion data for the same device IDs might differ across APIs.

Get conversion data

Conversion data is made available in the platform using any of the following:

Non-organic conversion data payload fields

Fields in the table that follows always exist for non-organic conversions, irrespective of the conversion media_source.

Fields always available
Payload field name Raw-data field name Remarks
media_source Media source

Attributed publisher. Equivalent to the pid parameter in attribution links

install_time Install time  
click_time Attributed touch time The time that a click or impression occurred in UTC
is_first_launch N/A true, false

Raw-data is divided into separate reports: organic, non-organic

af_siteid Site ID  
adgroup_id Ad ID  
adset Adset  
adset_id Adset ID  
agency Partner null, or agency name (for campaigns run by agencies)
campaign Campaign  
campaign_id Campaign ID  
http_referrer HTTP Referrer  
retargeting_conversion_type Retargeting Conversion Type "none", or retargeting_conversion_type
af_sub[n] (n=1—5) Sub Param [n] (n=1–5)  

The fields in the table that follows are available in some cases, depending on how the SRN populates the individual event. 

Fields available in some cases
Payload fields name Raw-data field name Remarks
af_channel Channel

SRNs populating this parameter:

  • Facebook
  • Google 
  • Snapchat
  • Twitter
  • Applovin

Example: Facebook—Instagram, Google—YouTube 


Note (1)


Note (1)


Note (1)


(1) Cost fields are populated with values shared by the ad network. In order for the ad network to share cost with AppsFlyer, you must enable cost integration on the integrated partners page. Some SRNs support cost-sharing in bulk. In this case, event-level cost fields return as 0. 

Additional fields

See raw-data fields dictionary for additional information.


Custom parameter names

Custom parameters cannot be called name (lower case "n". Name is valid).

If a parameter is called name, it is removed from the payload.

The following sections contain various user conversion scenarios and their corresponding conversion data payloads:

Was this article helpful?