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 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.

Important: Please ensure that consent status for EEA users is captured before sending app conversions to your third-party AAP. In the scenario a conversion is passed and user-level consent has not been granted, Google Ads may use the gbraid for non-user level app conversion measurement.

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

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

Adjust:

  1. Integrate the Adjust SDK.
  2. 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.
  3. Activate Integrated Conversion Measurement in the Adjust user interfaceI by ensuring that “Probabilistic Modeling” (disabled by default), and the Attribution Window for Probabilistic Modeling is set to 24 hours (6 hours by default).
  4. Provide consent status for EEA users by following these Android and iOS compliance guides and ensure "addGranularOption" for third-party sharing is enabled. 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:

  1. Integrate the Airbridge SDK.
  2. 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.
  3. Activate Integrated Conversion Measurement in the Airbridge user interface by ensuring the Lookback Window for Probabilistic Modeling Matching is set to 24 hours or longer (24 hours by default) for Google Ads.
  4. Provide consent status for EEA users by following these Android and iOS compliance guides. 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.
    • Note: All Airbridge SDK versions are compliant.

AppsFlyer:

  1. Integrate the AppsFlyer SDK.
  2. 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.
  3. Activate Integrated Conversion Measurement in the AppsFlyer user interface by ensuring that “Advanced Data Sharing” is enabled (disabled by default) for Google Ads.
  4. Provide consent status for EEA users by following these Android and iOS compliance guides. 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:

  1. Integrate the Branch SDK.
  2. Follow these Android and iOSdeeplink guides to ensure that Google can receive referring URL click identifiers from Branch for attribution.
  3. Activate Integrated Conversion Measurement in the Branch UI by ensuring that the “Integrated Conversion Measurement” setting is enabled for (enabled by default), and Attribution Windows for Click To Install is set to 24 hours or longer (7 day default) for Google Ads.
  4. Provide consent status for EEA users by following these Android and iOS compliance guides. 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:

  1. Integrate the Kochava SDK.
  2. 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.
  3. Activate ICM in the Kochava user interface by ensuring Privacy Profiles and Modeled Attribution are enabled (enabled by default for Android, disabled by default for iOS), and the Click Reconciliation for Modeled Lookback is set to 24 hours or longer (7 day default for Android, disabled by default for iOS) for Google Ads.
  4. Provide consent status for EEA users by following this SDK compliance guide. 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:

  1. Integrate the Singular SDK.
  2. Follow these Android and iOS deeplink guides to ensure that Google can receive referring URL click identifiers from Singular for attribution.
  3. Activate Integrated Conversion Measurement in the Singular user interface by ensuring that “Integrated Conversion Measurement” is enabled (enabled by default), and the Attribution Lookback Window for Probabilistic Attribution is set to 24 hours (24 hours by default) for Google Ads.
  4. 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. Contact your Singular CSM for guidance.
    • Note: All Singular SDK versions are compliant.

Tenjin:

  1. Integrate the Tenjin SDK.
  2. Follow this deeplink guide to ensure Google can receive referring URL click identifiers from Tenjin for attribution.
    • Note: All Tenjin SDK versions are compatible.
  3. Activate Integrated Conversion Measurement in the Tenjin UI by ensuring that “Probabilistic Matching” is enabled (enabled by default), and the Attribution Window for Probabilistic Matching is set to 24 hours (1 hour by default) for Google Ads.
  4. Provide consent status for EEA users by following these Android and iOS compliance guides. 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.
    • Note: The Tenjin Android SDK v1.15.0+ and iOS SDK 1.14.0+ are required for compliance.

Collect app conversion events and user consent 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 and optimization. To configure third-party server-to-server events:

Adjust:

  1. Integrate the Adjust S2S API.
  2. 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.
  3. Activate Integrated Conversion Measurement in the Adjust user interface by ensuring “Probabilistic Modeling” (disabled by default), and the Attribution Window for Probabilistic Modeling is set to 24 hours (6 hours by default) for Google Ads.
  4. Provide consent status for EEA users by following this compliance guide.

Airbridge:

  1. Integrate the Airbridge S2S API.
  2. Contact your Airbridge CSM for guidance to ensure Google can receive referring URL click identifiers from Airbridge for attribution.
  3. Activate Integrated Conversion Measurement in the Airbridge UI by ensuring the Lookback Window for Probabilistic Modeling Matching is set to 24 hours or longer (24 hours by default) for Google Ads.
  4. Provide consent status for EEA users by following this compliance guide.

AppsFlyer:

  1. Integrate the AppsFlyer S2S API.
  2. Contact your AppsFlyer CSM for guidance to ensure Google can receive referring URL click identifiers from AppsFlyer for attribution.
  3. Activate Integrated Conversion Measurement in the AppsFlyer user interface by ensuring that “Advanced Data Sharing” is enabled (disabled by default) for Google Ads.
  4. Provide consent status for EEA users by following this compliance guide.

Branch:

  1. Integrate the Branch S2S API.
  2. Include the fields below to ensure Google can receive referring URL click identifiers from Branch for attribution:
  3. Activate Integrated Conversion Measurement in the Branch user interface by ensuring that the “Integrated Conversion Measurement” setting is enabled for (enabled by default), and Attribution Windows for Click To Install is set to 24 hours or longer (7 day default) for Google Ads.
  4. Provide consent status for EEA users by following this compliance guide.

Kochava:

  1. Integrate the Kochava S2S API.
  2. Include the fields below to ensure Google can receive referring URL click identifiers from Kochava for attribution:
  3. Activate Integrated Conversion Measurement in the Kochava user interface by ensuring Privacy Profiles and Modeled Attribution are enabled (enabled by default for Android, disabled by default for iOS), and the Click Reconciliation for Modeled Lookback is set to 24 hours or longer (7 day default for Android, disabled by default for iOS) for Google Ads.
  4. Provide consent status for EEA users by following these Install and Post-Install Event compliance guides.

Singular:

  1. Integrate the Singular S2S API.
  2. Include the fields below to ensure Google can receive referring URL click identifiers from Singular for attribution:
  3. Activate Integrated Conversion Measurement in the Singular user interface by ensuring that “Integrated Conversion Measurement” is enabled (enabled by default), and the Attribution Lookback Window for Probabilistic Attribution is set to 24 hours (24 hours by default) for Google Ads.
  4. Provide consent status for EEA users by following this compliance guide.

Tenjin:

  1. Integrate the Tenjin S2S API (available for paid clients by request).
  2. Contact your Tenjin CSM for guidance to ensure Google can receive referring URL click identifiers from Tenjin for attribution.
  3. Activate Integrated Conversion Measurement in the Tenjin user interface by ensuring that “Probabilistic Matching” is enabled (enabled by default), and the Attribution Window for Probabilistic Matching is set to 24 hours (1 hour by default) for Google Ads.
  4. Contact your Tenjin CSM for guidance to provide consent status for EEA users.

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:

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.

Related links

Was this helpful?

How can we improve it?

Need more help?

Try these next steps:

Post to the help community Get answers from community members
Contact us Tell us more and we’ll help you get there
true
Achieve your advertising goals today!

Attend our Performance Max Masterclass, a livestream workshop session bringing together industry and Google ads PMax experts.

Register now

Search
Clear search
Close search
Main menu
4608205395174456053
true
Search Help Center
true
true
true
true
true
73067
false
false
false
true
false