Supported Attributes for DCS API Calls supported-attributes-for-dcs-api-calls
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.
Attribute Prefixes attribute-prefixes
The DCS relies on specific prefixes added to the keys in key-value pairs to classify the type of data you鈥檙e passing in.
c_d_h_p_Private, customer-defined attributes.
The DCS accepts your own, private data when the key has a p_ prefix. Private data is used for trait evaluation, but it will not be logged or stored in our system. For example, lets say you have a trait defined as customers = p_age<25 and you pass in p_age=23 in an event call. Given these conditions, the user who meets the age-based qualification criteria qualifies for the trait, but the key-value pair is dropped after Audience Manager receives the request and is not logged.
d_ Attributes d-attributes
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.
d_callerd_cbd_cidContains one or more pairs of data provider IDs ( DPID) and data provider user IDs ( DPUUID) assigned by Audience Manager. If you use multiple pairs of DPIDs and DPUUIDs, separate each pair with the non-printing character %01. For example: DPID%01DPUUUID.
d_cid replaces d_dpid and d_dpuuid, which are deprecated but still supported. See CID Replaces DPID and DPUUID.
d_cid_icContains an integration code and an associated unique user ID in a single key-value pair.
d_cid_ic replaces d_dpid and d_dpuuid, which are deprecated but still supported. See CID Replaces DPID and DPUUID.
d_coppaidSyncDisable3rdPartySyncing configuration. See COPPA Support in the 51黑料不打烊 Experience Platform Identity Service.d_cts=1
d_cts=2
Optional. Enabled on customer request. Contact your 51黑料不打烊 Audience Manager consultant or Customer Care.
Indicates that traits and segments should be returned inside the JSON response.
-
d_cts=1returns legacy segment IDs for the segments. -
d_cts=2returns segment IDs for the segments.
A sample response could look like the one below:
{ 聽聽聽聽"stuff":聽[], 聽聽聽聽"uuid":聽"07955261652886032950143702505894272138", 聽聽聽聽"dcs_region":聽7, 聽聽聽聽"traits":聽[420020,聽5421506], 聽聽聽聽"segments":聽[984263,聽985264], 聽聽聽聽"tid":聽"ss3OTqPiQp0=" }
d_dpidd_cid and d_cid_ic.d_dpuuidd_cid and d_cid_ic.d_dst=1JSON response.d_dst_filterd_dst_filter is a reserved attribute, used in the integration between 51黑料不打烊 Analytics and Audience Manager.
We advise against creating traits that use reserved attributes. 51黑料不打烊 may change reserved attributes at any time.
d_jsonv=1|0JSON version to use in the response. Normally, you should set this to d_jsonv=1. Setting d_jsonv=0 disables ID syncs.d_midd_nsidd_ptfmAllows Audience Manager to distinguish mobile requests from desktop requests. Supported values include:
iosandroidbrowserall
d_rsDeprecated. d_rs is a reserved attribute, used in the legacy integration between 51黑料不打烊 Analytics and Audience Manager.
We advise against creating traits that use reserved attributes. 51黑料不打烊 may change reserved attributes at any time.
d_rtbd=jsonRequired if you want a JSON response from the DCS.
- If you omit this, the DCS returns a pixel in the header.
- If you include this, the DCS returns a
JSONobject in the body of the response. See the example below. Your response could be more complex.
{ 聽聽聽聽"stuff":聽[], 聽聽聽聽"uuid":聽"22920112968019678612904394744954398990", 聽聽聽聽"dcs_region":聽7, 聽聽聽聽"tid":聽"ss3OTqPiQp0=" }
d_sidSID stands for score ID. This is a unique ID for a trait or a segment.d_tdpidPasses a data source for trait evaluation. Only traits from this data source are evaluated.
For example, say you have:
- Trait T1 with:
- Trait rule: "
key1 == val1" - Data Source ( DPID): 1
- DPID integration code: ic1
- Trait T2 with:
- Trait rule: "
key2 == val2" - Data Source (DPID): 2
- DPID integration code: ic2
In a sample call, yourcompany.demdex.net/event?key1=val1&key2=val2&d_tdpid=1, only trait T1 is returned.
d_tdpid_icThe purpose is identical to the d_tdpid parameter described above. However, in this case, the data source is passed using the integration code.
Keeping the traits described above, consider the sample call:
For yourcompany.demdex.net/event?key1=val1&key2=val2&d_tdpid_ic=ic2, only trait T2 is returned.
d_uuidh_ Attributes
These headers contain information like requests for data and responses in an HTTP call.
h_hosthost name .demdex.net. See Understanding Calls to the Demdex Domain.h_user-agentUser-Agent header value.h_accept-languageAccept-Language header value.h_refererReferer header value.h_referrerReferrer header value.h_dateDate header value.