A client wishes to increase content velocity and reuse by utilizing content created in Adobe Experience Manager (AEM) within Adobe Target Automated Personalization activities. What should the…

Question

Options

• AUse AEM Content Fragments as Adobe Target Offers.
• BUse the Adobe Target createOffer API to pass JSON Offers to Adobe Target.
• CUse AEM Experience Fragments as Adobe Target Offers.
• DEmbed Experience Manager HTML directly into Target offers.

• A
  13% (5)
• B
  5% (2)
• C
  79% (31)
• D
  3% (1)

Explanation

Experience Fragments are AEM's purpose-built vehicle for cross-channel content reuse, and Adobe provides a native integration that lets authors export them directly to Adobe Target as HTML or JSON offers - enabling content teams to build once in AEM and activate in Target's Automated Personalization without duplication.

Why the distractors fail:

• A (Content Fragments): Content Fragments are structured, headless data blobs with no presentation layer and no native Target offer export. They're for content modeling, not channel delivery.
• B (createOffer API): While technically possible, this bypasses AEM's reuse model entirely - a developer must manually construct and push offers, which increases maintenance burden rather than improving content velocity.
• D (Embed AEM HTML directly): There is no supported mechanism for embedding live AEM HTML into Target; it's a fragile, unscalable workaround that breaks content governance.

Memory tip: Think of the word "Experience" as your clue - an Experience Fragment is designed to deliver a complete, renderable experience across channels (web, email, Target). A Content Fragment is raw content data with no render - it has no channel awareness.

No community discussion yet for this question.