The reporting team has been struggling to segment internal development and stage environment traffic from the live website data in Adobe Target reporting. This is impacting their ability to evaluate…

Question

Options

• ACustom Global Target request (mbox)
• BHosts
• CProperties
• DCustom Response Tokens

• A
  15% (6)
• B
  75% (30)
• C
  8% (3)
• D
  3% (1)

Explanation

Hosts in Adobe Target is the feature that allows you to define and group environments (production, staging, development) so that traffic from each can be separated in reporting. By configuring host groups and assigning environments correctly, the architect ensures that internal/staging traffic is excluded or isolated from live production data, preserving the integrity of activity reporting and statistical significance calculations.

Why the distractors are wrong:

• A. Custom Global mbox - This controls the name of the global request that fires on page load; it has no bearing on filtering traffic by environment.
• C. Properties - Properties are used for enterprise governance and permissions (workspace/channel segmentation), not for distinguishing environments.
• D. Custom Response Tokens - These pass data back to the page (e.g., activity name, experience ID) for analytics integration; they don't control which environments are included in reporting.

Memory tip: Think "Hosts = Habitats" - just as animals are separated by habitat, Hosts separates your environments (dev, stage, prod) so each lives in its own reporting bucket. If your data is "contaminated" by non-production traffic, Hosts is where you clean house.

No community discussion yet for this question.