Jampp is a performance marketing platform for acquiring and retargeting mobile customers. It combines behavioral data with predictive and programmatic technology to generate revenue for advertisers by showing personal, relevant ads that inspire consumers to purchase for the first time, or more often.

Braze customers can integrate with Jampp by configuring the Braze webhook channel to stream events into Jampp. As a result, customers can add richer data sets to their retargeting initiatives with Jampp within the mobile advertising ecosystem.

Retargeting Cases

Some examples of when you would want to retarget customers with an ad:

  • When a customer’s email or push subscription state changes.
  • How a customer interacted with a Braze messaging campaign.
  • If the customer has triggered a specific geofence.

One of the best ways to accomplish this is to use Braze as well as a retargeting partner specialized in mobile, such as Jampp. You want the retargeting partner to receive automated user info from Braze using webhooks. You’ll be able to leverage Braze’s targeting and triggering abilities to send events to Jampp, which could then be used to define retargeting campaign definitions in Jampp.

Prerequisites for Integration

This integration supports iOS and Android apps.

Requirement Source Description
Android App ID Braze Your unique application identifier for Android (i.e. “com.example”).
iOS App ID Braze Your unique application identifier for iOS (i.e. “012345678”).
Enable IDFA Collection in Braze SDK Braze IDFA Collection is optional within the Braze SDK and disabled by default.
Collection of Google Advertising ID via custom attribute Google Google Advertising ID collection is optional for customers and can be collected as a custom attribute.


Step 1: Create a Webhook Template in Braze

You can create this from the Templates & Media section, or create a new webhook campaign in Braze.


Step 2: Fill Out Your Template

For this webhook, all data is passed on alongside the HTTP URL as query string parameters. The following parameters that need to be defined:

  • You’ll need to set the event name. This is to define the name of the event that will appear in your Jampp dashboard.
  • Jampp requires you to pass along your app’s unique application identifier for Android (i.e. “com.example”) and iOS (i.e. “012345678”).
  • You’ll also need to insert Liquid for the appropriate custom attribute you’re tracking the Google Advertising ID.

Below is an example of what your Webhook URL might look like:

{% assign event_name = 'your_jampp_event_name' %}
{% assign android_app_id = 'your_android_app_id' %}
{% assign iOS_app_id = 'your_iOS_app_id' %}

{% capture json %}{'name':'{{event_name}}','active':true,'joined':{{'now' | date: '%s' }}}{% endcapture %}

http://tracking.jampp.com/event?kind={{event_name}}&rnd={{rnd}}&app={% if {{most_recently_used_device.${idfa}}} == blank %}{{android_app_id}}{% else %}{{iOS_app_id}}{% endif %}&apple_ifa={{most_recently_used_device.${idfa}}}&google_advertising_id={{custom_attribute.${aaid}}}&user_agent={user-agent}&prtnr=braze

{% if {{most_recently_used_device.${idfa}}} == blank and {{custom_attribute.${aaid}}} == blank %}
{% abort_message('No IDFA or AAID available') %}
{% endif %}

Elements (from sample above) to modify before sending the campaign:

  1. {% assign event_name = 'your_jampp_event_name' %}
  2. {% assign android_app_id = 'your_android_app_id' %}
  3. {% assign iOS_app_id = 'your_iOS_app_id' %}
  4. &google_advertising_id={{custom_attribute.${aaid}}

Please note that in this example the Google Advertising ID is listed as aaid but you will need to replace it with the custom attribute name your developers set.

After defining the parameters above, insert this Liquid code template into the Webhook URL field and edit as needed. You do not have to define a Request Body for this webhook. Here is the template in Braze:

Webhook Template Jampp

Request Headers and Method

The Content-Type should be pre-populated as a key-value pair within the webhook template.

Jampp Method

Step 3: Preview Your Request

To ensure the request is rendering properly for different users, use the Message Preview. A good approach is to preview the Webhook for both Android as well as iOS users. You can also send test requests for these users. If the request was successful the API responds with HTTP 204.

New Stuff!