A retailer wants to use Adobe Target to deliver personalized offers in their mobile app. What is the first step they need to take?

Question

Options

• AEnable pre-hiding in the app.
• BIntegrate AEP Mobile SDK.
• CUse HTML Offers for mobile targeting.
• DCreate an audience in A4T.

• A
  6% (3)
• B
  70% (35)
• C
  20% (10)
• D
  4% (2)

Explanation

Integrating the AEP (Adobe Experience Platform) Mobile SDK is the prerequisite foundation - without it, the mobile app has no way to communicate with Adobe Target, so no personalization can occur at all. Option A (pre-hiding) is a technique to prevent content flicker during experience delivery, but it's a refinement step that comes after the SDK is in place. Option C is wrong because HTML Offers are a web-based format; mobile apps use JSON Offers or native rendering, not HTML. Option D is a red herring - A4T (Analytics for Target) is an analytics integration for reporting, not an audience-creation tool, and audiences are built in the Target or AEP interface regardless.

Memory tip: Think of the SDK as the "door" - you must open the door before you can do anything else inside the house. All other options (hiding content, choosing offer types, setting up analytics) only matter once the door is open.

No community discussion yet for this question.