At a glance: Starting iOS 15, configure your app to send postbacks directly to AppsFlyer in addition to sending them to ad networks. This allows AppsFlyer to validate the conversion value (CV) and verify postback integrity.
Why send postbacks to AppsFlyer?
Postbacks contain information critical to advertisers—specifically, the conversion value (CV) used to measure user quality. In postbacks, the CV is neither encrypted nor part of the postback signature. As a result, the CV as reported by the ad network can't be validated and is open to manipulation.
Configuring your app to send a copy of postbacks directly to AppsFlyer helps prevent CV manipulation by allowing AppsFlyer to:
- Validate postbacks and conversion values from all ad networks
- Verify postback integrity by comparing the postbacks sent directly to AppsFlyer with those sent via the ad network
Note! AppsFlyer must still receive ad network postbacks as they contain additional data (for example, campaign name).
Copies of postbacks are available via SKAdNetwork reporting options.
Configure your app to send a copy of postbacks to AppsFlyer
To register the AppsFlyer endpoint:
Info.plistin the Project navigator in Xcode.
Click the Add button (+) beside a key in the property list editor and press Return.
Type the key name NSAdvertising Attribution Report Endpoint.
Choose String from the pop-up menu in the Type column.
- Type the AppsFlyer endpoint URL in the format
Don't believe everything you hear!
Are these statements true or false?
- Advertisers no longer depend on ad networks to get postbacks.
- The advertiser still depends on the ad network to decode significant pieces of data. For example, only the ad network can map the SKAdNetwork campaign ID to the campaign name.
- As soon as I've set an additional endpoint, copies of all postbacks are sent there.
- The additional endpoint feature is only available for devices running iOS 15+. Postback copies aren't sent from devices running earlier versions.