Adjust Cloud Mode Integration

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

Find the open source transformer code for this destination in the GitHub repository.

Supported events

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

• Track

RudderStack does not support Identify events in the cloud mode integration — these events are only available in device mode.

Track

The track call lets you record 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 using Adjust’s server-to-server event endpoint.

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.

A sample track call is shown below:

rudderanalytics.track("Product Purchased", {
  revenue: 20.99,
  currency: "USD",
  quantity: 10
});

Callback parameters

RudderStack sends all custom properties in your track calls as callback parameters to Adjust. However, revenue and currency are excluded from callback parameters as they’re handled separately.

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. RudderStack automatically converts numeric values into strings before sending the data to Adjust.

Suppose you set the following mappings in the RudderStack dashboard:

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

rudderanalytics.track("purchase", {
  revenue: 20.99,
  currency: "USD",
  quantity: 10
});

The corresponding Adjust payload highlighting the parameters is shown below:

{
  "params": {
    "android_id": "3f034872-5e28-45a1-9eda-ce22a3e36d1a",
    "gps_adid": "3f034872-5e28-45a1-9eda-ce22a3e36d1a",
    "att_status": 3,
    "tracking_enabled": true,
    "currency": "USD",
    "ip_address": "[::1]",
    "s2s": 1,
    "app_token": "t1yurrb968zk",
    "event_token": "tf4gm5",
    "environment": "production",
    "partner_params": {
      "price": "20.99",
      "quantity": "10"
    }
  }
}

Revenue tracking

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

rudderanalytics.track("purchase", {
  revenue: 2.99,
  currency: "USD"
});

If you don’t specify the currency property, RudderStack defaults to USD.

Device requirements

For cloud mode to work correctly, your events must include the following device information:

• Device type: Must be either android or an Apple family device (iOS, iPadOS, etc.)
• Device ID: Required for identifying the device
• Advertising ID: Optional but recommended for better attribution

Property mapping

The following table highlights the mapping between RudderStack fields and Adjust parameters:

Note that:

• revenue and currency are excluded from callback_params as they’re handled separately.
• Partner parameters only accept String data type — RudderStack automatically converts numeric values to strings before sending them to Adjust.

Troubleshooting