Languages 

Set up Liftoff

Liftoff is a network and Adjust module partner. Our integration lets Liftoff receive attribution and in-app event data through automated callbacks.

Use our basic setup instructions to turn on Adjust’s integration and send callbacks to Liftoff. Then, use our advanced setup instructions to customize what information Liftoff receives.

Basic setup

To turn on Adjust’s integration with Liftoff, follow these steps.

  1. Find your app and select your app options caret (^)
  2. Select Partner Setup > ADD PARTNERS
  3. Select the add (+) icon next to Liftoff
  4. Turn on Enabled
  5. Optional: see advanced setup to customize your callbacks
  6. Select Save

Well done! Basic setup is complete. Now you can create an Adjust tracker URL and submit it to Liftoff to launch your campaign.

Liftoff will receive callbacks for these activities:

  • install
  • session
  • uninstall
  • reinstall
  • reattributionReinstall
  • reattribution
  • event
  • rejectedInstall
  • rejectedReattribution
  • ad revenue

Advanced setup

Choose which data Liftoff receives from Adjust by customizing your setup.

Only forward data attributed to Liftoff

Adjust sends Liftoff your installs and reattributions across all ad platforms.

To stop Liftoff from receiving data attributed to other ad platforms, follow these steps.

  1. Find your app and select your app options caret (^)
  2. Select Partner Setup > Liftoff
  3. Turn on Attributed Only

Now Liftoff will only receive data attributed to their own platform.

Forward in-app revenue

In-app revenue forwarding lets Liftoff receive revenue amounts along with your revenue event data.

To forward in-app revenue to Liftoff, follow these steps.

  1. Find your app and select your app options caret (^)
  2. Select Partner Setup > Liftoff
  3. Turn on In-App Revenue Forwarding

Now Liftoff will receive the revenue amount for every tracked transaction.

Note: Link at least one [revenue event] to Liftoff before turning on In-App Revenue Forwarding.

Forward ad revenue

Ad revenue forwarding lets Liftoff receive user ad revenue data. This feature is available with Adjust’s Ad Revenue package. To purchase our Ad Revenue package, contact your sales representative.

To forward ad revenue to Liftoff, follow these steps.

  1. Find your app and select your app options caret (^)
  2. Select Partner Setup > Liftoff
  3. Turn on Ad Revenue Forwarding

Now Liftoff can use ad revenue data to optimize your user targeting and campaigns.

Forward uninstalls / reinstalls

To forward uninstalls and/or reinstalls to Liftoff, follow these steps.

  1. Find your app and select your app options caret (^)
  2. Select Partner Setup > Liftoff
  3. Turn on Uninstall / Reinstall Forwarding

Now Liftoff will receive all of your app’s uninstall and/or reinstall data.

Forward sessions

Adjust does not automatically send session callbacks due to the high volume of sessions.

To forward in-app sessions to Liftoff, follow these steps.

  1. Find your app and select your app options caret (^)
  2. Select Partner Setup > Liftoff
  3. Turn on Session Forwarding

Now Liftoff will receive your app’s session activity.

Forward custom data

Partner parameters (available in Adjust SDK version 4.0+) let Adjust collect custom data points from your app and send them to Liftoff.

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

To forward partner parameters to Liftoff, follow these steps.

  1. Set up partner parameters within the Adjust SDK (instructions for iOS and Android)
  2. In the Adjust dashboard, find your app and select your app options caret (^)
  3. Select Partner Setup > Liftoff
  4. Turn on Parameter Forwarding
  5. Select Partner Parameter Mapping
  6. In the FROM APP field, enter the name of your Adjust parameter (as written into the Adjust SDK). In the TO PARTNER field, enter your corresponding Liftoff name.
  7. Select Save

Now Liftoff will receive custom event details for each of your linked events.

Note: If you set up partner parameters within the Adjust SDK without turning on Partner Parameter Mapping, Adjust forwards the parameters as named in the Adjust SDK.

Forward in-app events

Event linking lets Liftoff receive in-app event data. You can link every in-app event in Adjust to a preset Liftoff name or a custom event name.

To forward in-app events to Liftoff, follow these steps.

  1. Find your app and select your app options caret (^)
  2. Select Partner Setup > Liftoff > Event Linking
  3. Find the event you want to link and update the field with a Liftoff event or your own custom name
  4. When you finish linking events, select OK
  5. Select Save

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

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:

PlaceholderInformation
{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