Enable Glispa (New)

Overview

Glispa is a mobile ad network that provides user acquisition and retargeting campaigns across iOS and Android. Connect Glispa 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 Glispa in the new Branch experience. For information on Glispa in legacy Branch, visit our legacy guide.

Partner capabilities

Before you begin

To set up the Glispa 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 Glispa account with admin access.

Enable Glispa

To begin, navigate to Configuration > Ad Partners > Glispa.

Branch enables Glispa's basic setup 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 Glispa.

Configure attribution

By default, Glispa uses your global app attribution settings. To set attribution windows specific to Glispa, 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 Glispa automatically activates postbacks for INSTALL. The default postback URL template is:

http://trk.glispa.com/event/00000000-0000-0000-0000-000000000E00/${ (last_attributed_touch_data.~click_id)! }?event_id=${ (name)! }&event_oid=${ (timestamp/1000)?long }&m.device_ip=${ (user_data.ip)! }&m.idfa=${ (user_data.idfa)! }&m.gaid=${ (user_data.aaid)! }&country=${ (user_data.geo_country_code)! }&os=${ (user_data.os)! }&os_version=${ (user_data.os_version)! }&m.app_id=${ (app.name)! }&m.app_version=${ (user_data.app_version)! }&m.locale=${ (user_data.language)! }&event_timestamp=${ (timestamp/1000)?long }&revenue_amount=${ (event_data.revenue)! }&revenue_currency=${ (event_data.currency)! }&mmp=BranchIO&city=${(user_data.geo_city_en)!}&match_type==${(last_attributed_touch_data.+via_features)!}

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 Glispa campaigns. Branch uses the link to attribute clicks and impressions 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 Glispa:

• 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 = Glispa.

• In Glispa: confirm that forwarded events are appearing in your Glispa attribution reporting.

Data mappings

Campaign data

Branch populates the following fields from Glispa campaign data.