What are common reasons for "Target Request and Response" errors? (Select two)

Question

Options

• AMalformed mbox names
• BMismatched Experience Cloud IDs
• COutdated at.js version
• DIncorrect audience mapping

• A
  78% (18)
• B
  13% (3)
• D
  9% (2)

Explanation

Malformed mbox names (A) cause Target to reject requests outright - if an mbox name contains invalid characters, spaces, or exceeds length limits, the request cannot be processed and triggers a request/response error. Outdated at.js (C) introduces compatibility issues with the Target delivery API, leading to failed or malformed HTTP exchanges that surface as request/response errors.

B (Mismatched Experience Cloud IDs) is incorrect because ID mismatches typically produce visitor identity or profile-merge issues, not request/response errors at the network level. D (Incorrect audience mapping) is a targeting/configuration concern - activities may not deliver to the right users, but the request and response themselves succeed without error.

Memory tip: Think "syntax and software" - request/response errors trace back to how the call is constructed (malformed mbox name = bad syntax) or what's making the call (outdated at.js = bad software). Identity and audience problems happen after a successful request, so they belong to a different error category.

No community discussion yet for this question.