Disabling Install Postbacks for CPA Based Campaigns

  • Advertisers
  • Ad Networks

Who Needs it?

How can you run a CPA (Cost per action) based mobile campaign?

Ad networks can use mapped in-app event postbacks sent from AppsFlyer for charging, instead of the standard install postbacks.

However, some networks require getting ONLY the specific in-app event postback (e.g. purchase) to effectively run a CPA campaign. These networks wish to prevent install postbacks, but still need to receive postbacks for specific in-app events.

By adding a simple parameter on AppsFlyer's attribution links this can be easily achieved. Note that installs, that come from these attribution links, are still attributed, aggregated and presented normally on AppsFlyer's dashboard and data.

Preventing Install Postbacks

Add af_installpostback=false as an additional parameter on the link to disable the install postbacks.


Installs coming from the link below do not result in install postbacks:


For a list of AppsFlyer's available attribution links macros go here.

Who Can Disable Install Postbacks?

Since disabling install postbacks entails but a simple addition on the attribution link, it can be added by either the advertiser or the ad network.

SRNs, which don't use external attribution links, can't use the af_installpostback parameter, and therefore can't disable install postbacks.

Effects of Disabling an Install Postback

  • No postback to the attributed media source
  • No postback to third party analytic networks such as Mixpanel, Localytics or Amplitude (full list of 3rd Party Analytic Partners here)
  • No postback to All-Installs networks
  • No raw data installation postback


Disabling install postbacks can cause serious reconciliation problems between advertisers and ad networks if not agreed upon in advance. Advertisers and ad networks MUST have consent from one another BEFORE starting to use attribution links with disabled install postbacks.

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

Page Contents: