Making Server-to-Server DCS API Calls
Calls require the host name of the regional DCS server and the user ID. If you do not have the required user and region IDs, see Get User IDs and Regions From a DCS Response and/or Experience Cloud . Once you have user and region IDs, you can make server-to-server calls to the DCS. Refer to this section for syntax and examples.
In the code and examples, italics represents a variable placeholder. Substitute a real value for the placeholder when you server-to-server calls to the DCS.
Call Syntax and Example
A basic server-to-server request that sends data to the DCS uses the syntax shown below.
A sample call looks similar to the following example.
"Host:foo.demdex.net" "https://usw2.demdex.net/event?d_rtbd=json&d_jsonv=1& d_uuid=123456789"`
This part of the call contains:
The http header host parameter which shows the name of the regional DCS server. The host name is tied to a region ID, which is why you need this before making these types of calls. See DCS Region IDs, Locations, and Host Names .
This part of the call:
d_uuid= Audience Manager user ID
This is the unique user ID key that holds the user ID value in a key-value pair.
Use d_uuid if you're passing in the Audience Manager user ID.
d_mid= Experience Cloud user ID
This is the unique user ID key that holds the Experience Cloud user ID value in a key-value pair. See also Get the User ID from the ID Service Cookie .
Use d_mid if you're passing in a Experience Cloud ID captured from the Experience Cloud ID service.
Optional response parameters.
None of these are required to send data to the DCS . However, if you want the DCS to return a response, you must include d_rtbd=json in your request.