SKAdNetwork integration guide for ad networks

At a glance: Ad networks integrate with AppsFlyer for SKAdNetworks, enabling them to optimize campaigns and to be attributed to the traffic they generate.


Learn more about the AppsFlyer SKAdNetwork solution for advertisers:

SKAdNetwork solution guide | SKAdNetwork dashboard by AppsFlyer

AppsFlyer offering for ad networks 

  • Be attributed for campaign conversions:
    • Integration with AppsFlyer ensures that the ad network is attributed for all installs, in-app events, and revenue resulting from campaigns run on advertisers' behalf.
    • Without integration in place, installs, in-app events, and revenue are attributed as organic and not to the ad network. 
  • Campaign optimization:
    • The conversion value in the postback is encoded.
    • AppsFlyer enables ad networks to translate the conversion value of each postback, ensuring ad networks can optimize their campaigns based on the decoded value per app.
  • No need for direct integration with each advertiser:
    SKAd postbacks are sent only to the ad network. Advertisers can consume the data by either: 
    • Individual integration with each ad network. A solution that is not scalable, neither for ad networks nor for advertisers. 
    • A single integration with AppsFlyer. Scalable for both the advertiser and the ad network.
  • Increase your prominence in AppsFlyer: 
    • Ad networks having SKAdNetwork integration are certified and identified as such in the AppsFlyer dashboard. 
    • This assures advertisers that they are working with ad networks that can be measured deterministically via this attribution model.

SKAdNetwork data flow


The full SKAd postback flow is as follows:

  1. iOS sends the SKAd postback to the attributed ad network.
  2. The ad network does one of the following:
    • Enrich and forward: Enrich the SKAd postback with the ad network campaign ID (to overcome the SKAdNetwork limitation of 100 campaign IDs), campaign name, and the iOS device IP address. 
    • Redirect: The network requests the iOS device to redirect the postback directly to AppsFlyer. In this case, campaign data enrichment will be performed via a separate API between AppsFlyer and the ad network.
  3. AppsFlyer validates and decodes the postback. Then, it sends the decoded and enriched postback to the ad network (in parallel to sharing it with the advertiser).

Main integration parts

SKAdNetwork integration between AppsFlyer and ad networks consists of the following main parts as described in this article:

  • Ad networks send SKAdNetwork data to AppsFlyer
  • Ad networks receive enriched and decoded data from AppsFlyer via postbacks

Send data to AppsFlyer

After the ad network receives the SKAd postback from the device, the ad network forwards it to AppsFlyer using one of the following methods:

  • Enrich and forward (POST)
  • Redirect (HTTP 307 redirect method)

Upon receipt of a SKAd postback, AppsFlyer performs the following:

  • Postback validation: Ensure that it is unique.
  • Conversion value decode: Generate attribution install/in-app event records.
  • Send decoded postbacks to the ad network.
  • Make attribution data available to advertisers via dashboards and reports.

Enrich and forward

Using this method, ad networks forward each postback received from the device to AppsFlyer.

The ad network:

  • Receives the postback from the iOS device
  • [Mandatory] Enriches the postback with:
    • Ad network campaign ID and campaign name
    • IP address received from the device, required mainly for geo resolution purposes. 
    • The timestamp of the postback sent from the iOS device
  • [Optional] Enrich the postback with:
    • Adset ID and name
    • Ad ID and name
  • Sends the postback to AppsFlyer.
  • Note! Before sending the postback to AppsFlyer, validate the Apple attribution signature using the content of the outgoing postback to ensure that you didn't inadvertently corrupt the data. 
SKAdNetwork enriched postback protocol

HTTP method POST
Accepted content types application/json
Return codes

200 OK: Postback received has a valid format. 

400: Bad request: Malformed JSON, empty, JSON, missing mandatory fields.

SKAdNetwork enriched postback JSON parameters





version String

SKAdNetwork version

Example: "version":"2.0"

SKAd postback
ad-network-id String

Ad network ID

Example: "ad-network-id":" abc123defg.skadnetwork"

SKAd postback
campaign-id Integer

SKAdNetwork campaign ID

Example: "campaign-id":23

SKAd postback
transaction-id String

SKAdNetwork postback transaction ID

SKAd postback
app-id Integer Target app ID SKAd postback
attribution-signature String Attribution signature SKAd postback 
redownload Boolean When redownload = true, it means the user downloaded the app from the app store again. SKAd postback
source-app-id Integer

Source App ID (publisher)

SKAd postback
conversion-value Integer

AppsFlyer SDK sets the conversion value according to advertiser settings.

SKAd postback 
ad-network-campaign-id String

To enable a common language between ad networks, advertisers, and AppsFlyer, you must provide your campaign-id.

Ad network
ad-network-campaign-name String Ad network campaign name associated with the ad network campaign ID. This name displays in dashboards and reports.  Ad network
ad-network-adset-id String

Ad network adset ID

Ad network
ad-network-adset-name String

Ad network adset name

Ad network
ad-network-ad-name String

Ad network ad name

Ad network
ad-network-ad-id String

Ad network ad ID

Ad network
ip String

The IP address of the device sending the postback.

iPv4 and IPv6 addresses supported.

Example: "ip":""

Ad network
timestamp String

Time the ad network received the SKAdNetwork postback. A 10-digit epoch UNIX timestamp. [Optional] 13-digit epoch timestamp permitted.


August 4, 2020, 07:25 UTC translates to "timestamp": "1596525944"

Ad network
fidelity-type Integer

Differentiate between ad presentation options that affect attribution. Indicated using the values 0 and1 as follows: 

  • View-though ads (0)
  • Storekit-rendered ads (1)

Mandatory field starting SKAdNetwork V2.2

SKAd postback (V2.2+)
did-win Boolean

Used to distinguish between campaigns contributing or attributed with the install. 

  • If true, the campaign is attributed for bringing the install.
  • If false, the campaign is recognized as contributing to the install
SKAd postback (V3.0+)
ad-network-source-app-id String

Populate with the publisher ID that you associate with the app publishing the ad. This is usually the ID you allocated to the publisher, and not the ID generated by Apple. 

Ad network

 Ad network optional parameters sent via query params







Name of the ad network

Example: ad_network_name=your_network

Ad network



The app id as it appears in AppsFlyer. Always has the prefix id.


Ad network

Curl example—enriched SKAd postback with optional query params

curl --location --request POST '' \
  --header 'Content-type: application/json' \
  --data-raw '{
      "app-id": 888707086,
      "ip": "",
      "ad-network-campaign-name": "skadnetwork_abc_campaign",
      "source-app-id": 888707074,
      "ad-network-id": "abcabcabc.skadnetwork",
      "transaction-id": "68eb3d91-15f5-44ee-9267-25c7655c20b6",
      "redownload": false,
      "attribution-signature": "MDYCGQCsQ4y8d4BlYU9b8Qb9BPWPi+ixk/OiRysCGQDZZ8fpJnuqs9my8iSQVbJO/oU1AXUROYU=",
      "timestamp": "1596525944",
      "ad-network-campaign-id": "222222",
      "conversion-value": 63,
      "campaign-id": 99



Using this method, the ad network responds to the device with an HTTP redirect command (307), requesting the device to send the postback directly to AppsFlyer. 

The redirect method has the following advantages:

  • Increased advertiser trust: The MMP acts on behalf of an advertiser. By providing AppsFlyer access to the postback firsthand, advertisers are confident that postbacks are not manipulated in transit.
  • No processing required by the ad network: Ad networks respond with the redirect command (to the device), thus eliminating the need to process postbacks. In comparison, the enrich and forward method requires that ad networks consume the postback, enrich it with additional parameters, and finally forward it to AppsFlyer.


  1. Configure your server to respond with an HTTP 307 response redirecting the postback to
  2. Append query params that contain campaign details using the query params listed in the table that follows. Regard the sending of your campaign details as mandatory. Campaign details enable us to enrich SKAdNetwork data with cost and other campaign data and enable advertisers to effectively optimize campaigns.

Example redirect URL

Query param


ad-network-campaign-id Campaign ID
ad-network-campaign-name Campaign name
ad-network-adset-id Ad set ID
ad-network-adset-name Ad set name
ad-network-ad-id Ad ID
ad-network-ad-name Ad name
Query params for campaign details (not mandatory)


Receive data from AppsFlyer

Prior to receiving your first postback, take into consideration the following: 

  • Ad networks must define the postback end-point and template (reach out to your AppsFlyer Partner Development Manager or to to ensure this is in place).
  • AppsFlyer sends SKAdNetwork postbacks using the same mechanism as with the existing postbacks sent to you.


  • For each postback sent from the ad network to AppsFlyer, AppsFlyer sends:
    • One install postback. Redownloads are signaled by the redownload parameter. 
    • Zero to several in-app event postbacks. The exact number depends on the translation of the conversion value. See simulated postbacks.
  • When you consume postbacks, the same install or event can be attributed by more than one AppsFlyer attribution solution. Use the attribution_source parameter to differentiate between postback types. 

Postback macros

Postback macro (name)


Format and example Relevant to in-app events only


The app publishing the ad (source app ID)

String: 876534



Estimated by AppsFlyer based on the updateConversion window. Provided as a 10-digit UNIX epoch timestamp or as a human-readable timestamp

  • String: 1596119460 
  • Translates to July 30, 2020, 14:31 UTC.


Time the postback was received by the ad network from the iOS device. Reported by the ad network. Provided as a 10-digit UNIX epoch timestamp or as a human-readable timestamp

  • String: 1596119460 
  • Translates to July 30, 2020, 14:31 UTC



Time AppsFlyer received the postback from the ad network. Provided as a 10-digit UNIX epoch timestamp or as a human-readable timestamp


  • String: 1596119460 
  • Translates to July 30, 2020, 14:31 UTC



Event name 

  • af_skad_revenue
  • af_login
  • af_skad_revenue
  • or as set by the advertiser 

String: af_skad_revenue, abc123




Revenue amount using the specified currency code

Number: 5, 20, 0.4



Currency code being the app-specific currency set by the advertiser

String: EUR, USD, ZAR



The source of the attribution data:

SKAdNetwork: skadnetwork

String: skadnetwork



App ID (advertiser app)

String: ID123456790



Install country determined using IP address sent by the ad network

String: US, UK, ZA 



Campaign name populated using ad-network-campaign-name sent in the postback from the ad network

String: UA_US_23+



Ad network Campaign ID populated using ad network-campaign-id sent in the postback from the ad network

String: 3456745



Possible values: true, false

When redownload = true, it means the user downloaded the app from the app store again

Boolean: true, false



Events received during the first 72-hours after an advertiser changes the SKAdNetwork settings in the dashboard. Due to the various timers employed by SKAdNetwork AppsFlyer can't map the event accurately.

Boolean: true, false



SKAdNetwork campaign ID as provided by the original SKAdNetwork postback

56, 23



A unique random identifier enabling partners to identify duplicate postbacks




Name/ID of the corresponding event in the ad network platform




SKAdNetwork postback transaction ID

Note: The advertiser must explicitly allow us to share the transaction_id with you. Ask the advertiser to do so in the Integration tab.




ad_network_adset_id Added to the iOS postback by the ad network String  
ad_network_adset_name Added to the iOS postback by the ad network String  
ad_network_ad_name Added to the iOS postback by the ad network String  
ad_network_ad_id Added to the iOS postback by the ad network String  
skad_min_event_counter See note (1)


skad_max_event_counter See note (1)


skad-min-time-post-install See note (2)


skad-max-time-post-install See note (2)


skad_min_event_revenue See note (3) Real number Yes
skad_max_event_revenue See note (3)

Real number 



  1. The number of event occurrences is calculated using the following formula:
    [round up (min_event_counter+max_event_counter) / 2]
    Note! The value must be rounded up to the nearest integer.
    • Example:
      • A. If min=0 and max=1 the number of events is 1.
      • B. If min=0 and max =10 the number of events is 5.
  2. AppsFlyer uses these values to determine the install time relative to the postback arrival time. Ad networks don't need to make use of these macros. 
  3. AppsFlyer uses these values to determine the revenue of an event. Ad networks don't need to make use of these macros. 
Macros available in the postback to Ad network partners

SKAd postback examples

Example of an install SKAd postback sent by AppsFlyer

Example of an in-app SKAd postback sent by AppsFlyer

Integration testing

The AppsFlyer solution for SKAdNetwork is live and ready. To validate the integration with AppsFlyer, use either or both of the following methods. 

  • Real SKAdNetwork postbacks: based on actual SKAd traffic received by the network
  • Simulated postbacks: based on AppsFlyer test apps

To receive real SKAdNetwork postbacks from iOS devices, the ad network completes the following:

To receive simulated postbacks:

Real environment

Using this method, the ad network sends AppsFlyer actual SKAd postbacks from live apps. 

Responsibility Action
Ad network Notify AppsFlyer via your partner development manager (or email to as to your SKAdNetwork network ID, provided by Apple.
Ad network and AppsFlyer Agree on a mutual customer (having integrated the most recent AppsFlyer SDK) to use for postback integration verification.
Ad network Send app SKAd postbacks to AppsFlyer, using one of the methods described in this article.
AppsFlyer Send decoded postbacks to the ad network in accordance with the conversion value mapping set by the advertiser.
Testing integration
Responsibility Action
Ad network Notify AppsFlyer as to the quantity of SKAd postbacks sent during a specified period for the agreed mutual customer.
AppsFlyer Verify the count of postbacks received versus the count sent by the ad network.

Share with the ad network the count of postbacks sent to the network for a given app broken down by type:

  • Install/redownload postbacks
  • In-app postbacks.
Note: If you use the same endpoint for probabilistic postbacks, ensure that you filter using attribution_source=skadnetwork to distinguish SKAd Network postbacks from other postbacks.
Test criteria

Simulated postbacks

  • Using this method, the ad network sends AppsFlyer preprepared postbacks to AppsFlyer test apps, as detailed in the table below. AppsFlyer replies with decoded postbacks to the ad network.
  • Each test app has a different conversion value mapping, as detailed in the table.
App ID Conversion mode Instructions

Revenue, in $1 units

Expected results: 

  1. In the Integration tab, enable in-app events postbacks
  2. Select event name af_skad_revenue and map to your event identifier.
  3. Save configuration.
  4. In a postback, send conversion value = 7.
  5. AppsFlyer responds with:
    • Install postback
    • af_skad_revenue postback with value of $7
id888707086 Conversion, including the in-app events:
  • af_level_complete
  • af_login
  • af_skad_revenue
  • af_register
  • af_subscription
  • af_custom_event
  1. In the Integration tab, enable in-app events postbacks
  2. Select each of the in-app events listed and map it to your event identifier. 
  3. Save configuration.
  4. In a postback, send conversion value = 63.
  5. AppsFlyer responds with:
    • Install postback
    • af_level_complete postback
    • af_login postback
    • af_skad_revenue postback
    • af_register postback
    • af_subscription postback
    • af_custom_event postback
id888707087 Engagement, measured using af_skad_revenue event
  1. In the Integration tab, enable in-app events postbacks
  2. Map the event name af_skad_revenue and to your event identifier.
  3. Save configuration.
  4. In a postback, send conversion value = 3.
  5. AppsFlyer responds with:
    • Install postback
    • 3 postbacks of af_skad_revenue event
Responsibility Action
Ad network Configure your SKAdNetwork network ID (provided by Apple) and SKAD postback template on the postback management platform. For queries and assistance, contact
Ad network
  1. Activate the test apps.
  2. For each app complete the instructions column in the previous table. 
  3. Send simulated postbacks, using the test apps listed in the preceding table. Considerations when sending simulated postbacks:
    • Set the app_id and conversion value as listed in the preceding table. 
    • Since Ad networks can't generate Apple compatible signatures, the simulated postbacks don't have to include the signature fields. AppsFlyer will not verify them for simulated postbacks.
    • Ad networks send the postback using either the POST or REDIRECT approach.
AppsFlyer Responds with the decoded postbacks to the endpoint designated by the ad network during integration
Integration steps
Responsibility Action
AppsFlyer Process the postback and sends postbacks to the ad network.
Ad network
  • Ad network receives and decodes the translated postbacks.
  • In-app postbacks sent by AppsFlyer match the expected flows. For example, conversion value 3 for app ID888707087, the ad network receives 3 postbacks of af_skad_revenue event. 
Test criteria


Clarifications relating to mandatory fields, enrichment, certification, and more.


Questions and answers about postbacks

Are the enrichment fields mandatory? 

For the present, we will process the postback even if it is missing one or more of the following enrichment parameters. Consider that the information is required for the following reasons: 

  • Ad network campaign ID: If we have cost integration with you then this is reported using your campaign ID. 
  • Ad network campaign name: Many advertisers relate to the campaign name and not the campaign number. 
  • IP address: Required for geo resolution. 
  • Timestamp: Assists us to attribute the install to the correct date. 

Can we send either our campaign ID, or our campaign name, but not both?

See the previous answer. Consider populating both ID and name with the same value. 

We are using Enrich and Forward. Can we add key-value pairs that are not in the AppsFlyer specification? 

Yes, you can. We will process the postback and disregard the extra information provided that the attribution signature is valid

Are the SKAdNetwork postback templates distinct from the existing postback templates?

Yes. The flow and structure differ.

Will we receive a SKAdNetwork postback and a probabilistic/deterministic modeling postback related to the same install, meaning duplicate reporting of the same install?

Yes. For each case, we record an install attributed to you, irrespective of method, we will send you a postback.

Use attribution_source to differentiate SKAdNetwork postbacks.


Are we required to process the postback from AppsFlyer?

No. Consider, that best practice is to optimize campaigns according to user-quality reported via the postback. 

Are we expected to call AppsFlyer attribution links or is it sufficient to send the postback with the SKAdNetwork payload and enriched data?

It is sufficient to send us the SKAdNetwork payload and enriched data.

What is required for us to be certified in the AppsFlyer dashboard as a SKAdNetwork integrated partner?

  • Complete integration using one of the methods listed in this article
  • Send us postbacks of apps using AppsFlyer as their attribution partner

How does the limit of 100 SKAdNetwork campaign IDs impact me

The 1-100 limit relates to the way you sign and number your campaigns in Apple. It means that at any time, you can have 100 simultaneous unique campaigns. We allow you to enrich the postback with your actual campaign name and ID. Meaning you map the SKAdNetwork campaign ID to your actual campaign IDs in use at the time the postback is received. Doing so means that the 100 ID limit does not restrict the number of campaigns that you measure in AppsFlyer provided of course that you don't have more than 100 simultaneous campaigns for a given app. 

Was this article helpful?