Overview
Jampp is a demand-side platform (DSP) that uses contextual and behavioral signals to run programmatic user acquisition and retargeting campaigns for on-demand apps. Connect Jampp to Branch to attribute clicks and installs, forward conversion events via postbacks, deep link users into your app, and import cost data.
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 Jampp in the new Branch experience. For information on Jampp in legacy Branch, visit our legacy guide.
Partner capabilities
Capability | Details |
|---|---|
Company type | DSP |
Deep linking | Supported |
Attribution | Click-through attribution, View-through attribution |
Ad campaign types | Acquisition campaigns, Retargeting campaigns |
Ad formats | Banners, Interstitials, Video, Native, CTV to mobile, Countdowns and tutorials |
Click types | Client-side click |
Supported platforms | iOS, Android |
Link wrapping | Supported |
Cost ingestion support | Supported (API) |
Cost time zone | GMT |
Pricing models | CPM |
Before you begin
To set up the Jampp 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 Jampp account with admin access and campaigns running through Jampp.
Enable Jampp
To begin, navigate to Configuration > Ad Partners > Jampp.
Branch enables Jampp's basic setup automatically. On the Status tab, the Ad Linking, Attribution, and Postbacks cards show Enabled. The Clicks and Impressions and Cost Data cards show Needs Setup until those features are configured (see Create a Branch Ad Link and Import cost data).
(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 Jampp.
Configure attribution
By default, Jampp uses your global app attribution settings. To set attribution windows specific to Jampp, 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 Jampp automatically activates postbacks for INSTALL, OPEN, and PURCHASE. The default postback URL template is:
http://tracking.jampp.com/event?kind=${ (name)! }&rnd=${ (timestamp/1000)?long }&value=${ (event_data.revenue)! }&pubid=${ (last_attributed_touch_data.~click_id)! }&app=<@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>&session_user_agent=${ (user_data.user_agent)! }&ip_address=${ (user_data.ip)! }&device_model=${ (user_data.model)! }&device_os_version=${ (user_data.os_version)! }&apple_ifa=${ (user_data.idfa)! }&apple_ifa_sha1=<@sha1>${ (user_data.idfa )! }</@sha1>?&google_advertising_id=${ (user_data.aaid)! }&google_advertising_id_sha1=<@sha1>${ (user_data.aaid )! }</@sha1>&google_advertising_id_md5=<@md5>${ (user_data.aaid )! }</@md5>&device_countrycode=${ (user_data.geo_country_code)! }&device_language=${ (user_data.language)! }&platform=${ (user_data.os)! }&vta=<#if last_attributed_touch_type == "CLICK">0<#elseif last_attributed_touch_type == "IMPRESSION">1</#if>&click_id=${ (last_attributed_touch_data.~click_id)! }&ad=${ (last_attributed_touch_data.~creative_id)! }&grp=${ (last_attributed_touch_data.group)! }To add postbacks for additional events or to customize postback behavior, follow Configure postbacks in the general Ad Partner Integration Guide.
Import cost data
Jampp cost ingestion uses API authentication with a Client ID and Client Secret. Contact your Jampp account manager if you need help locating these credentials.
In Branch, select Partner settings to open the Manage account dialog. Under Cost Data Credentials, enter your Client ID and Client Secret, then select Save.
Create a Branch Ad Link
Create a Branch Ad Link to use in your Jampp campaigns. Branch uses the link to attribute clicks and impressions and deep link users into your app. Placing the Branch Ad Link in your Jampp campaign will resolve the Clicks and Impressions: Needs Setup status on the Status tab.
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 Jampp:
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 = Jampp. Cost data appears in cost-reporting views once ingestion is active. Allow up to 24 hours after setup for the first cost data to be pulled in.In Jampp: confirm that forwarded events are appearing in your Jampp attribution reporting.
Data mappings
Campaign data
Branch populates the following fields from Jampp campaign data.
Branch field | Partner data |
|---|---|
|
|
|
|