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

Re-enable/disable third-party sharing via S2S

With Adjust, you can manage how data is shared with third parties for statistics purposes. This gives your users greater choice over how their data is handled. Here, you can find instructions on how to re-enable and disable third-party sharing server-to-server (S2S).

Note:

Any user that opts-out of sharing user data will not be re-targeted again, even if they opt-in at a later point. This means they are not included in Audiences lists.

Minimum SDK version	Developer documentation
Android SDK 4.26.0+	Android - re-enable sharing
iOS SDK 4.25.0+	iOS - re-enable sharing

Endpoint

The API endpoint request address is:

https://s2s.adjust.com/third_party_sharing

Use a POST request to interact with the API. You can also send endpoint parameters in the URL or as form data.

Required parameters

Parameter name	Value
`gps_adid`, `idfa`	Device ID string. At least one device ID is required. The API supports the same device IDs supported by other Adjust S2S APIs.
`s2s`	Always `1`
`app_token`	The app token.
`sharing`	`enable` or `disable` to allow or prevent third-party sharing, respectively.

Responses

Success response

You will receive the following for a successful response:

{
   “status”: "OK"
}

Error response

In case of an error, you will receive a 400 Bad Request response status code along with a message describing the error.

Example:

{
   "error": "Third party sharing failed (App not found)”
}

Example URLs

Insert the enable parameter to allow third-party sharing, for example:

https://s2s.adjust.com/third_party_sharing?s2s=1&sharing=enable&app_token=abc123abc123&gps_adid=10820328-872d-43a2-9786-0ccc748335d9

Insert the disable parameter to prevent third-party sharing, for example:

https://s2s.adjust.com/third_party_sharing?s2s=1&sharing=disable&app_token=abc123abc123&gps_adid=10820328-872d-43a2-9786-0ccc748335d9

Provide consent data to Google (Digital Markets Act compliance)

To comply with the EU's Digital Markets Act (DMA), Google Ads and the Google Marketing Platform require explicit consent to receive Adjust’s attribution requests to their APIs.

In the event a user changes their consent response, you can use Adjust's re-enable/disable third party sharing API to share this with us. Pass the following parameters in your request:

Key	Value	Description
`eea`	1 = users are in the EEA and the DMA applies 0 = users are not in the EEA and the DMA does not apply	The eea parameter informs Google whether users are located in the EEA and thus whether the European regulations, including the DMA, apply to this user and conversion. The parameter type is boolean.
`ad_personalization`	1 = user consented 0 = user did not consent	For Google Ads The ad_personalization parameter informs whether users consented to being served personalized ads via Google Ads after installing the app, i.e. whether Google can retarget the users.
`ad_user_data`	1 = user consented 0 = user did not consent	The ad_user_data parameter informs Google whether users granted consent to personal data being shared for measurement purposes or not. The consent applies to all the Core Platform Services (CPS) advertisers have specified in their Google Ads and Google Marketing Platform UI.
`npa`	1 = user did not consent 0 = user consented	For Google Marketing Platform The npa parameter informs whether users consented to being served personalized ads via Google Marketing Platform after installing the app, i.e. whether Google can retarget the users.

Note that you need to send the ad_personalization parameter if you are working with Google Ads, and the npa parameter if you are working with Google Marketing Platform.