A client has a multi-tenant Adobe Target setup, where each business unit has their Workspace and properties defined in Adobe Target. What needs to be configured on a page before an activity can be…

Question

Options

• ATarget request (mbox) at_property parameter needs to be populated at a page level.
• BTarget request (mbox) user.sessionId parameter needs to be populated at a page level.
• CTarget request (mbox) profile parameter needs to be populated at a page level.
• DTarget request (mbox) custom parameter needs to be populated with Activity ID.

• A
  81% (22)
• B
  11% (3)
• C
  4% (1)
• D
  4% (1)

Explanation

Option A is correct because Adobe Target uses the at_property parameter as a property token that identifies which Workspace a page belongs to. In a multi-tenant setup, each business unit's Workspace has a unique property token, and this token must be passed in the Target mbox request at the page level so Target knows which Workspace's activities are eligible to fire on that page - without it, Target cannot associate the page with the correct business unit.

Option B is wrong because user.sessionId is a visitor-identification parameter used for session continuity, not for workspace/property assignment - it has no role in determining which business unit's activities apply.

Option C is wrong because profile parameters (profile.*) store visitor-level attributes used in audience targeting rules, not for scoping pages to a specific Workspace.

Option D is wrong because activities are matched to pages through the property token and audience/URL rules, not by manually passing an Activity ID as a custom parameter - that's not how Target's architecture works.

Memory tip: Think of at_property as a building key card - each business unit has its own floor (Workspace), and the page must carry the right key (at_property token) to unlock that floor's activities.

No community discussion yet for this question.