A client notices that JSON Offers are not being applied after adobe.target.applyOffer() is called. The Adobe Experience Cloud Debugger confirms the client is qualified for the Activity. How should…

Question

Options

• AFilter the actions array passed to adobe.target.getOffer() for all actions that contain a setContent
• BFilter the actions array provided to adobe.target.getOffer() for all actions that have a setJson
• CUse the adobe.target.event.REQUEST_SUCCEEDED event to read the JSON Offer from the
• DUse a Data Provider to read the JSON Offer passed as an attribute to the provider method.

• A
  17% (7)
• B
  71% (29)
• C
  7% (3)
• D
  5% (2)

Explanation

When adobe.target.getOffer() succeeds, its callback receives an actions array - each element representing a type of operation Target wants to perform. For JSON Offers specifically, the relevant action type is setJson, so you must filter that array for objects whose type equals setJson to extract the JSON payload programmatically; applyOffer() won't auto-render JSON the way it renders HTML, which is why the offer appears "not applied."

Option A is wrong because setContent is the action type for HTML offers (it injects markup into the DOM) - filtering for it on a JSON Offer response returns nothing useful.

Option C is wrong because REQUEST_SUCCEEDED is a lifecycle event useful for observability, not the prescribed mechanism for reading offer content from the actions payload.

Option D is wrong because Data Providers flow inward - they supply third-party data to Target before a request fires (e.g., for audience qualification), not outward to read offer responses.

Memory tip: Match the offer type to the action type - HTML offer → setContent, JSON offer → setJson. If you remember that pairing, you'll never confuse A and B on the exam.

No community discussion yet for this question.