AD0-E408 · Question #91
Which syntax is used for Geo location variables that are used as tokens in Adobe Target activities?
The correct answer is A. ${profile.geolocation.country}. Option A (${profile.geolocation.country}) is correct because Adobe Target uses the ${} token syntax to interpolate dynamic variables into activity content, and geo location data is accessed via the profile.geolocation namespace. Options B and C are wrong because bare…
Question
Which syntax is used for Geo location variables that are used as tokens in Adobe Target activities?
Options
- A${profile.geolocation.country}
- Bprofile.geolocation.country
- C[profile.geolocation.country]
- D${geo.location.country}
How the community answered
(31 responses)- A71% (22)
- B6% (2)
- C3% (1)
- D19% (6)
Explanation
Option A (${profile.geolocation.country}) is correct because Adobe Target uses the ${} token syntax to interpolate dynamic variables into activity content, and geo location data is accessed via the profile.geolocation namespace. Options B and C are wrong because bare dot-notation (profile.geolocation.country) and bracket-notation ([profile.geolocation.country]) are not valid Adobe Target token formats - they won't be evaluated or replaced at runtime. Option D (${geo.location.country}) uses the correct wrapper syntax but the wrong namespace path; Adobe Target exposes these values under profile.geolocation, not geo.location.
Memory tip: Think of ${} as a "dollar sign = substitution" rule - Adobe Target tokens always wrap the variable path in ${...}, just like template literals in JavaScript. If you remember that the namespace mirrors the UI label ("profile → geolocation → country"), you can reconstruct the correct token without memorizing it.
Topics
Community Discussion
No community discussion yet for this question.