Lists and describes the syntax and supported attributes (or key-value pairs) you can pass in to the Data Collection Servers (DCS). This information can help you format your DCS requests and understand the parameters returned by this system.
The DCS relies on specific prefixes added to the keys in key-value pairs to classify the type of data you’re passing in.
Key Prefix | Reserved For |
---|---|
|
Customer-defined attributes. |
|
Audience Manager attributes. |
|
HTTP header data. |
|
Private, customer-defined attributes. The DCS accepts your own, private data when the key has a |
All of these are optional, unless you want a response from the DCS. If you want the DCS to return a response, then d_rtbd=json
is required.
Attribute | Description |
---|---|
|
Used to identify the caller who is making the call to the DCS API. |
|
Specifies a JavaScript function you want to execute using the DCS response as a function parameter of the callback function. |
|
Contains one or more pairs of data provider IDs (
|
|
Contains an integration code and an associated unique user ID in a single key-value pair.
|
|
Disable usage of third party cookies in order to comply with child protection regulations. This parameter is dynamically set by the Adobe Adobe Experience Platform Identity Service and depends on the |
|
Optional. Enabled on customer request. Contact your Adobe Audience Manager consultant or Customer Care. Indicates that traits and segments should be returned inside the
A sample response could look like the one below:
|
|
Deprecated. See |
|
Deprecated. See |
|
Returns URL destination data in the |
|
We advise against creating traits that use reserved attributes. Adobe may change reserved attributes at any time. |
|
Indicates the |
|
Specifies the Experience Cloud ID set and used by the Experience Cloud ID service. For more information about the ECID, see Cookies and the Experience Cloud Identity Service. |
|
Name Space ID. Indicates which JavaScript container is used. Used by DIL to for id-syncing. |
|
Allows Audience Manager to distinguish mobile requests from desktop requests. Supported values include:
|
|
Deprecated. We advise against creating traits that use reserved attributes. Adobe may change reserved attributes at any time. |
|
Required if you want a
|
|
|
|
Passes a data source for trait evaluation. Only traits from this data source are evaluated. For example, say you have:
In a sample call, |
|
The purpose is identical to the Keeping the traits described above, consider the sample call: For |
|
Unique user ID. Identifies a visitor when this value is not available from a cookie. |
These headers contain information like requests for data and responses in an HTTP call.
Attribute | Description |
---|---|
h_host |
This is set to the client’s specific data collection host name. It appears as host name .demdex.net . See Understanding Calls to the Demdex Domain. |
h_user-agent |
Set to the User-Agent header value. |
h_accept-language |
Set to the Accept-Language header value. |
h_referer |
Set to the Referer header value. |
h_referrer |
Set to the Referrer header value. |
h_date |
Set to the Date header value. |