Enable Singletap (New)
Overview
SingleTap by Digital Turbine is an app delivery and advertising technology that lets users install and engage with apps directly from an ad, without leaving their current context. Connect SingleTap by Digital Turbine 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 SingleTap by Digital Turbine in the new Branch experience. For information on SingleTap by Digital Turbine in legacy Branch, visit our legacy guide.
Partner capabilities
Capability | Details |
|---|---|
Company type | Non-SAN ad network |
Deep linking | Supported |
Attribution | Click-through attribution |
Ad campaign types | User acquisition, app discovery |
Ad formats | Video Ads Playable Ads, Banner and Display Ads, Offerwalls |
Click types | Client-side click |
Supported platforms | iOS, Android |
Link wrapping | Contact SingleTap by Digital Turbine for details |
Cost ingestion support | Not supported |
Pricing models | CPI (cost per install), CPEI (cost per engaged install) |
Before you begin
To set up the SingleTap by Digital Turbine 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.
A SingleTap by Digital Turbine account with admin access, and a Buyer ID provided by your Digital Turbine account manager.
Enable SingleTap by Digital Turbine
To begin, navigate to Configuration > Ad Partners > SingleTap by Digital Turbine.
Branch enables SingleTap by Digital Turbine's basic setup automatically. On the Status tab, the Ad Linking and Attribution cards show Enabled. The Postbacks card shows Needs Setup until you add your Buyer ID (see below).
To add your Buyer ID, select Partner settings to open the Manage account dialog. Under Postback Credentials, enter the Buyer ID provided by your Digital Turbine account manager, then select Save. These credentials are automatically added to your postbacks.
(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 SingleTap by Digital Turbine.
Configure attribution
By default, SingleTap by Digital Turbine uses your global app attribution settings. To set attribution windows specific to SingleTap by Digital Turbine, 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
Enabling SingleTap by Digital Turbine automatically activates postbacks for INSTALL and PURCHASE. The default postback URL template is:
http://br.tpbid.com/postback?bid_id=${ (last_attributed_touch_data.~click_id)! }&ios_ifa=${ (user_data.idfa)! }&android_ifa=${ (user_data.aaid)! }&ios_ifv=${ (user_data.idfv)! }&android_id=${ (user_data.android_id)! }&bundle=<@loop data=app.app_bundles val="bundle"><#if user_data.os == bundle.os><#if bundle.os=="ANDROID">${(bundle.android.package_name)!}<#elseif bundle.os == "IOS">${(bundle.ios.itunes_id?substring(2))!}</#if><@break/></#if></@loop>&evt_at=${ (timestamp/1000)?long }&device=<#if (user_data.os)! == "IOS" && (user_data.idfa)! != "">${(user_data.idfa)!}<#elseif (user_data.os)! == "IOS">${(user_data.idfv)!}<#elseif (user_data.os)! == "ANDROID">${(user_data.aaid)!}</#if>&os=${ (user_data.os)! }&osv=${ (user_data.os_version)! }&ip=${ (user_data.ip)! }&country=${ (user_data.geo_country_code)! }&lang=${ (user_data.language)! }&ua=${ (user_data.user_agent)! }&cid=${ (last_attributed_touch_data.~campaign)! }&crid=${ (last_attributed_touch_data.~creative_name)! }&evt_name=${ (name)! }&costo=${ (event_data.revenue)! }&cur=${ (event_data.currency)! }&is_attributed=<#if (last_attributed_touch_data.$3p)! == (ad_network.machine_name)!>1<#else>0</#if>&yid=${ (ad_network.credentials.buyer_id)! }&label=${ (last_attributed_touch_data.label)! }&tsys=brTo 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 SingleTap by Digital Turbine 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.
To make your Branch Ad Link compatible with SingleTap, retrieve your base SingleTap link from your Digital Turbine account manager, then append &dvURL= followed by your URL-encoded Branch link to the end of the SingleTap URL.
For advanced setup, including using Branch Journeys with SingleTap, see the SingleTap developer documentation.
Verify your data
After your integration is connected and events are flowing, you can verify data is reaching Branch and SingleTap by Digital Turbine:
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 = SingleTap by Digital Turbine.In SingleTap by Digital Turbine: confirm that forwarded events are appearing in your SingleTap by Digital Turbine attribution reporting.
Data mappings
Campaign data
Branch populates the following fields from SingleTap by Digital Turbine campaign data.
Branch field | Partner data |
|---|---|
|
|
|
|