Set up Glispa

Glispa is an ad network integrated with Adjust. Our integration lets Glispa receive attribution and in-app event data through automated callbacks.

In this article, learn how to set up measurement with Glispa for your app. This includes activating the integration, creating a campaign link, and choosing what data Adjust can share with Glispa.

Before you begin

Requirements

iOS / Android / Windows / Unity / React Native / Flutter / Adobe Air / Cordova / Marmalade / Xamarin / Cocos2d-x / Titanium / Corona

Select Glispa and your app in Campaign Lab

  1. Under Campaign Lab, select Partners.
  2. Select New partner > Glispa. Select Next to move to the next screen.
  3. In the App selection screen, choose the app for which you want to create the link, and enable the integration to share data with Glispa.
  4. Select Next.

Enable data sharing

Enable data sharing to activate the integration with Glispa. To enable data sharing:

  1. Turn on Enabled

Once you enable data sharing with Glispa, Adjust automatically sends Glispa the following data, by default:

  • install
  • session
  • reattribution
  • event
  • rejectedInstall

Set your data sharing options

If you’re working with a multi-platform app with data sharing enabled for multiple platforms, you can:

  1. Separate data sharing options at the platform-level by selecting Use platform-specific settings.
  2. Set the same data sharing settings for multiple platforms by selecting Use global settings.

Now, under What will be shared by default?, review the activities that Adjust shares with Glispa by default.

  • install
  • session
  • reattribution
  • event
  • rejectedInstall

Send additional data

Choose the amount and type of data that you want to share with Glispa through callbacks. Glispa may use this information to optimize performance.

  1. Under What sources of data do you want to share?, choose the attribution source of the data you are sharing with Glispa:
  • Data from all attribution sources
  • Only data attributed to Glispa

In-app revenue (from in-app purchases)

Sharing in-app revenue lets Glispa receive revenue amounts along with your revenue event data. You need to map events that generate revenue to share this data.

Sessions

Adjust does not automatically send session callbacks due to the high volume of sessions. Sharing sessions means Glispa will receive your app’s session activity.

Map parameters

You usually need to map parameters to share custom data with Glispa.

Map events

Map events that you want to share to the values that Glispa can receive. Data for unmapped events is not shared with Glispa.

Under Map events, follow these steps to choose the in-app events you want to directly send to Glispa.

  1. Select Map event.
  2. In the Adjust event list, choose the Adjust event that you want to share with Glispa.
  3. In the Partner event list, choose or enter a custom event name that you want to map the Adjust event to. You might have to map an event to several values.
  4. Select Apply.

Now Glispa will receive in-app event data for each of your linked events.

Map parameters

Partner parameters (available in Adjust SDK version 4.0+) let Adjust collect custom data points from your app and send them to Glispa. This lets Glispa receive custom event details for each of your linked events.

Before adding new partner parameters to the Adjust SDK, make sure no pre-existing partner parameters already fit your requirements.

To share partner parameters to Glispa, follow these steps.

  1. Set up partner parameters within the Adjust SDK: iOS, Android
  2. Check the Parameters data sharing checkbox.
  3. Map your events.
Note:

If you set up partner parameters within the Adjust SDK without setting up parameter sharing in the dashboard, Adjust forwards the parameters as named in the Adjust SDK.

Configure your link and settings

You have the option to set your:

Create your link and share it with Glispa

In the Setup review screen, you can review your choices. You can also go back and make changes to:

  • Your selected app
  • Data sharing options
  • Link structure parameters
  • User destinations
  • Attribution settings

Select Create link to create your click URL, impression URL, QR code and link token. Creating a link also enables data sharing and the integration with Glispa.

Once you’ve created your link, share it with Glispa for placement in campaigns.

List of all parameters forwarded to Glispa

Glispa requires Adjust to send the following parameters (data points) with your callbacks:

PlaceholderInformation
{adid}Adjust device ID (all platforms)
{adwords_matchtype}Google AdWords search keyword and match type
{android_id}Android ID (Android only)
{city}Device city
{country}Device two-character country code
{currency}Original ISO 4217 currency code sent from Adjust SDK
{device_name}Device model number
{gps_adid}Google Play Store advertising ID
{idfa}ID for advertisers (iOS only)
{ip_address}Device IP address
{isp}Device internet service provider
{language}Device two-character language code
{os_name}Device operating system
{os_version}Operating system version number
{partner_parameters}Custom partner parameters collected by the Adjust SDK or S2S request and transmitted to third party providers via postbacks
{revenue_float}Revenue, as sent from Adjust SDK, in whole currency units
{sdk_version}Adjust SDK version (per app)
{timezone}Device time zone
{tracking_limited}1 if tracking is limited, 0 if not
{user_agent}Incoming raw user agent
{activity_kind}Type of user activity
{app_id}Store App ID or Google Play Store
{app_name}Name of the app
{app_version_raw}App version number (Android), build-version-number for the bundle (iOS)
{connection_type}Internet connection type
{install_begin_time}App download began timestamp (Android and Google Play Store only)
{install_finish_time}App download completion timestamp
{installed_at}Install (i.e., first app open) timestamp
{is_organic}1 if organic traffic, 0 if non-organic
{referral_time}User landed on app Play Store page timestamp (Android and Google Play Store only)
{rejection_reason}Reason for a rejected attribution