An Adobe Target activity uses a new Experience Cloud audience previously created in Adobe Analytics. The activity is live, but according to the activity reporting, no visitors have yet qualified for…

Question

Options

• AAudience Library in People Core Service
• BSegments in Adobe Audience Manager
• CAudiences in Adobe Target
• DAudience Processing Dashboard

• A
  74% (20)
• B
  7% (2)
• C
  4% (1)
• D
  15% (4)

Explanation

Option A is correct because Experience Cloud audiences created in Adobe Analytics are published to the People Core Service (now called Experience Cloud Audiences), and the Audience Library within that service is where you can monitor the initial processing/publishing status - including whether the audience has finished syncing and is ready for use in downstream solutions like Adobe Target. When an Analytics-based audience is newly created, it undergoes a processing pipeline before becoming available, and the Audience Library is the authoritative place to check that readiness status.

Why the distractors are wrong:

• B (Audience Manager): AAM is a separate DMP; Analytics-created Experience Cloud audiences don't route through AAM's Segments interface for status checking unless AAM is explicitly part of the integration.
• C (Adobe Target Audiences): Target will eventually receive the audience, but if no visitors have qualified yet, you can't confirm from Target's side whether the problem is processing delay vs. audience logic - and Target doesn't show the initial processing status.
• D (Audience Processing Dashboard): This is a fabricated distractor; no such named dashboard exists in the Adobe Experience Cloud ecosystem.

Memory tip: Think of the People Core Service / Audience Library as the "staging area" - audiences must pass through it before reaching Target. If something isn't working in Target, check the source (Audience Library) first, not the destination (Target itself).

No community discussion yet for this question.