A Healthcare company wants to develop personalized experiences based on the age and location of the visitor. The Optimization Lead wants to use JSON to pass these parameters into Adobe Target. This…

Question

Options

• Aadobe.target.getOffers()
• BtargetPageParams()
• Cadobe.target.triggerView()
• DregisterExtension

• A
  18% (5)
• B
  71% (20)
• C
  7% (2)
• D
  4% (1)

Explanation

targetPageParams() is the designated function for passing additional parameters (like age and location) to the auto-created global mbox before it fires - it returns a JSON object that Adobe Target automatically picks up and includes in the request, making it the perfect fit for this use case.

Why the distractors are wrong:

• A. adobe.target.getOffers() - used to manually fetch offers from Target without rendering them; it's for custom, developer-controlled requests, not the global mbox.
• C. adobe.target.triggerView() - used in Single Page Applications (SPAs) to notify Target when a view changes, unrelated to passing global mbox parameters.
• D. registerExtension - a legacy Launch/DTM API for registering extensions in the tag management layer, not a Target parameter-passing function.

Memory tip: Think of targetPageParams() as the "page passport" - it's called before the global mbox fires and hands Target everything it needs to know about the current visitor (age, location, etc.) right at the door. The "Params" in the name is your clue it's for parameter passing.

No community discussion yet for this question.