Which component is critical for implementing Adobe Target in native mobile apps?

Question

Options

• ATarget API
• BAEP Mobile SDK
• CContent Fragments
• DExperience Cloud ID Service

• A
  15% (5)
• B
  76% (26)
• C
  6% (2)
• D
  3% (1)

Explanation

AEP Mobile SDK (B) is the critical component because it provides the native mobile libraries that enable Adobe Target to deliver personalized experiences on iOS and Android - without it, there's no way to integrate Target's decisioning engine into a mobile app.

Why the distractors are wrong:

• A. Target API - While Target has APIs, there's no standalone "Target API" product for native mobile; API calls alone lack the SDK's lifecycle management, event handling, and Adobe Experience Platform integration.
• C. Content Fragments - These are an Adobe Experience Manager (AEM) authoring concept for headless content delivery, unrelated to Target's mobile implementation layer.
• D. Experience Cloud ID Service - The ECID Service is part of the AEP Mobile SDK ecosystem and handles identity, but it's a dependency/component within the SDK, not the standalone implementation mechanism.

Memory tip: Think "mobile needs a mobile SDK" - Adobe baked Target support directly into the AEP (Adobe Experience Platform) Mobile SDK so developers install one SDK to get access to the entire Experience Cloud suite, including Target, on native platforms.

No community discussion yet for this question.