Skip to content
AppDues
Log in
Contact salesSign up

iAd vs AdServices: what's the difference?

Apple retired iAd and replaced it with AdServices starting in iOS 14.3. The two frameworks answer the same question — which Apple Search Ads click led to an install — but they answer it under very different privacy rules. This guide explains what each framework returns, where the data gets thinner, and how to turn AdServices attribution on in an app.

The one-paragraph answer

iAd could return rich attribution detail, but only when a user opted in through App Tracking Transparency. AdServices trades some of that depth for coverage: it returns an attribution payload for every user, including people who decline tracking and people in children's apps. If you need campaign, ad group, or keyword names rather than raw IDs, you have to fetch them separately through Apple's authenticated Campaign Management API.

How the two frameworks compare

The comparison table below is the captured reference from the original article. It reflects the framework behavior as documented at the time of writing; Apple's platform rules can change, so confirm current behavior against Apple's documentation before you ship.

What iAd was and why it went away

iAd arrived in 2010 with iOS 4.0 as an in-app ad network. When Apple Search Ads launched in 2016, the in-app network side was shut down and iAd became the framework developers used to read attribution details for App Store search ads. Because it predates modern tracking limits, iAd could expose detailed attribution on-device, and any third-party SDK in the app could read that data. It was deprecated as of iOS 14.5 and was never permitted in children's apps.

What AdServices returns

AdServices, introduced in iOS 14.3 and available on macOS 11.1 and later, does not hand the app a dictionary of names. It hands the app an attribution token. The app sends that token to the AdServices REST API, which returns a small JSON payload. The endpoint requires no authentication, which is also why the payload is limited: it carries the conversion type (Download or Redownload), country or region, and several numeric IDs, but not the human-readable names for the organization, campaign, ad group, or keyword. Those names require an authorized request to the Campaign Management API using OAuth 2.0.

Field map: iAd payload vs AdServices payload

The two payloads describe the same campaign but at different levels of detail. Use this map when you migrate stored attribution fields.

When attribution is missing, thin, or nameless

Three different failures get confused in practice, and they need different fixes. First, no attribution at all: with iAd this happened whenever the user declined tracking, and it is why iAd returned nothing for children's apps. With AdServices the payload is still returned, so an empty result points to a token or network problem rather than a privacy decision. Second, thin attribution: AdServices returns IDs and a conversion type but no names, so a dashboard that shows blank campaign names is not broken — it is missing the authenticated Campaign Management API step. Third, missing click date: the clickDate field appears in the AdServices payload only when the user allows tracking through the ATT prompt, so a null click date is expected for users who declined.

Setup checklist for AdServices attribution

Work through these steps in order; each one gates the next.

  1. Update the iOS SDK to version 4.10.0, then add one line after Purchases.configure: Purchases.shared.attribution.enableAdServicesAttributionTokenCollection(). Cross-platform minimums for the same integration are react-native-purchases 5.0.0-beta.4, purchases-flutter 4.1.0, and cordova-plugin-purchases 3.0.0-rc.5.
  1. In the dashboard, open the Integrations page and select the Apple Search Ads integration.
  1. Click "Add Apple Search Ads Integration" if it has not been added before. Apple Search Ads Basic users are finished at this point.
  1. Optional, for Advanced users: grant read access to your Apple Search Ads account. AdServices payloads carry only campaign and ad group IDs, so displaying their names requires an authorized request to Apple's Campaign Management API.
  1. Submit the app for App Store review and confirm your Apple Search Ads campaigns are running.

Eligibility: the integration is available on {{OWNER_PLAN_ELIGIBILITY}} plans. Full setup documentation: {{OWNER_DOCS_LINK}}.

What the integration shows you

With the Apple Search Ads integration enabled, the dashboard reports what share of your customers and revenue trace back to Apple Search Ads, and a monthly recurring revenue chart can be segmented by ad campaign. That view is what turns raw attribution IDs into a spending decision: you can see which campaigns bring in paying subscribers rather than just installs. The integration has supported AdServices since {{OWNER_INTEGRATION_AVAILABILITY_DATE}} and is available on {{OWNER_PLAN_ELIGIBILITY}} plans.

The trade-off, restated

AdServices is the direction Apple Search Ads attribution has moved in, and the design choice behind it is deliberate. You give up some per-install richness — names, and click dates for users who decline tracking — and in exchange the payload arrives for the whole user base instead of only the opted-in slice. For most teams that is the better measurement base, because a complete picture of installs and revenue beats a detailed picture of a self-selected minority.

iAd vs AdServices framework comparison
iADAdServices
Without ATT / denying ATTNo attribution dataAttribution data
Allowing ATTAttribution data with click dateAttribution data with click date
Allowed in children's appsNoYes
Available platformsOnly iOS but deprecated as of iOS 14.5iOS 14.3+ and macOS 11.1+
Attribute app-download campaigns that originate from…Apple Search Ads CampaignsApp Store, Apple News, Stocks

Captured reference from the original article; framework behavior may have changed since publication.

Frequently asked questions

Does AdServices require the App Tracking Transparency prompt?

No. AdServices returns an attribution payload whether or not the user allows tracking. The ATT prompt only adds the clickDate field to the payload. iAd, by contrast, returned nothing when the user declined tracking.

Why does my AdServices payload show IDs but no campaign names?

The AdServices REST API is unauthenticated, so it only returns IDs. Names for the organization, campaign, ad group, and keyword come from the Campaign Management API, which requires OAuth 2.0. A dashboard that shows names has already made that authenticated request.

Can I use AdServices in a children's app?

Yes. AdServices is permitted in children's apps because it tracks installs in a privacy-focused way and withholds names without authenticated access. iAd was not allowed in children's apps.

What SDK versions support AdServices attribution?

The iOS SDK added support in version 4.10.0 with a single call after Purchases.configure. Cross-platform support arrived in react-native-purchases 5.0.0-beta.4, purchases-flutter 4.1.0, and cordova-plugin-purchases 3.0.0-rc.5.

{
"Version3.1" = { 
"iad-attribution" = true; 
"iad-org-name" = "org name";
"iad-org-id" = "40669820";
"iad-campaign-id" = "542370539"; 
"iad-campaign-name" = "campaign name"; 
"iad-purchase-date" = "2020-08-04T17:18:07Z" 
"iad-conversion-date" = "2020-08-04T17:18:07Z"; 
"iad-conversion-type" = "newdownload"; 
"iad-click-date" = "2020-08-04T17:17:00Z"; 
"iad-adgroup-id" = "542317095"; 
"iad-adgroup-name" = "adgroup name"; 
"iad-country-or-region" = "US"; 
"iad-keyword" = "keyword";
"iad-keyword-id" = "87675432";
"iad-keyword-matchtype" = "Broad";
"iad-ad-id" = "542317136";
}
}
{
  "attribution": true,
  "orgId": 40669820,
  "campaignId": 542370539,
  "conversionType": "Download",
  "adGroupId": 542317095,
  "countryOrRegion": "US",
  "keywordId": 87675432,
  "adId": 542317136
}