What are common challenges in implementing Adobe Target on mobile apps? (Select two)

Question

Options

• AHigh latency due to API calls
• BLack of support for custom mboxes
• CSynchronization of offline and online data
• DManaging in-app offer display logic

• A
  12% (3)
• B
  8% (2)
• C
  81% (21)

Explanation

Implementing Adobe Target on mobile apps presents unique challenges around data synchronization (C) and offer display logic (D). Mobile users frequently switch between connected and offline states, making it difficult to keep personalization data consistent - Target must reconcile cached experiences with live server responses when connectivity is restored. Managing in-app offer display logic is also complex because mobile UIs have diverse layouts, lifecycle events, and navigation patterns that make it harder to control when, where, and how offers render compared to a browser DOM.

Why A is wrong: While API latency is a real performance concern, it's not specific to Target on mobile - it's a general web service issue, and Target's SDK provides prefetch capabilities specifically to mitigate this.

Why B is wrong: Adobe Target does support custom mboxes on mobile via the Mobile SDK; this is a supported feature, not a limitation.

Memory tip: Think "COD" - Connectivity and On-screen Display - the two things that make mobile genuinely different from web. Offline/online sync is the network challenge; offer display logic is the rendering challenge. Both are unique to the mobile environment.

No community discussion yet for this question.