Adjust Device Mode Integration

After you have successfully instrumented Adjust as a destination in RudderStack, follow this guide to correctly send your events to Adjust in device mode.

See the following GitHub repositories for more information on the implementation:

• Android
• iOS

Add device mode integration

Follow these steps to add Adjust to your project depending on your integration platform:

pod 'Rudder-Adjust'

#import <Rudder-Adjust/RudderAdjustFactory.h>

RudderConfigBuilder *builder = [[RudderConfigBuilder alloc] init];
[builder withDataPlaneUrl:DATA_PLANE_URL];
[builder withFactory:[RudderAdjustFactory instance]];
[RudderClient getInstance:WRITE_KEY config:[builder build]];

pod 'RudderAdjust', '~> 1.0.0'

import RudderAdjust

@import RudderAdjust;

let config: RSConfig = RSConfig(writeKey: WRITE_KEY)
            .dataPlaneURL(DATA_PLANE_URL)

RSClient.sharedInstance().configure(with: config)
RSClient.sharedInstance().addDestination(RudderAdjustDestination())

RSConfig *config = [[RSConfig alloc] initWithWriteKey:WRITE_KEY];
[config dataPlaneURL:DATA_PLANE_URL];

[[RSClient sharedInstance] configureWith:config];
[[RSClient sharedInstance] addDestination:[[RudderAdjustDestination alloc] init]];

dependencies {
  // ...
  
  // Add Rudder Kotlin and Adjust integration SDKs:
  implementation("com.rudderstack.sdk.kotlin:android:<latest-version>")
  implementation("com.rudderstack.integration.kotlin:adjust:<latest-version>")
}

import android.app.Application
import com.rudderstack.sdk.kotlin.android.Analytics
import com.rudderstack.sdk.kotlin.android.Configuration
import com.rudderstack.integration.kotlin.adjust.AdjustIntegration

class MyApplication : Application() {
    lateinit var analytics: Analytics

    override fun onCreate() {
        super.onCreate()
        analytics = Analytics(
            configuration = Configuration(
                writeKey = "WRITE_KEY",
                application = this,
                dataPlaneUrl = "DATA_PLANE_URL",
            )
        )
        
        analytics.add(AdjustIntegration())
    }
}

repositories {
  mavenCentral()
}

<uses-permission android:name="android.permission.INTERNET"></uses-permission>
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE"></uses-permission>
// If you are not targeting the Google Play Store, you need to add the following permission:
<uses-permission android:name="android.permission.ACCESS_WIFI_STATE"></uses-permission>
// If you are targeting Android 13 and above (API level 33), you need to add the com.google.android.gms.AD_ID permission to read the device's advertising ID.
<uses-permission android:name="com.google.android.gms.permission.AD_ID"></uses-permission>

// RudderStack Android-SDK
implementation 'com.rudderstack.android.sdk:core:[1.0,2.0)'
// RudderStack Adjust-SDK
implementation 'com.rudderstack.android.integration:adjust:1.0.1'
// Add Google Play Services library to enable the Google Advertising ID for Adjust SDK
implementation 'com.google.android.gms:play-services-ads-identifier:17.0.1'
// To support the Google Play Referrer API, make sure you have the following in your build.gradle file:
implementation 'com.android.installreferrer:installreferrer:2.2'

import com.rudderstack.android.integration.adjust.AdjustIntegrationFactory;

val rudderClient: RudderClient =
    RudderClient.getInstance(
        this,
        WRITE_KEY,
        RudderConfig.Builder()
            .withDataPlaneUrl(DATA_PLANE_URL)
            .withFactory(AdjustIntegrationFactory.FACTORY)
            .build()
    )

// Build your config
RudderConfigBuilder configBuilder = new RudderConfigBuilder()
    .WithEndPointUrl(DATA_PLANE_URL)
    .WithFactory(RudderAdjustIntegrationFactory.GetFactory());

// Get instance for RudderClient
RudderClient rudderClient = RudderClient.GetInstance(
    WRITE_KEY,
    configBuilder.Build()
);

rudder_integration_adjust_flutter: ^1.0.1

flutter pub get

import 'package:rudder_integration_adjust_flutter/rudder_integration_adjust_flutter.dart';

final RudderController rudderClient = RudderController.instance;
RudderConfigBuilder builder = RudderConfigBuilder();
builder.withFactory(RudderIntegrationAdjustFlutter());
rudderClient.initialize(<write_key>, config: builder.build(), options: null);

Supported events

In device mode, RudderStack supports sending the following events to Adjust:

• Identify
• Track

Identify

RudderStack’s identify call lets you identify a visiting user and associate them to their actions.

RudderStack sends the user information in the identify call to Adjust’s addSessionPartnerParameter method to set the userId (or anonymousId, in case userId is absent), so that the user information is passed to the subsequent calls.

A sample identify call is shown below:

[[RudderClient sharedInstance] identify:@"developer_user_id"
                                 traits:@{@"foo": @"bar", @"foo1": @"bar1"}];

Track

The track call lets you record the user actions along with any properties associated with them.

When you make a track call, RudderStack maps the event name with the corresponding Adjust custom event in the dashboard using Adjust’s trackEvent method.

Make sure to define the event mapping in the Map events to Adjust Event Tokens dashboard setting. Adjust will reject any events apart from these mappings.

You must create the event token in the Adjust dashboard before specifying the mappings.

Callback parameters

RudderStack sends all custom properties in your track calls as callback parameters.

A sample track call is shown below:

[[RudderClient sharedInstance] track:@"test_event"
                          properties:@{@"key":@"value", @"foo": @"bar"}];

Partner parameters

You can also send custom properties in your track calls as partner parameters to Adjust. Adjust then sends those parameters to the external partners you have set up in your Adjust dashboard. See the FAQ for more information on adding a partner in Adjust.

RudderStack uses the property mappings specified in the RudderStack Parameters to Partner Parameters dashboard setting to check if a key is present in the track event properties and maps it to the corresponding Adjust partner parameter object.

• Adjust will reject any properties apart from mappings specified in the RudderStack Parameters to Partner Parameters dashboard setting.
• The partner parameters only accept the String data type.

Suppose you set the following mappings in the RudderStack dashboard:

A sample track call with the above properties is shown below:

[[RudderClient sharedInstance] track:@"purchase"
                          properties:@{@"revenue":@20.99,
                          @"currency": @"USD",
                          @"quantity": @10}];

Revenue tracking

To send revenue tracking events to Adjust, add revenue and currency to your event properties:

[[RudderClient sharedInstance] track:@"purchase"
                          properties:@{@"revenue":@2.99, @"currency": @"USD"}];

App install attribution

RudderStack’s Adjust mobile integration (iOS and Android) automatically triggers an Install Attributed event if you have enabled Install Attribution tracking in the dashboard settings.

The enhanced attribution support is available from:

• Rudder-Adjust Android v2.1.0 and above
• Rudder-Adjust iOS v2.2.0 and above

Usage

Follow these steps to use the enhanced attribution tracking feature:

1. Configure token mapping in the Adjust dashboard

1. In your Adjust dashboard, create a new event token specifically for the Install Attributed event — you can also use an existing event token in case you have one.
2. Copy the generated event token.
3. Use this token in the Adjust destination configuration (explained below).

2. Adjust destination configuration in RudderStack

1. In your RudderStack dashboard, add Adjust as a mobile device mode destination.
2. Specify your Adjust App Token.
3. In the Map events to Adjust event tokens dashboard setting, map the Install Attributed event to the event token obtained above.
4. Save the mapping.

3. Enable automatic attribution tracking

Toggle on the Enable Install Attribution dashboard setting to automatically track the Install Attributed event when the app is installed for the first time.

How attribution tracking works

By leveraging Adjust’s attribution callback on iOS and Android, the integration listens for an attribution change from Adjust’s SDK and triggers the event with the following Adjust attribution parameters:

An example of the attribution data automatically captured by the Install Attributed event is shown below:

{
  "event": "Install Attributed",
  "properties": {
    "provider": "Adjust",
    "trackerToken": "abc123",
    "trackerName": "Campaign Name",
    "campaign": {
      "source": "google",
      "name": "summer_campaign",
      "content": "click_label",
      "adCreative": "banner_ad",
      "adGroup": "mobile_users"
    }
  }
}

If any of the above values are unavailable, they are defaulted to null. This event is then sent to all the connected device mode and cloud destinations.

See the following FAQs for troubleshooting tips:

• Why are the Install Attributed events not appearing in my Adjust dashboard?
• Why is the Install Attributed event not triggering?

Environment dependency on log level

Property mapping

RudderStack’s device mode integration automatically handles device information through the native Adjust SDK. The following table shows how RudderStack events map to Adjust’s native methods:

Device mode automatically handles device identification through the native Adjust SDK, so you don’t need to manually provide context.device information like in cloud mode.

Troubleshooting

Questions? Contact us by Email or on Slack