What action can be performed using browser debugging tools like Experience Cloud Debugger?

Question

Options

• AValidate audience membership
• BModify traffic allocation dynamically
• CAdd custom metrics to a report
• DCreate new Target activities

• A
  83% (30)
• B
  3% (1)
• C
  11% (4)
• D
  3% (1)

Explanation

Validating audience membership (A) is the core use case for browser debugging tools like Adobe Experience Cloud Debugger - they let you inspect which audiences a current visitor qualifies for, what mbox requests are firing, and whether Target activities are being triggered correctly for that session.

B is wrong because traffic allocation (the percentage split between control and variant) is a static configuration set inside Target's activity editor, not something a browser tool can change dynamically at runtime.

C is wrong because custom metrics are defined within the Target activity setup or through Analytics; a debugger tool reads and validates data, it doesn't write to reporting configurations.

D is wrong because creating activities is a server-side action performed in the Target UI - the browser debugger is a read-only diagnostic tool that observes what's happening, not an authoring interface.

Memory tip: Think of the debugger as a validator, not a creator. It answers "Is this visitor in the right audience?" - everything else (allocations, metrics, activities) lives in the Target admin interface where changes are made, not the browser.

No community discussion yet for this question.