A Target practitioner observes that an active experience is not displaying for certain audience segments. Upon checking the Experience Cloud Debugger, they notice the targeting rules are configured…

Question

Options

• AVerify that the experience is active and approved
• BRecreate the audience and relaunch the activity
• CUpdate the reporting source in the activity settings
• DIncrease the traffic allocation for the experience

• A
  80% (48)
• B
  5% (3)
• C
  2% (1)
• D
  13% (8)

Explanation

Verifying that the experience is active and approved (A) is the correct next step because an experience that hasn't been approved or has been paused will not render for any audience segment, regardless of how correctly the targeting rules are configured - the activity lifecycle state gates delivery before targeting logic is even evaluated.

Why the distractors are wrong:

• B - Recreating the audience is unnecessary busywork; the debugger already confirmed the targeting rules are correct, so the audience definition isn't the issue.
• C - The reporting source (Analytics vs. Target) affects data collection, not whether an experience is delivered to a visitor.
• D - Traffic allocation controls the percentage of qualifying visitors who enter the activity; it doesn't prevent an experience from showing to already-qualified segments.

Memory tip: Think of activity approval as the "power switch" - targeting rules are the wiring, but if the switch is off, nothing flows. Always check status/approval before digging into configuration details.

No community discussion yet for this question.