What are key components for implementing Adobe Target in a mobile app? (Select two)

Question

Options

• AExperience Cloud SDK
• BJavaScript Tag Manager
• CTarget Global mbox
• DMobile-specific Profile Scripts

• A
  81% (26)
• B
  6% (2)
• D
  13% (4)

Explanation

Implementing Adobe Target in a mobile app requires the Experience Cloud SDK (A), which is the native library that enables mobile apps to communicate with Adobe Target and other Experience Cloud services - there is no browser-based equivalent for native mobile apps. The Target Global mbox (C) is the core request mechanism that the SDK uses to fetch personalized activities and experiences from Target servers, making it a foundational implementation component.

B (JavaScript Tag Manager) is wrong because tag managers operate in browser environments via JavaScript injection; native mobile apps use SDK integrations, not JS-based tag managers. D (Mobile-specific Profile Scripts) is a distractor because profile scripts are server-side enhancements for refining audience targeting - they're not a required component for the initial implementation itself.

Memory tip: Think "SDK + mbox = mobile implementation basics." The SDK is your connection layer, the global mbox is your request mechanism - together they form the minimum viable setup. Tag managers and profile scripts belong to web environments and advanced personalization, respectively.

No community discussion yet for this question.