Adjust Destination

Adjust is the mobile attribution provider of choice for hundreds of organizations across the globe. They unify all your marketing activities into one powerful platform, giving you the insights you need to scale your business. The Adjust Destination is open-source. You can browse the code on GitHub for iOS and Android.

This document was last updated on January 31, 2018. If you notice any gaps, out-dated information or simply want to leave some feedback to help us improve our documentation, please let us know!

Getting Started

The first step is to make sure Adjust supports the source type and connection mode you’ve chosen to implement. You can learn more about what dictates the connection modes we support here.

📱 Device-based
☁️ Cloud-based
  1. From your Segment UI’s Destinations page click on “Add Destination”.
  2. Search for “Adjust” within the Destinations Catalog and confirm the Source you’d like to connect to.
  3. Do not need to include Adjust’s SDK natively as this prevent you from successfully implementing the Adjust.
  4. Depending on the source you’ve selected, include Adjust’s library by adding the following lines to your dependency configuration.


If you are using iOS, simply add this line to your CocoaPods Podfile:

pod "Segment-Adjust"

After adding the dependency, you must register the destination with our SDK. To do this, import the Adjust destination in your AppDelegate:

#import <Segment-Adjust/SEGAdjustIntegrationFactory.h>

And add the following lines:

NSString *const SEGMENT_WRITE_KEY = @" ... ";
SEGAnalyticsConfiguration *config = [SEGAnalyticsConfiguration configurationWithWriteKey:SEGMENT_WRITE_KEY];

[config use:[SEGAdjustIntegrationFactory instance]];

[SEGAnalytics setupWithConfiguration:config];

In cases where the Adjust integration sometimes does not track the install attribution properly, you can configure a delay for the Adjust reporting to ensure all session parameters have been loaded properly. Segment allows you to configure this via our UI by enabling setDelay and providing a delayTime in seconds. Segment then calls the Adjust iOS SDK’s configuration to set a delay. The maximum delay start time of the Adjust SDK is 10 seconds.


If you are using Android, simply add this line to your gradle file:

compile ''

After adding the dependency, you must register the destination with our SDK. To do this, import the Adjust destination:


And add the following line:

analytics = new Analytics.Builder(this, "write_key")

After you build and release to the App Store, we’ll automatically start translating and sending your data to Adjust.


Our server-side integration allows you to send supplemental data to Adjust via our server-side integration. This, however, does not include attribution events. If you are relying on the Adjust server-side component, and you are not bundling the Segment-Adjust SDK, your installs will not be attributed. Ecommerce events and other general track events are supported out of the box. You must map your track events to your custom Adjust Event Token in your Adjust destination settings.

Additionally, to send any events to Adjust from the server, you must include the as well as the device.type in the context object of your event. For example:

  userId: '019mr8mf4r',
  event: 'Item Purchased',
  properties: {
    revenue: 39.95,
    shippingMethod: '2-day'
  context: {
    device: {
      id: '3e9ffbefafe0d903',
      type: 'Android'


If you haven’t had a chance to review our spec, please take a look to understand what the Identify method does. An example call would look like:

analytics.identify('12091906-01011992', {
  name: 'Grace Hopper',
  email: ''

When you call identify, Segment will call Adjust’s addSessionPartnerParameter method and set the userId and/or anonymousId. This will set these values within Adjust, and allow Adjust to send back attribution data from their servers.


If you haven’t had a chance to review our spec, please take a look to understand what the Track method does. An example call would look like:

analytics.track('Article Completed', {
  title: 'How to Create a Tracking Plan',
  course: 'Intro to Analytics',

When you call track Segment maps the event to your pre-defined Adjust custom event. You must map your track events to your custom Adjust Event Token in your Adjust destination settings.

If you don’t provide a mapping, Adjust cannot accept the event. We include all the event properties as callback parameters on the Adjust event, and automatically translate revenue and currency to the appropriate Adjust event properties based on our spec’d properties.


If you haven’t had a chance to review our spec, please take a look to understand what the Reset method does. An example call would look like:


When you call reset, Segment will reset these partner parameters via Adjust’s resetSessionPartnerParameters method.

Install Attributed


Segment will trigger an Install Attributed event if you have trackAttributionData enabled in your settings, and the Segment-Adjust integration installed in your app.

Using Adjust’s Attribution callback, Segment listens for an attribution change from Adjust’s SDK and triggers the call with the following Adjust attribution parameters:

providerAdjusthardcoded by Segment
trackerTokenattribution.trackerTokenthe tracker token of the current install
trackerNameattribution.trackerNamethe tracker name of the current install
campaign.sourceattribution.networkthe network grouping level of the current install
campaign.nameattribution.campaignthe campaign grouping level of the current install
campaign.contentattribution.clickLabelthe ad group grouping level of the current install
campaign.adCreativeattribution.creativethe creative grouping level of the current install
campaign.adGroupattribution.adgroupthe click label of the current install

If any value is unavailable, it will default to nil. This call will be sent to all enabled device and cloud mode destinations.


If you are also loading Adjust’s SDK natively in addition to loading via the Segment-Adjust integration, Install Attributed event callback will likely be affected/unable to be triggered. Remove native Adjust implementation.

Since there will not be a change in attribution for registered testing devices you are currently using to send data to Adjust, you will need to unregister that device in Adjust.

To do so:

  1. Take note of the IDFA/advertisingId (you can find this in the raw view of an event in your Segment debugger)
  2. Uninstall the app from your device
  3. Delete the IDFA/advertisingId from Adjust’s testing console
  4. Re-install the app on the device and you should now see the device register in Adjust and an Install Attributed triggered.


Unlike the client-side option to send Install Attributed to Segment, the server-side option will not include device context information nor will it be sent to enabled device mode destinations.

If you are bundling the Segment-Adjust integration and would like attribution data sent from Adjust’s servers back to Segment, you can enable Segment as a Special Partner in Adjust. Once set up, Install Attributed will be sent server-side to Segment and on to enabled server-side destinations.

Please reach out to the Adjust team at for questions related to enabling Segment as a Adjust Special Partner.

Additional Features


By default, our destination sends data to the Adjust Sandbox Environment. When you release your app to the App Store, enable the Production option in the Adjust destination settings on Segment (or use two separate sources, one for dev and one for prod, with different environment settings for Adjust).

Callback Parameters

The destination sends all event properties as callback parameters to Adjust. To set Partner Parameters, you can access the Adjust SDK directly.

Note that we now support setting these Partner Parameters. Be sure you are pulling in the minimum versions for iOS 1.1.0 and Android 0.3.0.

Transaction Deduplication

The destination will automatically recognize the spec’d orderId property, and send it as the transaction ID to Adjust for revenue de-duplication.

Duplicate Purchase Events

If you’re using Adjust’s iOS SDK, it will automatically takes care of duplicate purchase events. We will use Adjust’s transactionId-based deduplication when you send an orderId (see the ecommerce spec).

In-App Purchase Receipts

The destination does not currently support in-app purchase receipts. If this is important to you, please let us know.

Push Notifications

The destination automatically forwards push notification tokens through to Adjust.

Event Buffering

By default, our destination enables event buffering for Adjust. This saves your customers’ battery life. However, you can disable this in the options on the Adjust destination settings on Segment.

Deep Linking

The destination does not automatically support deep linking out of the box (you’d need to write code here regardless). This means you can use Adjust’s deep-linking by accessing the Adjust SDK directly.

Questions? Need help? Contact us!
Can we improve this doc?
Email us:!