Postback macros for ad networks

At a glance: Ad networks, as part of their integration with AppsFlyer, define the content and endpoints of postbacks sent to them by AppsFlyer. Postbacks relate to app user engagement like installs, in-app events, re-engagements, and so on. 

Related integrated partner postback guides:

• Advanced Privacy
• SKAdNetwork 
• Rejected attribution postbacks

Postbacks for ad networks

• Postback configuration: To request changes to your postback settings, contact integrations@appsflyer.com or your AppsFlyer partner development manager. 
• Postback types: Postbacks are available for install and in-app events and blocked install and in-app events (due to fraud identified by Protect360 or in violation of targeting validation rules).

Postback macros

When included in a postback, macros are replaced with the user-relevant data. For example, to get the IP address of the user installing the app, include country_code=(ip) in the postback structure.  Supported macros supported are listed in the following table:

The columns in the table that follows have the following meaning:

• Source: Where the data originates from.
  • Link: Attribution links
  • SDK: AppsFlyer SDK embedded in the app or server-to-server API
  • AF: After processing by AppsFlyer
• Send all: If yes, you can receive the data of installs and events attributed to other networks or organic.  (Means not attributed to you). 
• [Base] Macros for all postbacks: Macros relevant to install, in-app event, and rejected event postbacks
• [Optional] for in-app events and rejected events as indicated in the column (rejected, in-app)

In-app event only macros

The examples that follow relate to in-app event postbacks available to partners.

&event=af_purchase&json=%7B%22af_quantity%22%3A1%2C%22
af_revenue%22%3A%2212000%22%2C%22af_currency%22%3A%
22USD%22%2C%22af_content_id%22%3A%221107%22%2C%22
af_content_type%22%3A%22default_type%22%7D%0A

{"af_quantity":1,"af_revenue":"12000","af_currency":"USD","af_content_id":"1107","af_content_type":"default_type"}

Encoded values

Postbacks may contain irregular characters, which are not alpha-numerical. To transfer these values correctly via postbacks, AppsFlyer URL-encodes non-alpha-numerical values.

To decode or encode a postback use an encoding web service. 

回传示例

一般安装回传示例

http://YourCompanyDomain.com?site_id=(publisher_id)
&advertising_id=(advertiser_id)&android_id=(android_id)
&install_time=(install_unix_ts)

http://YourCompanyDomain.com?&site_id=(publisher_id)&
device_ip=(ip)&;idfa=(idfa)&install_time=(install_unix_ts)

一般应用内事件回传示例

http://YourCompanyDomain.com?site_id=(publisher_id)&
device_ip=(ip)&advertising_id=(advertiserId)&android_id=(android_id)&
install_time=(install_unix_ts)&event_name=(event_name)&currency=(currency)&
json=(event_value)

http://YourCompanyDomain.com?clickid=(clickid)&site_id=(publisher_id)&
device_ip=(ip)&idfa=(idfa)&install_time=(install_unix_ts)
&event_name=(event_name)&currency=(currency)&json=(event_value)

 In-app event postback example

事件参数:

• Event Name: af_revenue
• Event Revenue: 120.00
• Event Currency: USD
• Event Value: {"af_quantity":1,"af_revenue":"120","af_currency":"USD","af_content_id":"1107","af_content_type":"default_type"}

回传：

http://YourCompanyDomain.com?clickid=8594845&site_id=click123&device_ip=
38.166.144.142&advertising_id=121sxxxx-xxxx-xxxx-xxxx-52454bd7500b&
android_id=9aaeecc4455xxxxx&;install_time=1451923560&event_name=af_purchase&
currency=USD&revenue=120.00&json=%7B%22af_quantity%22%3A1%2C%22 />af_revenue
%22%3A%22120.10%22%2C%22af_currency%22%3A%22USD%22%2C%22af_content_id
%22%3A%221107%22%2C%22af_content_type%22%3A%22default_type%22%7D%0A