A client has a requirement to promote a discount offer to reorder the last purchased product by the user. The recommendation is to use Adobe Target HTML Offers with Dynamic Data. Last product…

Question

Options

• A${campaign.lastProductPurchased}
• B${profile.lastProductPurchased}
• C${user.lastProductPurchased encode="escape"}
• D${context.lastProductPurchased}

• A
  4% (1)
• B
  79% (22)
• C
  14% (4)
• D
  4% (1)

Explanation

In Adobe Target HTML Offers, dynamic tokens must use a namespace that matches how the data was passed into Target. Since the question explicitly states the data is passed as a profile attribute, the correct token syntax is ${profile.lastProductPurchased} - the profile. namespace maps directly to profile attributes in Target's token replacement engine.

Why the distractors are wrong:

• A (campaign.) is not a valid Adobe Target token namespace - it doesn't exist in the Target token syntax.
• C (user.) is the incorrect namespace (there is no user. namespace in Target offers), and encode="escape" is not valid Adobe Target syntax - that style of attribute encoding belongs to other templating languages.
• D (context.) is reserved for contextual/environmental data (device type, browser, geo), not profile attributes.

Memory tip: Match the namespace to the method of data delivery - profile attribute → profile., mbox/request parameter → mbox., entity attribute → entity.. If you remember this mapping, the question answers itself.

No community discussion yet for this question.