Skip to content

App Attribution Partner Integrations

Last updated: October 6, 2026

CYBEXO Android SDK 2.0.0 forwards consent to supported recipient SDKs linked into your application. Follow the Android setup guide for your published CYB- App, denied Firebase startup defaults and privacy controls.

The host application must add each recipient’s dependency, configure its account and API keys, initialize its SDK objects, and manage its session lifecycle. Class detection alone does not establish that a service is configured or ready. Disclose every actual recipient and link its privacy information in your app’s consent information and privacy policy.

Keep Google Consent Mode enabled in the published CYBEXO App when you need this forwarding. CYBEXO supplies the consent mapping; do not add another mapper that overwrites its updates. Unknown jurisdiction, disabled forwarding or an unavailable recipient must not be interpreted as a grant.

These are the SDK versions used for integration checks. Validate the versions and optimized build used by your application.

Recipient Version Consent delivered
Firebase Analytics BoM 34.19.0 / Analytics 23.2.0 ad_storage, analytics_storage, ad_user_data and ad_personalization through its consent API.
AppsFlyer 6.17.5 setConsentData(AppsFlyerConsent): jurisdiction, data usage, ads personalization and ad storage. Outside GDPR, the jurisdiction value is false and the remaining fields are null.
Adjust 5.8.0 trackThirdPartySharing: google_dma options for eea, ad_user_data and ad_personalization.
Branch 5.21.3 Instance setDMAParamsForEEA: jurisdiction, ads personalization and user data.

The AppsFlyer, Adjust and Branch DMA APIs above do not have an analytics_storage field. Adjust and Branch do not receive an ad_storage field through these APIs. The four Google values are delivered separately to Firebase.

  • Firebase: Set denied manifest defaults before initialization, disable its separate automatic TCF reader, and follow the Firebase setup steps.
  • AppsFlyer: Initialize its object, apply CYBEXO consent, then start the session.
  • Adjust: Apply consent before the first session. Its SDK can queue the consent call before initialization.
  • Branch: Call Branch.expectDelayedSessionInitialization(true) before creating the configured instance, apply consent, then initialize the session. An absent instance reports NOT_READY.

Consent forwarding does not start or stop these SDKs, erase data, log users out, or replace ordinary host configuration. These DMA fields do not disable every unrelated collection feature. Configure each recipient’s collection controls and gate optional application events according to your collection policy.

Read CybexoCMP.getConsentSnapshot() and inspect firebaseDelivery and aapDelivery; see the Android API reference. Results are recorded separately for each recipient.

For attribution recipients, APPLIED means the API returned normally and can include a value queued before initialization. Other outcomes include NOT_LINKED, UNSUPPORTED, NOT_READY, FAILED, DISABLED, JURISDICTION_UNKNOWN and INVALID_SIGNALS. Treat those outcomes as diagnostics, not successful delivery.

Test a fresh install, accept, reject, mixed choices, withdrawal and restart. Check that consent precedes the first recipient session and that later changes reach the intended API. Local API acceptance does not prove remote reception: use your configured service accounts and provider tools to verify delivery. A saved choice, a consent API call, an HTTP response and a durable consent record are separate results.