Show Menu
TOPICS×

DCS Error Codes, Messages, and Examples

Error codes and messages generated by the Data Collection Servers (DCS) listed in numeric order by code ID.
In the tables below, italics represents a variable placeholder.

System Error Codes

Code ID Error Message Description
0
Unspecified error
This is a catch-all error that handles events that is not covered by the other error handlers. Troubleshooting this error is difficult. It can be caused by a variety of unknown actions or events.
If you receive this error, try your DCS request again. Contact your Adobe representative if the problem persists.
1
Could not find config for hostname: hostname
The host name sent in the request has not been set up by our partner provisioning team. Contact your Adobe representative if you see this error message.
2
Invalid d_orgid value (could not find a config for this org id): ID
The Organization ID is incorrect.
Check your ID and try the request again. If you do not know or have your Organization ID, see the "Administration Page" section in Experience Cloud Administration for information about how to find it.

Integration Error Codes

Code ID Message Description
100
Could not retrieve host name for the request
An API call did not send the host HTTP header in the request.
Add host header to the call and try again. Note, most browsers and API clients do this automatically.
101
Invalid Experience Cloud id passed in ID
The DCS call contains an invalid Experience Cloud ID.
Check the d_mid= key-value pair in the header string. Make sure you're passing in the correct Experience Cloud ID and try the request again.
102
Invalid aam id passed in request ID
The DCS call contains an invalid Audience Manager ID.
Check the d_uuid= key-value pair in the header string. Make sure you're passing in the correct Audience Manager ID and try the request again.
104
All customer ids are invalid
All of the customer IDs in your call are invalid. Check your IDs and try again.
109
Referer HTTP referer is not allowed for partner Partner ID
The [!DNL HTTP referer] header on the call is not allowed for the partner ID on the call. Check that the [!DNL HTTP referer] header is correct.
111
Invalid IMS token received
Returned for Audience Manager - Adobe Target integrations. The error is thrown when a call is made to the DCS, containing an invalid IMS token. The token might be malformed, expired or the user might not be authorized to access the required resource.

Opt-Out Error Codes

Code ID Message Description
171
Encountered opt out tag for id ID
A customer has opted-out from receiving interest-based advertising.
172
Blocked cookies
Returned when the user's browser blocks third-party cookies.
173
Encountered trust relationship via NAI
The user has initiated an opt-out process through NAI.
198
Requests from this country are blocked by partner
Based on the IP address, the DCS blocks requests from countries where the partner has deliberately limited the traffic.
199
Requests from this country are not allowed
Based on the IP address, the DCS blocks requests from the following countries:
  • Cuba (CU)
  • Iran (IR)
  • North Korea (KP)
  • Sudan (SD)
  • Syria (SY)

Profile Retrieval Error Codes

Code ID Message Description
200
Cannot read traits from profile cache for id: ID
Returned when a user profile cannot be read from our internal storage.
201
Cannot read device ids from profile cache for customer id: ID
Returned when the device ID cannot be retrieved for a Profile Link merge rule.
202
Cannot read related customer for device id: ID
Returned when the customer ID (UUID) associated to a device ID cannot be retrieved for a Last Authenticated merge rule from our internal storage.
203
Cannot read device cluster for id: ID
The linked device IDs from the same device graph cluster cannot be returned for this device ID.
204
Could not perform migration since profile read failed for primary device
If you receive this error, we may be experiencing scalability issues with our data store ( PCS ). Contact your Adobe representative if the problem persists.
205
Could not perform migration from ID to ID , because profile read failed for ID
If you receive this error, we may be experiencing scalability issues with our data store ( PCS ). Contact your Adobe representative if the problem persists.

Integration Warning Codes

Code ID Message Description
300
Invalid customer id ID
The customer ID is invalid (missing values for data source, missing integration codes, invalid format for data sources, blocked customer ID, blank customer ID, unauthorized access attempt to a data source that does not belong to the partner).
301
Maximum number of customer ids exceeded. Maximum allowed is maximum allowed . Found is maximum found .
The number of customer IDs associated with a cross-device data source exceed the allowed number of cross-device IDs per request. These IDs include cross device, mobile, or cookie IDs. The limit is currently set to 10.
302
Unauthorized customer id ID
Returned when the customer ID data source is not owned by the current Organization ID. If you do not know or have your Organization ID, see the "Find your Organization ID" section in Organizations and Account Linking for information about how to find it.
303
Blocked customer id ID
Returned when the customer ID has been identified as malicious and has been blacklisted.
304
Blocked datasource id ID
Returned when the data source ID has been identified as malicious and has been blacklisted.
306
Blocked declared device id ID
The device ID has been identified as malicious and has been blacklisted. This can happen when we receive an extreme amount of DCS requests containing this device ID in a short amount of time.
307
Blocked profile operation for ID
A read/write action has been blocked because an ID has been identified as malicious and has been blacklisted. See error code 306.
309
Customer id ID was discarded because it exceeded the limit of declared customer ids per request
Related to error 301. This error specifies which customer ID was discarded because the limit was exceeded.
For example, If there are 12 customer IDs declared on the DCS call, two of them will be discarded. In order to relay which ones were discarded, this error will appear twice in the response (once for each of discarded customer ID ).
310
Customer id was discarded because it exceeded the limit for a given namespace. Namespace id is ID , customer id is ID .
This error code is returned if there are more than 3 customer IDs declared for the same namespace ( DPID ) on a DCS call.
https://partner.demdex.net/event?d_rtbd=json&d_cid_ic=one&d_cid_ic=one&d_cid_ic=one&d_cid_ic=one
In this sample DCS request, there are 4 ids declared for the same namespace (with the integration code one). One of the IDs is discarded and error 310 is returned.
311
Request contains invalid parameters
The DCS returns this error code when at least one URL parameter is not properly encoded. In this case, the DCS disregards the entire request.
http(s)://partner.demdex.net/event?d_event=imp&d_rtbd=json&d_src=38454&d_site=%esid!&d_creative=%ecid!&d_adgroup=%eaid!&d_placement=%epid!&d_campaign=%ebuy!&d_adsrc=48123
In the sample request above, the % sequence is incorrectly encoded. Consequently, the DCS will disregard it.
The correctly encoded sample should look like this:
http(s)://partner.demdex.net/event?d_event=imp&d_rtbd=json&d_src=38454&d_site=%25esid!&d_creative=%25ecid!&d_adgroup=%25eaid!&d_placement=%25epid!&d_campaign=%25ebuy!&d_adsrc=48123
312
Request contains an invalid Global Device ID
The DCS returns this error code when the request contains an invalid Global Device ID. DCS ignores the invalid ID and throws a 312 error along with the specific errors of the invalid ID. Refer to Global Data Sources and Index of IDs in Audience Manager for detailed information on the correct device advertising ID formats and corresponding global data sources.
Example of an incorrect call: "http://partner.demdex.net/event?d_rtbd=json&d_cid=20915%01a53cc5a2-6aa1-4210-8ded-a88b29b6212z"
Explanation: An IDFA (DPID 20915) must be an uppercase ID. The ID provided in the request is lowercase.

Sample Error Code Messages

The DCS returns error codes and messages in a JSON object or in an X- header in the HTTP response string.

Sample DCS Error Code and Message

{ 
   "errors":[ 
      { 
         "code":101,
         "msg":"Invalid Experience Cloud id passed in"
      },
      { 
         "code":102,
         "msg":"Invalid aam id passed in request"
      }
   ]
}

X-Error

Error codes captured by the X- header appear in the URL string like this, X-Error: 101,102 .