Integration Error Codes

Error CodeError MessageDescription
100Could not retrieve host name for the requestAn API call did not send the host HTTP header in the request. Add the host header to the call and try again. Most browsers and API clients do this automatically.
101Invalid Experience Cloud id passed in IDThe 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.
102Invalid AAM ID passed in request IDThe 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.
104All customer IDs are invalidAll of the customer IDs in your call are invalid. Check your IDs and try again.
109Referer HTTP referer is not allowed for partner Partner IDThe HTTP referer header on the call is not allowed for the partner ID on the call. Check that the HTTP referer header is correct.
111Invalid IMS token receivedReturned 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 IDMessageDescription
171Encountered opt out tag for id IDA customer has opted-out from receiving interest-based advertising.
172Blocked cookiesReturned when the user's browser blocks third-party cookies.
173Encountered trust relationship via NAIThe user has initiated an opt-out process through NAI.
198Requests from this country are blocked by partnerBased on the IP address, the DCS blocks requests from countries where the partner has deliberately limited the traffic.
199Requests 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 IDMessageDescription
200Cannot read traits from profile cache for id: IDReturned when a user profile cannot be read from our internal storage.
201Cannot read device ids from profile cache for customer id: IDReturned when the device ID cannot be retrieved for a Profile Link merge rule.
202Cannot read related customer for device id: IDReturned when the customer ID (UUID) associated to a device ID cannot be retrieved for a Last Authenticated merge rule from our internal storage.
203Cannot read device cluster for id: IDThe linked device IDs from the same device graph cluster cannot be returned for this device ID.
204Could not perform migration since profile read failed for primary deviceIf you receive this error, we may be experiencing scalability issues with our data store ( PCS). Contact your Adobe representative if the problem persists.
205Could not perform migration from ID to ID, because profile read failed for IDIf 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 IDMessageDescription
300Invalid customer id IDThe 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).
301Maximum 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.
302Unauthorized customer id IDReturned 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.
303Blocked customer id IDReturned when the customer ID has been identified as malicious and has been added to a denylist.
304Blocked datasource id IDReturned when the data source ID has been identified as malicious and has been added to a denylist
306Blocked declared device id IDThe device ID has been identified as malicious and has been added to a denylist This can happen when we receive an extreme amount of DCS requests containing this device ID in a short amount of time.
307Blocked profile operation for IDA read/write action has been blocked because an ID has been identified as malicious and has been added to a denylist See error code 306.
309Customer 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 ).

310Customer 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.

311Request 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

312Request 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.

313CMP ID is not present in GCLWhen gdpr=1 and the IAB TC string is generated by a CMP ID that is not present in Audience Manager's cached version of the Global CMP List at the moment of evaluation, the Audience Manager Plug-in for IAB TCF discards the IAB TC string and process the request as usual. The IAB TCF v2.2 ${GDPR} macro is set to 0 and the ${GDPR_CONSENT_XXX} macro is empty.
314CMP ID is marked as deleted in GCLWhen gdpr=1 and the IAB TC string is generated by a CMP that is marked as deleted in our cached version of the Global CMP List, the Audience Manager Plug-in for IAB TCF discards the TC string and processes the request as usual, if the evaluation time is past the deletion time from the Global CMP List. The IAB TCF v2.2 ${GDPR} macro is set to 0 and the ${GDPR_CONSENT_XXX} macro is empty.
315Consent string indicates no consentWhen no consent is provided, the Audience Manager Plug-in for IAB TCF opts the user out of further data collection, or drops the call completely if there is no partner context detected.