Skip to content

iOS Attribution Integrations

Last updated: October 12, 2026

CYBEXO iOS SDK 2.0.2 detects supported recipient SDKs linked into your app and forwards the current consent using their native APIs. Add only the recipients you actually use. Configure their real app accounts and disclose them in your privacy information.

Recipient Locally checked version Consent API
Firebase Analytics 12.4.0 Four Google consent values via setConsent. The review host uses FirebaseAnalyticsCore without advertising identifier support.
AppsFlyer 6.17.7 Native AppsFlyerConsent object for GDPR applicability, data usage, personalization and ad storage; manual consent is authoritative.
Adjust 5.8.0 ADJThirdPartySharing with google_dma options for eea, ad_user_data and ad_personalization, plus measurement consent.
Branch 3.14.2 Class DMA API and exported consumer-protection attribution levels.

The recipient APIs differ. A provider’s DMA object is not a copy of all four Firebase fields. CYBEXO also applies reversible collection restrictions to these iOS integrations: AppsFlyer stop state, Adjust enable/disable and measurement consent, and Branch attribution level. These attribution integrations require both advertising storage and analytics storage before enabling tracking; advertising user-data and personalization choices still control their distinct native fields. Ordinary denial does not invoke Adjust’s permanent erasure API or log the visitor out of Branch.

Follow the iOS setup guide for denied defaults, readiness observation and Firebase collection gating. Keep optional recipients inactive until their actual consent has been applied. After configuring a recipient, call CybexoCMP.shared.retryRecipientConsent() before starting its first session.

  • AppsFlyer: configure your actual developer key and Apple app ID. Apply consent before calling its start API.
  • Adjust: configure the actual app token and intended environment. Its native consent calls can queue before SDK initialization; local acceptance is not proof of a sent session.
  • Branch: configure a real Branch key. Restoring an attribution level can itself initialize a session, so configuration and collection policy must be ready before a grant is delivered. An absent key reports SDK_NOT_CONFIGURED on a grant attempt and retains that pending update. Denied updates can apply locally without a key.

No placeholder credential constitutes a working integration. The SDK does not create provider accounts or obtain Apple’s App Tracking Transparency permission. Unknown jurisdiction is treated conservatively.

Read getConsentSnapshot()["aapDelivery"] for per-provider diagnostics. LOCAL_API_APPLIED means the supported native calls completed locally; it can include a queued provider update. An absent, unsupported or unconfigured recipient is not reported as successful delivery. Missing or unconfigured recipients receive a bounded discovery retry. The latest state is also reapplied on foreground validation and when the host calls retryRecipientConsent(); call it after any later recipient configuration.

Test acceptance, rejection, independent analytics, personalization-only denial, withdrawal, restart and late configuration with the exact versions linked into your release app. Verify that denial does not erase the provider’s account identity, log out the app user or queue optional events for later replay.

The published integration checks cover real linked SDKs locally. Remote reception must be verified separately in your configured AppsFlyer, Adjust and Branch accounts. Those results are not interchangeable with Firebase DebugView or CYBEXO consent reporting.