Continue here for information about how to request a DCS response in a /event
call. This section includes a response example and definitions for common data elements in a response.
Before reviewing this content, see Send Data to the DCS.
Your DCS request must include d_rtbd=json
if you want to receive a response from the DCS. The DCS will not return data if you omit this parameter. A basic call to the DCS to request data uses this syntax:
https://domain_alias.demdex.net/event?key1=val1&key2=val2&d_dst=1&d_rtbd=json&d_cb=callback
Recall that from the Send Data to the DCS documentation, the fictional company Acme, Inc. made this call:
https://acme_aam_domain.demdex.net/event?videoTypeID=2&data=moarData&d_dst=1&d_rtbd=json&d_cb=acme_callback
As this call includes the required response parameter, the DCS sent back the JSON object shown below. Yours may be similar or more complex.
{
"stuff": [],
"uuid": "22920112968019678612904394744954398990",
"dcs_region": 7,
"tid": "31ZpxW5bQGc="
}
The table below lists and defines the more common parameters you may see in a response from the DCS. This applies to event calls or other DCS API queries that return data.
Parameter | Description |
---|---|
c |
A URL that has been set as a URL destination. |
cn |
The name or ID set in the cookie name field of a cookie destination. |
cv |
The values sent to the destination defined by the “cn”:" destinaton name" parameter. |
dcs_region |
The server-to-server DCS calls. |
dests |
This object contains information for all URL destinations which are configured in the UI. This object’s list is dynamic based on the user’s actions. |
dmn |
This is the domain specified in the Cookie Domain field for a cookie destination. See Optional Settings for Cookie Destinations. For Server to Server integrations we recommend using a domain like aam-api.com . |
e |
The secure URL that has been set in a URL destination. |
stuff |
This object contains information for all Cookie destinations. This object’s list is dynamic based on the user’s actions. |
tid |
Transaction ID, which is a unique 12-character ID used for debugging purposes. Each /event call to the DCS receives a tid that you can reference in support enquiries for a better and faster response. |
ttl |
The cookie time-to-live value in days. |
u and uuid |
Unique User ID assigned by Audience Manager. This is required if you’re making server-to-server DCS calls. |
y |
Destination type, iFrame (iframe ) or image (img ). |