SKAdNetwork (SKAN) overview dashboard by AppsFlyer

At a glance: The SKAdNetwork (SKAN) dashboard provides iOS campaign metrics reported by iOS SKAN postbacks and additional data points during an initial 12-72 hour measurement period. Data is displayed by install or postback arrival date. 


Dashboard principles

The dashboard contains SKAN campaign performance data and adheres to the following principles:

  • Non-organic metrics in the dashboard are calculated using iOS postback data received by AppsFlyer. 
  • Organic metrics are calculated as AppsFlyer attribution data minus SKAN non-organic attribution data. 
  • Agency-driven traffic is treated as coming from a transparent agency.
  • In some cases, Apple, due to a privacy threshold mechanism, doesn't populate the conversion value. This means that an install is recorded without any addtional metrics.
  • Data freshness: 
    • Daily.
    • Postbacks received on a given day are processed at the end of the day UTC. Data is available by 08:00 UTC of the following day. Meaning postbacks received on Monday reflect in the dashboard on Tuesday morning.
    • See expected dashboard update time.

kb Related reading

SKAN dashboard view options

Display data using either the install date or postback arrival date.

To select a date display option, in AppsFlyer, go to Dashboard > SKAN Overview. In the filter bar, select a Display by date option. Additional filters and display options are described in the sections that follow. 

Dashboard use

Dashboard settings

Dashboard settings are available when your app is set to use conversion measurement, to select the conversion event. 

To select the conversion event

  1. In the upper-right side of the dashboard, click Dashboard settings.
  2. Select a conversion event.
  3. Click apply.
    Conversion metrics are calculated using this event.

Filter options

Use filters to refine the information displayed.



Display by

  • Install date
    • The install date is derived from the postback arrival time as follows: Postback arrival time-36 hours-[average last-active range]. The default [average last-active range] is 12 hours. 
  • Postback arrival date:
    • The date the postback was received by AppsFlyer
    • When you compare metrics in the AppsFlyer SKAN dashboard to those provided by ad networks consider that ad networks typically make data avaialble using the postback arrival date.
    • Organic metrics aren't available when selecting this option.
    • In the case of Google Ads, the arrival and install dates don't differ

Date range

  • The attributed install date. This date is derived using the postback arrival time.
  • If there are large numbers of installs, the inaccuracy due to timing issues is insignificant. 
  • Installs include redownloads.
  • The date range is limited to 90 days.
Media source
  • The ad network attributed with the install
  • Agency-driven traffic: The actual media source displays irrespective of the agency transparency status. Consequently, you may see media sources that you aren't familiar with. 
  • Campaign name and ID as set by the ad network. 
  • AppsFlyer translates the postback campaign ID to that of the ad network.
  • If a given campaign ID has multiple campaign names associated with it, then all names display in the dashboard. Note! The ad network provides the campaign ID and name per postback. Both campaign ID and campaign name are available in raw data and aggregated SKAN reports. 

Site ID

  • Source app displaying your ad.
  • Use to analyze the apps most beneficial to you.


  • Territory or country
  • The Geo is derived using data supplied by the ad network or using the device IP address.
  • Starting iOS 14.6 the device IP address is masked by an Apple proxy server. Meaning that the geolocation of the Apple server is reflected and not the device itself.

Install type

  • Installs
  • Redownloads reported by the app store


Available if the ad network provides this data point


Available if the ad network provides this data point
Filter bar

Headline metrics

Metric Remarks


SKAN does not report installs if the user did not engage with an ad prior to the install. AppsFlyer calculates the organic metrics using AppsFlyer attributed installs (LTV dashboard.) 

  • Non-organic: Installs attributed to a media source in the context of a paid app-to-app campaign and reported by SKAN.
  • Organic calculated by AppsFlyer includes the following: 
    • Installs not attributed by SKAN or for which no postback was received from an ad network.
    • App Clips
    • Apple Search Ads.

Touchpoints (1) 

Impressions and clicks reported by the ad network by click or API.


  • Available when revenue mode is active.
  • Divided between organic and non-organic revenue.
  • Organic revenue is calculated as the revenue of all sources minus non-organic revenue.
  • To enable a like-to-like comparison, the duration of the post-install activity window of organic and non-organic installs is the same.

Cost (1)

  • Cost reported by the ad network. Cost displays in USD irrespective of the app currency.
  • If the campaign name changes, cost displays under the most recent campaign name used. (If there are multiple campaign names)

Click-to-install rate

Click-to-install rate.

Adjacent period trend

Trend values in % indicate the change of the current metric relative to the metric of the previous equivalent period. For example, if the current period is May 1-10, the previous period is April 21-30.

(1) Currently, the metric includes all cost and touchpoint data relating to all campaigns, including SKAN campaigns. Data is reported to AppsFlyer using Xpend/Cost API.


The charts available depend on the selected measurement type.

Chart metric Remarks

User acquisition by date

Dimensions available:

  • Organic
  • Non-organic


Touch to conversion 

Views available:

  • Touchpoint dimensions:
    • Impressions
    • Clicks
  • Click-to-install rate


Installs by advertising hierarchy elements like 

  • Media source
  • Campaign
  • Site ID
  • Adset
  • Ad

Metric breakdown by advertising hierarchy elements like: 

  • Media source
  • Campaign
  • Site ID
  • Adset
  • Ad
Top events


The top events relate to both organic and non-organic users. Use the media source filter at the top of the page to distinguish between organic and non-organic users or per selected media sources. 

Top countries mceclip1.png


  • Select metrics from those available.
  • Set the primary and secondary group by dimensions to drill down into performance metrics.


About the metrics table:

  • Use the table to compare the performance of campaigns and media sources.
  • Initially, the top 20 media sources display, sorted by the number of installs in descending order. 
  • To sort the table, click on a column header. Click again to reverse the sort order.
  • Cost-related metrics (cost, impressions, and clicks) are available if at least 1 install is associated with a given campaign. Note:
    • Campaigns with 0 installs don't display at all. 
    • Some ad networks, report cost-related metrics at the adset and ad level, but report the install at the campaign level. In this case, the adset and ad cost-related metrics display with an install metric of 0. 
  • Attributed touch-type dimension limitation: Cost-related metrics can't be broken down and display as Unknown
Metric Formula/remarks


  • Total installs
  • Click-throughs
    • Users brought via click-through attribution

    • Available for installs recorded starting December 22, 2021

  • View-throughs
    • Available for installs recorded starting December 22, 2021
    • Applies to ad networks implmenting SKAdNetwork V2.2+
    • Installs brought by Facebook always display are included in the click-through metric

This data is derived from the fidelity_type field in the postback





Click-to-install rate

Installs/Clicks * 100

Converted users

Unique users performing the event
Converted users/Installs  




  • Cost reported by the ad network 
  • If the campaign name changes, cost displays under the most recent campaign name used. (If there are multiple campaign names)


In-app event metrics
In-app event name  
Event occurrences   
Table metrics available

AppsFlyer attribution vs. SKAN attribution

SKAN metrics differ from those available using the AppsFlyer attribution model. The table that follows enumerates the main causes. 


Concept SKAN


Attribution methodology supported

Apple SKAN for click- and view-through attribution. Contains traffic of app-to-app campaigns of ad networks and SRNs supporting SKAN.


AppsFlyer attribution model supports multiple attribution methods and scenarios: 

  • Mobile web
  • View-through
  • Click-through
  • App Clips
  • Web attribution 
  • Apple Search Ads
  • Owned media
  • SRN traffic (consenting users)
  • And more
Primary data source
  • SKAN postbacks
  • SDK

SDK and associated solutions. Example: Server-to-Server events.

Data freshness

SKAN data freshness. Updated 32-104 hours after install.

Real-time when the user launches and uses the app.
Time zone UTC  App-specific time zone.
Install time Derived from the iOS postback arrival time.

Reported by SDK.

Activity window

User activity during a fixed activity window [default 24 hours], starting with the app open.

Contains LTV data from the install date until the present.

Use Cohort to view data limited to cohort day 0 or cohort day 1, or both together to view a comparable measurement period.

Consider, cohort day 0 consists of less than 24 hours of activity. For example, a user installing at 18:00 on a given day has 6 hours of activity on cohort day 0.

Installs reported by
  • SKAN: Limited to non-organic installs and non-organic redownloads.
  • SDK: All installs are reported. Only first-time installs are counted for metric purposes. Meaning reattributions are disregarded. 

SDK reports all installs categorized using Rules into first-time installs and retargeting reinstalls (re-attributions). 

Advertising granularity level Campaign, adset, adset ID, ad, and ad ID.  

Full hierarchy: Campaign, campaign ID, adset, additional parameters like channel and partner. 

Redownloads vs. reinstalls

Redownloads relate to the actions of a given Apple ID user. They are not parallel to re-attributions.

Retargeting (re-engagements re-attributions) reflect in the Retargeting dashboard. They are not parallel to redownloads.

Attribution framework differences
Metric SKAN Traditional attribution
Non-organic installs 

Count of valid iOS postbacks received by AppsFlyer.

Consider, AppsFlyer doesn't get the postbacks of ad networks that haven't completed SKAN integration with AppsFlyer.

This can lead to undercounting of non-organic installs and increased organic installs.

  • Reported by SDK.
  • Attributed to a media source.
  • Counted using Rules. 
Organic installs

SDK installs minus SKAN installs.

  • Reported by SDK.
  • Not attributed to any media source.
  • Counted using Rules.

Non-organic: Revenue reported by SKAN postbacks.

Organic: Revenue reported by SDK in-app events minus non-organic revenue. 

  • Reported by SDK and server-to-server API.
Ad revenue


User-level ad revenue is attributed based on IDFV

Revenue during the activity window.

  • LTV
  • Metrics of UA and retargeting campaigns.
Metric differences

FAQ—SKAN discrepancies

Reason  Discrepancies—Q&A


Q: Why do the conversion numbers in the AppsFlyer dashboard differ to that of the ad network dashboard?

A: Reasons for discrepancies

  • Install date vs. postback arrival date:
    • AppsFlyer: The install date is derived using the iOS postback arrival time using the following formula: Install time = Postback arrival time - average (24 hours + activity window. So the default difference is 36 hours.
    • Ad network: Typically use the iOS postback arrival time as the install date without adjustment.
    • Use the display by postback arrival date option in the dashboard to eliminate this difference. 
  • Postback validation: AppsFlyer validates the iOS postbacks received and ensures that the Apple signature is valid. The ad network may send invalid postbacks disregarded by AppsFlyer. 
  • Missing postbacks: iOS Postbacks must be sent by the ad network to AppsFlyer. AppsFlyer doesn't get the postback directly from the device. If postbacks are missing, AppsFlyer has no way of knowing this.


Q: Differences between the SKAN performance API and dashboard versus the SKAN aggregate postback API?

A: The postback API date range relates to the date on which AppsFlyer received the postback. The performance API date range relates to the install date derived as described in reason A. 


Q: Do all ad networks report the Geo? 

A: No. 


Q: Why are there differences between the Overview dashboard and the SKAN dashboard.

A: See the preceding section for an overview as to reasons for discrepancies. 

Was this article helpful?