About tracking app conversions with an App Attribution Partner

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 that you want into Google Ads

How 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) programme 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:

The methods through which you can pass app conversions to analytics providers are detailed below:

Collect app conversion events through a third-party AAP SDK integration

Leverage third-party AAP SDK integration to collect and pass app conversion events to Google Ads for campaign attribution. Click on your chosen provider below to configure a third-party SDK:

Adjust: Follow these Android and iOS deeplink guides to ensure that Google can receive referring URL click identifiers from Adjust for attribution. Adjust Android SDK v4.12+ is required.
Airbridge: Follow these Android and iOS deeplink guides to ensure that Google can receive referring URL click identifiers from Airbridge for attribution.
AppsFlyer: Follow this deeplink guide to ensure that Google can receive referring URL click identifiers from AppsFlyer for attribution. AppsFlyer Android SDK v4.8.5+ is required.
Branch: Follow these Android and iOS deeplink guides to ensure that Google can receive referring URL click identifiers from Branch for attribution. Branch Android SDK v5.1.3+ and iOS SDK v1.43.1+ are required.
Kochava: Follow these Android and iOS deeplink guides to ensure that Google can receive referring URL click identifiers from Kochava for attribution.
Singular: Follow these Android and iOS deeplink guides to ensure that Google can receive referring URL click identifiers from Singular for attribution. Singular Android SDK v12.0.0+ and iOS SDK v11.0.6+ are required.
Tenjin: Follow this deeplink guide to ensure that Google can receive referring URL click identifiers from Tenjin for attribution.

Collect app conversion events through a third-party AAP server-to-server integration

Use third-party AAP server-to-server integration to collect and pass app conversion events to Google Ads for campaign attribution. To configure third-party server-to-server events:

Adjust: To ensure Google can receive referring URL click identifiers from Adjust for attribution, also configure the Adjust SDK to receive session_start conversion events.
Airbridge: To ensure Google can receive referring URL click identifiers from Airbridge for attribution, contact your Airbridge CSM for guidance.
AppsFlyer: To ensure that Google can receive referring URL click identifiers from AppsFlyer for attribution, contact your AppsFlyer CSM for guidance.
Branch: To ensure that Google can receive referring URL click identifiers from Branch for attribution, include the fields below:
- 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/open
Kochava: To ensure that Google can receive referring URL click identifiers from Kochava for attribution, include the fields below:
- 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
- Singular: To ensure Google can receive referring URL click identifiers from Singular for attribution, include the fields below:
  - For Android app install, pass ‘openuri’ field to https://s2s.singular.net/api/v1/launch
  - For Android app engagement, pass 'install_ref' field to https://s2s.singular.net/api/v1/launch
  - For iOS app engagement, pass 'openuri' field to https://s2s.singular.net/api/v1/launch

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
- Recommended conversion window settings
- Reducing discrepancies
Airbridge
- Recommended conversion window settings
- Reducing discrepancies
AppsFlyer
- Recommended conversion window settings
- Reducing discrepancies
Branch
- Recommended conversion window settings
- Reducing discrepancies
Kochava
- Recommended conversion window settings
- Reducing discrepancies
Singular
- Recommended conversion window settings
- Reducing discrepancies
Tenjin
- Recommended conversion window settings
- Reducing discrepancies

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.

Was this helpful?

How can we improve it?