Google Ads

Guide · 27 Oct 2026

SKAdNetwork and AdAttributionKit setup: check network support

Apple framework compatibility, buying-network support and postback delivery require separate checks before an iOS attribution change.

G2P Media · · 4 min read

SKAdNetwork and AdAttributionKit setup: check network supportGoogle Ads

At a glance

FieldDetail
WhatDecide which Apple attribution framework and conversion-value setup each buying network can use.
Who it matters toiOS app advertisers buying on Google Ads or Meta.
WhereSKAdNetwork covers the App Store; AdAttributionKit also supports alternative app marketplaces. Network support needs a separate check.
When it appliesWhen implementing attribution, changing the conversion schema or testing postback delivery.
ActionConfirm network support, assign schema ownership and verify app behavior separately from reporting.

SKAdNetwork and AdAttributionKit setup requires separate decisions about Apple’s APIs, the buying network’s supported measurement and the app’s implementation. Apple documents interoperability between the frameworks, while Google’s guide explicitly says Google Ads does not currently support AdAttributionKit for attribution. Our suggested approach is to confirm those boundaries before changing the app. Apple’s interoperability documentation and Google’s iOS campaign guide establish different parts of that decision.

Confirm the supported path

Apple says the conversion-update API depends on the framework the ad network uses. Integrations supporting both frameworks can call both APIs. Apple also documents bridging from SKAdNetwork conversion updates into AdAttributionKit. These statements describe framework behavior; they do not establish every network’s product support.

Apple resolves impressions across both frameworks to a single winning impression for a conversion. Our interpretation: a dual-framework implementation should not be treated as two independent acquisition results. Keep framework compatibility and the buyer’s reporting definition separate when reviewing a proposed migration. Apple explains these interactions.

Decision or approachSource-backed capabilityLimitationSuggested check
Google Ads SKAN install measurementGoogle documents integration through Google Analytics, another measurement SDK or manual implementation.Google states that AdAttributionKit attribution is not currently supported.Confirm the intended integration against Google’s supported path.
Google Ads post-install schemaGoogle Analytics, an App Attribution Partner or the Google Ads API can configure the schema.Google’s conversion modeling uses fine conversion values, not coarse values.Verify the chosen schema and biddable events.
Meta through AppsFlyerAppsFlyer documents schema sharing and receipt of Meta SKAN data.This is a vendor-specific SKAN integration.Check both sharing directions and the SDK responsible for conversion updates.
Advertiser postback copiesApple lets the advertised app opt in to winning-postback copies.Copies require app configuration and a receiving server.Review endpoint configuration separately from network reporting.

The Google rows follow its campaign guide and schema documentation. The Meta row follows AppsFlyer’s integration guide; the endpoint row follows Apple’s advertised-app configuration. Meta AdAttributionKit eligibility: Not specified in the cited documentation.

Assign the schema and conversion-update responsibility

For Google Ads, choose where to configure the SKAN schema. Google recommends choosing one place. It also says the schema must be integrated with the Google Ads account for optimization, and the intended optimization events should exist as biddable conversion events in Google Ads. Our suggested check is to compare the schema’s event definitions with the conversion settings before approving implementation. Google’s schema guide distinguishes creating the mapping from connecting it for campaign use.

For advertisers using AppsFlyer with Meta, AppsFlyer describes two connections: permission for Meta to share SKAN data, and sharing the conversion-value schema with Meta. Its documented integration transfers conversion-value updating from Meta’s SDK to the AppsFlyer SDK. Check that the intended event mappings accompany that change; SDK presence alone does not complete the documented process. AppsFlyer’s instructions apply to this integration, so use them only when that is the app’s chosen route.

Configure the advertised app and optional copies

Apple’s advertised-app instructions say a conversion-value update must occur at least once to start the postback’s conversion window, and recommend doing so at first launch. Ask the app team to identify the implementation that performs this update.

Receiving advertiser copies is a separate opt-in. Apple documents configuring the app’s Information Property List and a server with a valid SSL certificate that accepts HTTPS POST messages. Apps using both frameworks need both postback-copy URLs configured. Reengagement copies require an additional opt-in. Review the intended copy types with the team operating the receiving server. Apple’s configuration guide describes these requirements.

Verify app behavior and reporting separately

Apple’s Development Postbacks tool can test AdAttributionKit without interacting with publisher ads or publishing the app. The specified app must be installed on the test device. The tool lets developers vary returned data to test server handling of different privacy tiers; Apple recommends a testing URL separate from production.

Development postbacks also use a different signing key from production. Our suggested acceptance check is to record which environment and key were tested before treating successful receipt as evidence about production delivery. Apple’s testing documentation establishes these distinctions.

For reporting verification, Google documents a SKAN conversions report under Campaigns, Reports, Other. In the AppsFlyer–Meta route, check the integration’s data-pull status and event mappings. AppsFlyer identifies missing mappings as a reason installs can appear without the intended in-app event measurement. These are separate checks from testing an Apple postback receiver. Google’s reporting instructions and AppsFlyer’s troubleshooting guidance support that separation.

What to review

  • Check network support before replacing a working SKAN integration.
  • Compare Google Ads biddable events with the configured conversion schema.
  • Check which SDK updates conversion values in the selected Meta integration.
  • Review optional postback copies independently from dashboard access.
  • Keep development-postback tests and production reporting checks distinct.

Use the iOS measurement review to document the app implementation, schema responsibility and reporting checks together.

Discuss your app.

Discuss your app