We constantly publish updates to our documentation, which may not yet be available in your language. For the most current information, use the English version.

for Marketers

Set up server-to-server (S2S) security

With Adjust's S2S security feature, you can add an authentication token to requests. This secures your S2S events and ad revenue, and protects against spoofed requests.

After you set up S2S security, each incoming request must carry a token generated in AppView. Requests that do not carry a valid token are rejected by our server.

Before you begin

Here's what you need to know before getting started.

S2S Security is not compatible with Google Tag Manager event measurement. Using Adjust's S2S authentication tokens in your Google Tag Manager configuration means that incoming Google Tag events are rejected.

Create an S2S token

Important:

You must configure at least one token to enable S2S authentication.

Under AppView, select All apps.
Select your app.
Select the Protection tab.
Under the S2S Security section, select Open S2S Security.
Select Add token.
Enter a token name, and select Add token.
Select the copy icon () to copy the token, and send it to your developer to add to your S2S event requests.
Ask your developer to run tests to confirm the integration.

At this point, S2S authentication is not active and requests carrying invalid tokens are still accepted. Speak to your dedicated Technical Account Manager or contact support@adjust.com to validate the setup before activating S2S authentication.

Token scopes

When S2S authentication is enabled, you must specify scopes for each token. Scopes define what actions you can take using a token. The following scopes are available:

Events: grants the ability to send event data.
Sessions: grants the ability to send session data.
Ad revenue: grants the ability to send ad revenue data.

Create a scoped token

To create a new scoped token:

Under AppView, select All apps.
Select your app.
Select the Protection tab.
Under the S2S Security section, select Open S2S Security.
Select Add token. A modal appears.
In the modal that appears, enter a token Token name.
Select the scope(s) you want to assign to the token from the Scope dropdown. You can select multiple scopes for each token.
Select Add token to save your token.
Select Copy token and close to copy the token. Send it to your developer to add to your S2S event requests.

The scopes of each token are visible in the token list.

Modify a scoped token

To modify the scopes of an existing token:

Under AppView, select All apps.
Select your app.
Select the Protection tab.
Under the S2S Security section, select Open S2S Security.
Find your token in the list and select the edit icon ().
Add or remove scopes from the Scope dropdown.
Select Edit token to save your changes.

Activate S2S authentication

Important:

Activate S2S authentication only after your developer has tested token implementation, and your Technical Account Manager or our team at support@adjust.com has validated your setup.

To activate S2S authentication, follow these steps.

Under AppView, select All apps.
Select your app.
Select the Protection tab.
Under the S2S Security section, select Open S2S Security.
Ensure you have at least one token configured.
Switch the toggle ON. A warning message appears to inform you that only requests sent with configured tokens will work.
Select Turn on to proceed.

Now, all incoming S2S requests are required to carry an active authentication token. If you previously configured a token without any scopes, these will continue to work for all endpoints. For added security, you should use scoped tokens.

S2S developer documentation

Use the link below to view all documentation for developers about server-to-server integration.

Server-to-server integration for developers