The integration with a third-party App Attribution Partner (AAP) can offer seamless conversion tracking by allowing you a trusted way to link a provider and import conversions to Google Ads.
Benefits
- Streamlined integration
- Early access to new measurement features compared to other third-party app analytics providers
- Reduced reporting discrepancies between Google Ads and your app analytics
- Easier import of the data you want into Google Ads
How a third-party AAP integration works
Google Ads partners with several third-party app analytics providers to track app conversion analytics. You can learn more about how this integration works below:
Enable Google Ads app conversion tracking using a third-party AAP
Google’s App Attribution Partner (AAP) program provides third-party app analytics certification for the following select mobile measurement partners. This collaboration ensures access to best-in-class analytics for your Google Ads campaigns. Click your chosen third-party provider below to get started:
- Adjust Integration
- Airbridge Integration
- AppsFlyer Integration
- Branch Integration
- Kochava Integration
- Singular Integration
- Tenjin Integration
The methods through which you can pass app conversions and user consent to analytics providers are detailed below.
Collect app conversion events and user consent through a third-party AAP SDK integration
Adjust:
- Integrate the Adjust SDK.
- Follow these Android and iOS deeplink guides to ensure that Google can receive referring URL click identifiers from Adjust for attribution.
Note: The Adjust Android SDK v4.12+ is required for compatibility, however all Adjust iOS SDK versions are compatible.
- Provide consent status for EEA users by following these Android & iOS compliance guides, ensure "addGranularOption" for third-party sharing is enabled.
Note: The Adjust Android SDK v4.26.0+ & iOS SDK 4.25.0+ are required for compliance.
- For optimal performance, delay SDK data transmission until consent status is captured. For Android, implement the Adjust.setOfflineMode method. For iOS, implement either the setOfflineMode method, requestTrackingAuthorizationWithCompletionHandler method, or requestTrackingAuthorization method.
Airbridge:
- Integrate the Airbridge SDK.
- Follow these Android and iOS deeplink guides to ensure that Google can receive referring URL click identifiers from Airbridge for attribution.
Note: All Airbridge SDK versions are compatible.
- Provide consent status for EEA users by following these Android and iOS compliance guides.
Note: All Airbridge SDK versions are compatible.
- For optimal performance, delay SDK initialization or data transmission until consent status is captured. For Android, implement the autoStartTrackingEnabled method. For iOS, implement the autoStartTrackingEnabled method.
AppsFlyer:
- Integrate the AppsFlyer SDK.
- Follow this deeplink guide to ensure that Google can receive referring URL click identifiers from AppsFlyer for attribution.
Note: The AppsFlyer Android SDK v4.8.5+ is required for compatibility, however all AppsFlyer iOS SDK versions are compatible.
- Provide consent status for EEA users by following these Android and iOS compliance guides.
Note: The AppsFlyer Android SDK v6.13.0+ & iOS SDK v6.13.0+ are required for compliance.
- For optimal performance, delay SDK initialization or data transmission until consent status is captured. For Android, implement the start method. For iOS, implement either the start method or the waitForATTUserAuthorization method.
Branch:
- Integrate the Branch SDK.
- Follow these Android and iOSdeeplink guides to ensure that Google can receive referring URL click identifiers from Branch for attribution.
Note: The Branch Android SDK v5.1.3+ & iOS SDK v1.43.1+ are required for compatibility.
- Provide consent status for EEA users by following these Android and iOS compliance guides.
Note: The Branch Android SDK v5.9.0+ & iOS SDK v3.2.0+ are required for compliance.
- For optimal performance, delay SDK initialization or data transmission until consent status is captured. For Android, implement the expectDelayedSessionInitialization() method. For iOS, implement the didFinishLaunchingWithOptions method.
Kochava:
- Integrate the Kochava SDK.
- Follow these Android and iOS deeplink guides to ensure that Google can receive referring URL click identifiers from Kochava for attribution.
Note: All Kochava SDK versions are compatible.
- Provide consent status for EEA users by following this SDK compliance guide.
Note: The Kochava Android SDK v5.3.0+, iOS SDK v7.5.0+ or 8.1.0+ are required for compliance.
- For optimal performance, delay SDK initialization or data transmission until consent status is captured. For Android, implement the sleeping the tracker method. For iOS, implement the sleeping the tracker method.
Singular:
- Follow these Android and iOS deeplink guides to ensure that Google can receive referring URL click identifiers from Singular for attribution.
Note: The Singular Android SDK v12.0.0+ and iOS SDK v11.0.6+ are required for compatibility.
- Provide consent status for EEA users by following this Limited Data Sharing compliance guide.
- For optimal performance, obtain and set user consent status before SDK initialization. Please contact your Singular CSM for guidance.
Tenjin:
- Follow this deeplink guide to ensure Google can receive referring URL click identifiers from Tenjin for attribution.
Note: All Tenjin SDK versions are compatible.
Note: The Tenjin Android SDK v1.15.0+ & iOS SDK 1.14.0+ are required for compliance.
- For optimal performance, delay SDK initialization or data transmission until consent status is captured. For Android, implement the onCreate method. For iOS, implement the ATTrackingManager method.
Collect app conversion events and user consent through a third-party AAP server-to-server integration
Adjust:
- Integrate the Adjust S2S API.
- Additionally, configure the Adjust SDK to receive session_start conversion events, to ensure Google can receive referring URL click identifiers from Adjust for attribution. View the above SDK section for additional guidance.
Airbridge:
- Integrate the Airbridge S2S API.
- Contact your Airbridge CSM for guidance to ensure Google can receive referring URL click identifiers from Airbridge for attribution.
- Provide consent status for EEA users by following this compliance guide.
AppsFlyer:
- Integrate the AppsFlyer S2S API.
- Contact your AppsFlyer CSM for guidance to ensure Google can receive referring URL click identifiers from AppsFlyer for attribution.
- Provide consent status for EEA users by following this compliance guide.
Branch:
- Integrate the Branch S2S API.
- Include the fields below to ensure Google can receive referring URL click identifiers from Branch for attribution:
- For Android app install, pass “install_referrer_extras” field to https://api2.branch.io/v1/open
- For Android app engagement, pass “android_app_link_url” field to https://api2.branch.io/v1/open
- For iOS app engagement, pass “universal_link_url“ field to https://api2.branch.io/v1/openpass
- Provide consent status for EEA users by following this compliance guide.
Kochava:
-
Integrate the Kochava S2S API.
-
Include the fields below to ensure Google can receive referring URL click identifiers from Kochava for attribution:
- For Android app install, pass “referrer=value” field/value to https://control.kochava.com/track/json
- For Android app engagement, pass “event_name=_deeplink” and “gclid=value” fields/values to https://control.kochava.com/track/json
- For iOS app engagement, pass “event_name=_deeplink” and “gclid=value” and “gbraid=value” fields/values to https://control.kochava.com/track/json
- Provide consent status for EEA users by following these Install & Post-Install Event compliance guides.
Singular:
- Integrate the Singular S2S API.
- Include the fields below to ensure Google can receive referring URL click identifiers from Singular for attribution:
- For Android app install, pass “install_ref” field to https://s2s.singular.net/api/v1/launch
- For Android app engagement, pass “openuri” field to https://s2s.singular.net/api/v1/launch
- For iOS app engagement, pass “openuri” field to https://s2s.singular.net/api/v1/launch
- Provide consent status for EEA users by following this compliance guide.
Reduce third-party AAP reporting discrepancies
App conversion discrepancies are expected between Google Ads and third-party reports due to multiple factors, including cross-network attribution. Outside of unavoidable discrepancies, it's critical that conversion windows are aligned to reduce additional variance. Below is more information about recommended conversion window settings and reducing discrepancies:
- Adjust
- Airbridge
- AppsFlyer
- Branch
- Kochava
- Singular
- Tenjin
Note: The Google Ads support team is unable to provide help regarding third-party AAP websites or platforms. Contact your third-party measurement partner directly for guidance or troubleshooting.
