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:
- Created a Branch Dashboard.
- Enabled Universal Ads for your Branch account.
- Contact your Branch account manager or visit https://branch.io/pricing
- Implemented the Branch SDK into your mobile app (iOS | Android)
- Admin access to your Google Ads account.
After signing into your Google Ads Account, you can link Branch as a third-party app analytics provider.
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:
- Use cross-account conversion tracking and set up a link ID with your third-party app analytics provider in your manager account. After setting up the link ID and conversions at the MCC level, ensure that you have appropriately set the manager as the conversion account for each sub-account you will run app ads on under Accounts>Management in Google Ads.
- 다른 Google Ads 계정과 단일 링크 ID를 공유하십시오.
- 사용자가 공유하는 계정은 링크 ID의 "소유자"입니다. 링크 ID의 "소유자"만이 링크 ID를 다른 계정과 공유할 수 있습니다. 소유자의 초대를 수락한 임의의 계정은 공유 링크 ID와 연관된 앱에 대한 해당 제3자 앱 분석 제공자로부터 변환을 가져올 수 있습니다.
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.
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!
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.
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:
click to session start
click to install
click to conversion event
impression to session start
impression to install
impression to conversion event
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
first_openevent 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.
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.
Please consult with your app development team to set up deep linking for your Google App Campaigns.
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.
Engagement campaigns have the ability to deep link using the following:
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 information on post-install or open events 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.
Your app needs to be whitelisted from Google’s end so that Google can start appending
gbraid to links.
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.
Track events with the Branch SDk in order to attribute post-install events in Google's reporting.
첫째, 모든 Google Ads 계정을 연결할 필요는 없습니다. 하지만 모바일 앱에 대한 인앱 전환을 소유한 Google Ads 계정을 연결해야 합니다. 이것은 대부분 MCC 계정입니다.
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.
Updated 4 days ago