A client would like to create an Activity that shows a promotional message to visitors on the checkout success page of their site when the total value of the visitor's order is over $100. The…

Question

Options

• AAdobe Experience Cloud Device Co-Op Audiences
• BAudience Library Audiences (People Core Service)
• CAdobe Analytics Audiences
• DAdobe Target Audiences

• A
  4% (2)
• B
  5% (3)
• C
  11% (6)
• D
  80% (45)

Explanation

Adobe Target Audiences (Option D) is correct because this scenario requires real-time audience evaluation using data passed in the same mbox call - specifically, the order total submitted as an mbox parameter on the checkout success page. Only native Target Audiences can evaluate mbox parameters (like orderTotal > 100) on-the-fly within that single request, enabling immediate experience delivery without waiting for data to process elsewhere.

Why the distractors fail:

• A (Device Co-Op): Designed for cross-device identity resolution, not real-time mbox parameter evaluation - wrong tool entirely.
• B (Audience Library / People Core Service): These are pre-built, shared segments from Experience Cloud that rely on previously processed profile data, not same-request mbox parameters.
• C (Adobe Analytics Audiences): Analytics data has inherent processing latency; these segments cannot be evaluated in real time from the current mbox request.

Memory tip: The phrase "same Target request (mbox)" is your signal for Adobe Target Audiences - any time audience qualification must happen in the moment using data from the current page call (like order values, cart contents, or form inputs), only native Target Audiences can do it. If data must travel through another system first (Analytics, Audience Manager), there's a delay - which rules out all other options here.

No community discussion yet for this question.