Set up Amplitude

Amplitude is an analytics partner integrated with Adjust. Our integration lets Amplitude receive data measured in Adjust through automated callbacks. Use this data with the partners' tools for analytics and insights.

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

Before you begin

Requirements

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

Credentials

API KEY

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

  • click
  • install
  • session
  • uninstall
  • reinstall
  • reattribution
  • event

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 Amplitude by default:

  • click
  • install
  • session
  • uninstall
  • reinstall
  • reattribution
  • event

Send additional data

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

To send additional data, you can review and customize the following:

In-app revenue (from in-app purchases)

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

Uninstalls or reinstalls

Sharing uninstalls or reinstalls lets Amplitude receive your app’s uninstall and/or reinstall data measured by Adjust.

Note:

For iOS apps, you might expect a low record of uninstalls and/or reinstalls. For more information, visit Uninstall and reinstall measurement.

Sessions

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

Map events

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

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

  1. Select Map event.
  2. In the Adjust event list, choose the Adjust event that you want to share with Amplitude.
  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 Amplitude will receive in-app event data for each of your linked events.

Enable Amplitude for your app

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

Select Enable partner to enable Amplitude for your app. Analytics partners don't work with links for campaigns. Once enabled, our integration sends attribution and in-app event data via automated callbacks.

List of all parameters forwarded to Amplitude

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

PlaceholderInformation
{android_id}Android ID (Android only)
{cost_amount}Cost of the user engagement (available for ad spend tracking only)
{cost_currency}ISO 4217 currency code of the cost data (available for ad spend tracking only)
{cost_type}The campaign pricing model (available for ad spend tracking only)
{fire_adid}Fire OS advertising identifier
{idfa||gps_adid}IDFA, or GPS ADID if IDFA is empty
{idfv}Uppercase iOS ID for vendors
{os_name}Device operating system
{revenue}Revenue, as sent from Adjust SDK in cents
{adgroup_name}Adgroup name, as taken from the tracker
{app_version}App version number (Android), build-version-number for the bundle (iOS)
{campaign_name}Campaign name, as taken from the tracker
{created_at}Activity timestamp
{creative_name}Creative name, as taken from the tracker
{network_name}Network name, as taken from the tracker
{tracker_name}Current tracker name