Overview
Admobs is a mobile advertising partner that runs acquisition and retargeting campaigns across mobile apps. Connect Admobs to Branch to attribute clicks and installs, forward conversion events via postbacks, and deep link users into your app.
For more information about integrating ad partners in general, visit our Ad Partner Integration Guide.
Note: this guide is for new Branch
Please note that this guide is about integrating Admobs in the new Branch experience. For information on Admobs in legacy Branch, visit our legacy guide.
Partner capabilities
Capability | Details |
|---|---|
Company type | Non-SAN ad network, DSP |
Deep linking | Supported |
Attribution | Click-through attribution |
Ad campaign types | Acquisition campaigns, Retargeting campaigns |
Ad formats | Mobile and web display ads, Video ads, Native contextual ads |
Click types | Client-side click |
Supported platforms | Android, iOS, Mobile web, Desktop web |
Link wrapping | Supported |
Cost ingestion support | Supported |
Cost ingestion types | API |
Pricing models | CPI, CPC, CPA |
Before you begin
To set up the Admobs integration, you need:
Branch's Performance product enabled for your Branch account. Contact your Branch account manager or visit https://branch.io/pricing.
A Branch account with access to Configuration > Ad Partners and admin permissions to enable and configure integrations.
The Branch SDK implemented in your app (iOS | Android) with event tracking configured.
An Admobs account with admin access.
Enable Admobs
To begin, navigate to Configuration > Ad Partners > Admobs.
Branch enables Admobs automatically. On the Status tab, the Ad Linking, Attribution, and Postbacks cards show Enabled.
(Recommended) To configure the optional PAM for Publishers privacy setting, select Partner settings to open the Manage account dialog and enable the toggle. When enabled, PAM for Publishers removes advertiser-specific user identifiers from postbacks for users who haven't opted in via Apple's App Tracking Transparency (ATT) framework, prioritizing identifiers provided directly by Admobs.
Configure attribution
By default, Admobs uses your global app attribution settings. To set attribution windows specific to Admobs, enable the Override global app settings toggle on the Attribution windows tab.
For more information, follow Configure attribution in the general Ad Partner Integration Guide.
Configure postbacks
When you enable Admobs, Branch activates a default postback for the INSTALL event. The default postback URL template is:
https://admobs57.trackier.co/acquisition?click_id=${ (last_attributed_touch_data.~click_id)! }&security_token=34d9059f6cec5ef526f2&idfa=${ (user_data.idfa)! }&gaid=${ (user_data.aaid)! }&goal_value=${ (name)! }Note: Admobs GOAL ID required
Admobs requires a GOAL ID that corresponds to each postback. Enter the GOAL ID for each event when you configure its postback, then select Save. Contact your Admobs account manager to obtain your GOAL IDs.
To add postbacks for additional events or to customize postback behavior, follow Configure postbacks in the general Ad Partner Integration Guide.
Create a Branch Ad Link
Create a Branch Ad Link to use in your Admobs campaigns. Branch uses the link to attribute clicks and installs and deep link users into your app. Follow Create a Branch Ad Link in the general Ad Partner Integration Guide.
Verify your data
After your integration is connected and events are flowing, you can verify data is reaching Branch and Admobs:
In Branch Liveview: confirm that events from your app appear in real time. This is the fastest way to confirm SDK events are firing.
In Branch Analysis dashboards: review attributed installs and events where
Ad Partner Name = Admobs.In Admobs: confirm that forwarded events are appearing in your Admobs attribution reporting.
Data mappings
Campaign data
Branch populates the following fields from Admobs campaign data.
Branch field | Partner data |
|---|---|
|
|
|
|