Which API method is used for server-side delivery in Adobe Target?

Question

Options

• AgetOffers
• BexecuteRequest
• CapplyOffer
• DpostRecommendation

• A
  76% (37)
• B
  4% (2)
• C
  12% (6)
• D
  8% (4)

Explanation

getOffers is the correct method for server-side delivery in Adobe Target because it is part of the Node.js SDK and server-side APIs specifically designed to fetch personalized offers from the Target delivery API without requiring a browser - making it the primary mechanism for server-rendered pages and backend integrations.

applyOffer (C) is a client-side method that manipulates the DOM to render a fetched offer in the browser, so it is the wrong layer entirely. executeRequest (B) is not a standard Adobe Target API method name - it is a distractor that sounds plausible but does not exist in the official SDK. postRecommendation (D) is fabricated; Adobe Target Recommendations are delivered through the same offers pipeline, not a separate POST method.

Memory tip: Think "Get offers on the Server" - the G in getOffers and S in server both come before their counterparts (applyOffer applies client-side, after the offer is already fetched), reinforcing that getOffers is the fetch/server step.

No community discussion yet for this question.