Set up Liftoff
Liftoff is an ad network integrated with Adjust. Our integration lets Liftoff receive attribution and in-app event data through automated callbacks.
In this article, learn how to set up measurement with Liftoff for your app. This includes activating the integration, creating a campaign link, and choosing what data Adjust can share with Liftoff.
Before you begin
Requirements
- Admin, Editor, or Custom Editor permissions in Adjust.
- Adjust SDK v4.0.0 and later to map SDK parameters to Liftoff parameters. Follow the guides linked below to use this feature.
iOS | Android | Windows | Unity | React Native | Flutter | Adobe Air | Cordova | Marmalade | Xamarin | Cocos2d-x | Titanium | Corona
Select Liftoff and your app in Campaign Lab
- Under Campaign Lab, select Partners.
- Select New partner > Liftoff. Select Next to move to the next screen.
- In the App selection screen, choose the app for which you want to create the link, and enable the integration to share data with Liftoff.
- Select Next.
Enable data sharing
Enable data sharing to activate the integration with Liftoff. To enable data sharing:
- Turn on Enabled
Once you enable data sharing with Liftoff, Adjust automatically sends Liftoff the following data, by default:
- install
- session
- uninstall
- reinstall
- reattributionReinstall
- reattribution
- event
- rejectedInstall
- rejectedReattribution
- ad revenue
Set your data sharing options
If you’re working with a multi-platform app with data sharing enabled for multiple platforms, you can:
- Separate data sharing options at the platform-level by selecting Use platform-specific settings.
- 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 Liftoff by default.
- install
- session
- uninstall
- reinstall
- reattributionReinstall
- reattribution
- event
- rejectedInstall
- rejectedReattribution
- ad revenue
Send additional data
Choose the amount and type of data that you want to share with Liftoff through callbacks. Liftoff may use this information to optimize performance.
- Under What sources of data do you want to share?, choose the attribution source of the data you are sharing with Liftoff:
- Data from all attribution sources
- Only data attributed to Liftoff
Ad revenue (from ad views)
Ad revenue sharing lets Liftoff receive user ad revenue data. This lets Liftoff use ad revenue data to optimize your user targeting and campaigns.
This feature is available with Adjust’s Ad Revenue package. To purchase our Ad Revenue package, contact your sales representative.
To share ad revenue to Liftoff, select one or more Ad Revenue Sources.
- If you leave this field empty, we send ad revenue data from all integrated mediation sources.
Sessions
Adjust does not automatically send session callbacks due to the high volume of sessions. Sharing sessions means Liftoff will receive your app’s session activity.
Uninstalls or reinstalls
Sharing uninstalls or reinstalls lets Liftoff receive your app’s uninstall and/or reinstall data measured by Adjust.
For iOS apps, you might expect a low record of uninstalls and/or reinstalls. For more information, visit Uninstall and reinstall measurement.
In-app revenue (from in-app purchases)
Sharing in-app revenue lets Liftoff receive revenue amounts along with your revenue event data. You need to map events that generate revenue to share this data.
Map events
Map events that you want to share to the values that Liftoff can receive. Data for unmapped events is not shared with Liftoff.
Map individual events
If you have a multi-platform app, you can choose to share different events per platform with Liftoff. This lets you:
- Set individual events to manage campaign strategies for each platform.
- Customize data sharing per platform.
Under Map events, follow these steps to choose the in-app events you want to directly send to Liftoff.
- Select Map event.
- In the Adjust event list, choose the Adjust event that you want to share with Liftoff.
- Under Partner event, you need to select the Liftoff event that corresponds to the Adjust event.
- For single platform apps and multi-platform apps with data sharing enabled for a single platform only, you map events for that platform only. For multi-platform apps with data sharing enabled for multiple platforms, you can:
- Select Use platform-specific mapping to map separate events at the platform-level or to not map events for certain platforms.
- Select Use global mapping to map the same events for all platforms.
- In the Partner event list, choose or enter a custom event name, that you want to map the Adjust event to.
- For single platform apps and multi-platform apps with data sharing enabled for a single platform only, you map events for that platform only. For multi-platform apps with data sharing enabled for multiple platforms, you can:
- Select Apply.
Now Liftoff will receive in-app event data for each of your linked events.
Map all events
If Liftoff supports mapping all events automatically, under Map events, select Map all events. This saves time in mapping individual events.
Now Liftoff will receive in-app event data for all your linked events.
Map parameters
You usually need to map parameters to share custom data with Liftoff.
Partner parameters (available in Adjust SDK version 4.0+) let Adjust collect custom data points from your app and send them to Liftoff. This lets Liftoff 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 Liftoff, follow these steps.
- Set up partner parameters within the Adjust SDK.
- Check Before you begin for all SDK development platform links.
- Under Set your data sharing options, select Parameters.
- Under Map parameters, you can specify how you want to send partner parameters defined in the SDK to the network:
- Select Map parameter.
- In the SDK parameter field, enter the name of the SDK parameter you want to share with the network.
- In the Partner parameter field, enter the network parameter that corresponds to the SDK parameter.
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 Liftoff
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 Liftoff.
Once you’ve created your link, share it with Liftoff for placement in campaigns.
Partner specific setup instructions
Liftoff allows you to send a set of predefined parameters. If you attach any of these parameters to an event in your adjust SDK, these will be forwarded to Liftoff. You can find out more about attaching partner parameters in the SDK readme specific to the SDK or SDKs you are working with. Below is a list of the defined parameters that Liftoff accepts:
Parameter key > Value
- product_id > product or content identifier, relevant for product feed retargeting
- product_type > product type or category
- revenue > item price
- currency_code > currency of item price
List of all parameters forwarded to Liftoff
Liftoff requires Adjust to send the following parameters (data points) with your callbacks:
Placeholder | Information |
{adid} | Adjust device ID (all platforms) |
{android_id} | Android ID (Android only) |
{city} | Device city |
{click_attribution_window} | Attribution window settings for device matching (hours) |
{country_subdivision} | Device subdivision of country, e.g., state |
{country} | Device two-character country code |
{currency} | Original ISO 4217 currency code sent from Adjust SDK |
{gps_adid} | Google Play Store advertising ID |
{idfa} | ID for advertisers (iOS only) |
{idfv} | Uppercase iOS ID for vendors |
{impression_attribution_window} | Attribution window settings for impression matching (hours) |
{inactive_user_definition} | Inactivity period required for reattribution (hours) |
{ip_address} | Device IP address |
{language} | Device two-character language code |
{mac_sha1} | Uppercase MAC SHA-1 hash |
{match_type} | Attribution method |
{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 |
{reattribution_attribution_window} | Attribution window settings for reattribution (hours) |
{region} | Device region code |
{revenue_float} | Revenue, as sent from Adjust SDK, in whole currency units |
{revenue_usd} | Revenue, in US dollars |
{tracking_enabled} | 1 if tracking is enabled, 0 if not |
{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_version_short} | App version number (Android), release-version-number for the bundle (iOS) |
{click_time} | Attributed click timestamp |
{connection_type} | Internet connection type |
{created_at} | Activity timestamp |
{fingerprint_attribution_window} | Attribution window settings for device fingerprinting (hours) |
{impression_based} | 1 if impression-based engagement, 0 if not |
{impression_time} | Attributed impression timestamp |
{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 |
{store} | Target store of click |
{is_s2s} | 1 if server to server engagement, 0 if not |
{is_s2s_engagement_based} | 1 if attributed to a server to server engagement, 0 if not |