Credentials

API token

First locate your API token, which is your user credentials. Learn where to find it here.

App token

Then locate your App token, which can be found under App details in Adjust. Read more here.

Account ID

If your app belongs to a different Adjust account than your API token, you need to specify which account your app belongs to. You may also need this if you see an "Invalid API Token for this App" error for a source.

To find your Adjust account ID:

Log in to the account you want to fetch data from and open https://automate.adjust.com/configs-service/config in your browser.
Find the adjust_account_id field. For example, "adjust_account_id": 1234 means your account ID is 1234.

Configuration

Selecting Report decides whether you get data per event date (Standard) or revenue data in a cohort grouped on install date (Cohort).

The cohort report has an extra dimension called Period. For a 7-day Cohort window it has values between 0 and 6, where "0" has values for the install date and "6" is 6 days after the user installed the app. This is when using "Day" as the Cohort Period; if you use "Week", the Period value "0" means the week the app was installed and "1" the week after.

Selecting Report Level decides the granularity of the data. The "Creative" level includes all trackers, while "Network" only includes the "Network Tracker" dimension.

Select the Additional Dimensions you are interested in. There is no limit on how many you can select, and the metric totals are always the same independent of your selection.

You can select the same attribution, ad spend mode, and timezone settings that you have in the Adjust dashboard, namely:

Attribution Type: read more here.
Attribution Source
Ad Spend Mode: read more here.
Reporting Timezone: the timezone you want to look at the data in.

For the data available from this connector, see Adjust: Dimensions and metrics.

Historical import never finishes for detailed reports

What you see: A creative-level Adjust data source with several breakdowns (such as country, OS or device type) never finishes its historical import. Downloads fail with an error like "ChunkedEncodingError - Response ended prematurely" or "IncompleteRead".

Why it happens: Each breakdown you add multiplies the number of rows Adjust has to return. With a creative-level report and several breakdowns, the response gets so large that the connection times out before it finishes.

What to do:

Remove optional breakdowns you don't need (for example country, device type or OS) from the data source configuration.
Or split the data into several lighter data sources, each with fewer breakdowns, instead of one data source with all of them.

Adjust: Connection guide