A client would like to use the Category Affinity feature of Adobe Target. Which Target request (mbox) parameter should be used to record category information?

Question

Options

• Aentity.categoryId
• Buser.categoryId
• Cprofile.categoryId
• Duser.categoryAffinities

• A
  9% (4)
• B
  74% (35)
• C
  13% (6)
• D
  4% (2)

Explanation

Option B (user.categoryId) is correct because Adobe Target's Category Affinity feature is specifically designed to read this mbox parameter to record which category a visitor is currently viewing, then automatically builds and scores affinity profiles over time based on those visits.

• A (entity.categoryId) is wrong - the entity. prefix belongs to the Recommendations feature, used to describe product/content attributes (like which category an item belongs to), not to track user browsing behavior for affinity.
• C (profile.categoryId) is wrong - while profile. parameters store persistent user data, profile.categoryId is not a recognized Adobe Target parameter; using an arbitrary profile parameter won't trigger the Category Affinity engine.
• D (user.categoryAffinities) is wrong - this is an output, not an input. Adobe Target writes the calculated affinity scores to user.categoryAffinities after processing; you read it for targeting, you don't pass it in.

Memory tip: Think of it as a two-step flow - you send user.categoryId (what the user is looking at now), and Target returns user.categoryAffinities (what the user cares about over time). Input → user.categoryId; Output → user.categoryAffinities.

No community discussion yet for this question.