Search specific term/phrase surrounded by double quotes. e.g. “deep linking”
Exclude records that contain a specific term prefixed with a minus. e.g. Android -Firebase

Enable Google App Campaigns

Integrate Branch in your Google App campaigns to enable robust attribution and deep linking.


By connecting Branch and Google Ads, the following is enabled:

  • App conversion data collected by the Branch SDK is sent to Google Ads for attribution.
  • Read-only access to import click and impression data at the aggregate level from Google Ads into your Branch account.
  • Viewing Google Ads metrics in your Branch Dashboard (your manager (MCC) and children accounts).
  • Deep link into in-app experiences (campaign specific)


In order to enable Google Ads, you need to have completed the following:

  1. Created a Branch Dashboard.
  2. Enabled Universal Ads for your Branch account.
  3. Implemented the Branch SDK into your mobile app (iOS | Android)
  4. Admin access to your Google Ads account.

Enable App Campaigns

1. Link Branch in Google Ads

After signing into your Google Ads account, click on Tools in the sidebar, then click on the Data manager tab.

Then, scroll down to Popular products, and select Third-party app analytics.

Click on Create link ID.

Choose Branch, in the App analytics provider dropdown to link Branch to Google Ads.

You are allowed to link multiple accounts as long as the user connecting has access to all of the accounts you wish to connect. For each app you want to track with Branch, you'll need to create a different link ID.

If you manage campaigns for the same app in multiple Google Ads account, you must do one of the following three options:

  • Use cross-account conversion tracking and set up a link ID with your third-party app analytics provider in your manager account. Once you link at the MCC level, there is one additional step to "share down" the ability for the sub-accounts to utilize these Conversion Events:
    • Navigate to MCCSettingsSub-account SettingsGoogle Ads Conversion account. For those accounts you wish to share conversions from the MCC, the “Google Ads Conversion account” column should be edited to "This Manager."
  • Or, share a single link ID with another Google Ads account.
  • Or, the account you share from will be the “owner” of the link ID. Only the “owner” of the link ID can share their link ID with other accounts. Any account that has accepted the owner's invite will be able to import conversions from the corresponding third-party app analytics provider for the app associated with the shared link ID.

Once you create the link IDs, copy them, as you'll need them for the next step.


Link ID Validation

Branch validates the link ID generated from Google in order to avoid any human error.

2. Connect Google Ads in Branch

In the Branch Dashboard under Ads > Partner Management, find/search for Google AdWords. If you're already logged into the Branch Dashboard, you can also click here to go there directly.

Click the Sign in with Google button to authenticate with your Google Ads account.

After selecting the Adwords accounts to connect with Branch, paste the link IDs from Step 1.

After inputting your link IDs, Google Ads should be connected to Branch!

3. Configure Events

After authenticating your Google Ads account to Branch, navigate to the Events Config tab to configure your events.

It's important to add your event mappings here for Branch to properly send event metadata to Google Ads for attribution. You should see the events you are tracking with the Branch SDK here when you Add Event Mappings. For more details on Google Ads and Branch event & metadata mapping, see the specifications here.

4. Configure Attribution Windows

After configuring your events, navigate to the Attribution Windows tab to set windows by attribution type.

You have full freedom to choose your attribution windows; however, it may cause discrepancies between the Branch and Google Dashboards when comparing.

Google's Recommended Attribution Windows:

Attribution TypeWindow
click to session start60 days
click to install30 days
click to conversion event90 days
impression to session start1 day
impression to install1 day
impression to conversion event1 day

5. Import Events in Google's Dashboard

After setting up events and the attribution windows in Branch, you will need to import app conversion data to Google Ads.

If you do not see conversion data to import in Google Ads, allow ~20 minutes for it to appear. You can expedite this process if you open your app and simulate the events you want to be forwarded to Google Ads.


Account-Default Conversion Goals

For any first_open event conversions, please ensure that you enable the "account default" setting for a conversion goal so that primary conversion actions within that goal can be tracked as conversions in your reporting.

For more information, please refer to Google's About the "Include in 'Conversions'" setting.

6. Launch Google Ads App Campaigns

In Google Ads, after you've created and optimized your App Install/Engagement campaign, you can create your ad group(s), which dynamically creates formats for various formats. Here is where you can set additional campaign configurations.

You must create separate campaigns for iOS and Android:

Once you finish, review the information and launch your campaign!

Note: If your campaigns are agency-managed, please see additional steps here.

Deep Linking from Google App Campaigns

Please consult with your app development team to set up deep linking for your Google App Campaigns.

App Install Campaign Deep Linking

The only type of deep linking supported by UAC is Branch's SAN Deferred Deep Linking feature. Please follow our guide here on how to set it up.

App Engagement Campaign Deep Linking

Engagement campaigns have the ability to deep link using the following:

Google Ads Conversion Reporting

Branch supports Google Ads conversion reporting for users that opt-out of ATT on the iOS14.5+ devices for Google Adwords campaigns. Branch sends Google Ads gbraid, an aggregated campaign identifier on app re-engagement from deep links and tracker URLs. To support Google Ads conversion reporting, the Branch SDK will store gbraid to associate it with events for a given 30-day window.

Enabling Google Ads Conversion Reporting

1. Update your iOS app

Be sure to update your iOS app with the latest version of the Branch iOS SDK to support gbraid handling to share the aggregated identifier with Google on post-install or open events when a user is opted out of ATT on the iOS 14.5+ devices.

2. Track Events

Track events with the Branch SDk in order to attribute post-install events in Google's reporting.

To learn more about Google Ads campaign identifiers, click here.


How do I handle multiple Google Ad accounts?

Firstly, it is not necessary to connect all Google Ads accounts. However, you must connect the Google Ads account that owns in-app conversions for your mobile app. Often, this is the MCC account.


MCC Accounts

Inside an MCC, it is possible to configure which account (the MCC or the child account) is responsible for conversions. Ensure that you create link IDs with the account that is noted as the Conversion Account under the MCC > Management tab.

Note: Do not authenticate a single ad account to multiple Branch apps (ex. Live and Test apps) as that will cause issues with authentication and Dashboard reports.

If you only have access to the child account (but that account is attached to an MCC), you can see which account is recording conversions within the child account as well, by going to Tools > Conversions > Settings > Conversion Account in Google Ads.