Server-to-server connectors allow you to activate audiences and orchestrate journeys by sending profile data directly to your chosen destination platforms — for example, Meta, Google DV360, or email marketing tools. This article explains how to configure, manage, and monitor these connectors within the Data Activation Platform.
Viewing configured connectors
To see which connectors you've already set up, navigate to Connectors → Server to Server Connectors.
From this page, you can:
Configure and activate a new partner server-to-server integration
Edit, disable, or delete a partner integration configuration
View data statistics per partner integration
Setting up a new connector
Before connecting to a specific channel, make sure you:
Have an active account with that vendor
Have the Data Activation Platform whitelisted in the vendor's system
To create a new connector:
Go to Connectors.
Select Server to Server Connectors.
Click New Connector.
You'll see a list of available connectors, including both server-to-server and tag-based options.
Note
The partner type determines where the correct identifier is stored.
Creating new partner configuration
After you select a connector, a new screen prompts you to enter the relevant details for that integration. Some partners, such as DV360, allow multiple configurations — for example, separate accounts for different sub-brands or marketing regions.
Partner data statistics
The partners overview displays traffic statistics per connector for 7, 30, or 90 days. The graph shows how many messages we send to the partner's platform:
Green: Profiles successfully sent to the destination
Blue: Profiles successfully removed from the segment or audience at the partner's platform
Other colours: Errors, categorized as follows:
Other error: A general error that provides limited insights (we're working to improve this)
Invalid credentials: Something is wrong with the credentials — this could be an expired password or insufficient privileges
Timeout: We stop the request if the destination doesn't respond within the timeout period (typically around 3 seconds)
Partner error codes: For 6 connectors (Xandr, CM360, DV360, Azure non-event, Facebook, Clang batch), we report the actual partner error code when available. Check the connector documentation for references to partner error documentation.
Deactivating a connector
You can deactivate a connector even when it's still connected to audiences or journeys. This allows you to quickly stop sending data to that partner if needed. A deactivated connector displays a "deactivated" label.
Important
If a live journey has unpublished changes, it will continue sending data. To ensure no journey sends data, publish all changes.
Deleting a connector
You can only delete a connector if it's not used in any integration. This prevents accidental data loss. To delete a connector, first remove it from each audience where it's configured.