Meta

Guide · 27 Oct 2026

Meta iOS app campaigns: check ATT consent and AEM eligibility

Review tracking permission, recorded consent states, and event eligibility separately when preparing or troubleshooting an iOS app campaign.

G2P Media · · 4 min read

Meta iOS app campaigns: check ATT consent and AEM eligibilityMeta

At a glance

FieldDetail
WhatVerify ATT consent handling before diagnosing Meta iOS app event eligibility.
Who it matters toApp buyers and developers preparing Meta iOS app promotion campaigns.
WhereiOS apps using the Meta SDK or a mobile measurement partner; partner-specific checks below cover Adjust and AppsFlyer.
When it appliesBefore launch, after consent-flow changes, or when app events appear ineligible for AEM.
ActionTest consent states, inspect the implemented SDK behavior, and check the selected event's eligibility.

Meta iOS app campaigns need a consent check alongside an event eligibility check. Our suggested review separates Apple's tracking permission, the app's recorded consent state, and Meta's acceptance of an event for Aggregated Event Measurement (AEM). A successful consent prompt alone does not establish that every downstream setting is ready.

Establish the permission boundary

Apple requires App Tracking Transparency (ATT) permission before tracking or accessing the advertising identifier on iOS 14.5 and later. Its definition covers linking app data with other companies' data for targeted advertising or advertising measurement. The system prompt must explain the purpose. Without permission, the Identifier for Advertisers (IDFA) is zeroed and the app may not perform that tracking. Apple's privacy guidance establishes this boundary.

Apple also says a hashed email address or another identifier cannot replace ATT permission for tracking. Review the proposed data use before changing sharing settings to resolve an eligibility warning. Our interpretation: an integration's technical ability to transmit an event is a separate question from whether the intended processing is permitted.

Gather the prerequisites

Use this as a review worksheet rather than a universal installation sequence. Each integration has its own behavior.

PrerequisiteSource-backed behaviorLimitationSuggested check
ATT purpose explanationApple requires a purpose string in the system prompt.Permission must be obtained for tracking.Match the explanation to the actual data use.
Meta SDK and iOS versionsMeta documents different handling of its advertiser tracking flag by version.The older manual-setting approach does not apply to every version combination.Record both versions before selecting implementation instructions.
Consent-state visibilityAdjust exports ATT status and supports notifications when it changes.A missing status needs investigation.Include consent information in the verification evidence.
Event eligibilityAppsFlyer directs advertisers to Meta Events Manager to check AEM eligibility.Eligibility must be checked for the affected app event.Inspect the intended optimization event.

Check the SDK behavior actually installed

In Meta's official iOS SDK source, the deprecation guidance says the manual advertiser tracking flag is unused with Facebook SDK version 17 and later on iOS 17 and later. That combination relies on Apple's tracking authorization status.

Ask the developer to identify the installed SDK version and the iOS versions under test. Then review the implementation against that combination. Do not assume that copying an older manual flag setter will change consent handling in a newer build. This check concerns the Meta SDK; it does not establish how a separate measurement partner processes consent.

Adjust's consent export documentation distinguishes Not Determined, Restricted, Denied, and Authorized. It also distinguishes a null value, which can indicate an older iOS version or a missing ATT framework implementation. A denied status can reflect a device setting that prevents the prompt from appearing.

For an app using Adjust, include ATT status in supported server callbacks or cloud storage exports and review the ATT update activity when consent changes. These are Adjust-specific verification options, not requirements for every Meta integration.

Our suggested test record pairs prompt behavior, exported status, and event timing. Check authorization, denial, an unanswered prompt, and restriction where available. Investigate missing values separately from explicit refusal.

Adjust's initialization guidance describes an approach that initializes the SDK before showing the prompt. It can initially record an install without the IDFA and rerun attribution after authorization. Using Adjust's consent wrapper notifies its backend immediately when status changes; calling Apple's authorization method directly can introduce a notification delay.

For that implementation, compare the initial record with later consent and attribution updates. A record captured before the response should not be treated as proof that the subsequent consent update failed.

Check AEM eligibility in the chosen integration

AppsFlyer's AEM documentation describes Advanced data sharing as making qualifying events available to Meta when an advertising identifier is unavailable. With that setting off, sharing is limited to conversions from users with an available advertising identifier. AppsFlyer explicitly requires advertisers to check applicable platform policies and regulations before enabling it.

For AppsFlyer integrations, inspect that setting and the affected event's AEM eligibility in Meta Events Manager. Sending an event and qualifying for AEM are distinct checks. Account-specific eligibility is not specified in the cited documentation and must be verified in the account.

What to review

  • Check the tracking purpose and permission behavior against Apple's requirements.
  • Record the installed Meta SDK and tested iOS versions before changing tracking flag code.
  • Compare observed consent choices with the measurement partner's exported states and updates.
  • Keep initial event timing and later consent updates together in the test record.
  • Check the selected event's AEM eligibility and review data sharing before changing integration settings.

Use an iOS measurement review to document these consent and eligibility checks alongside the app's reporting setup.

Discuss your app.

Discuss your app