A client reports that activities are not rendering on their newly launched mobile app. Debugging reveals that at.js is working as expected. What should the architect investigate?

Question

Options

• AVerify mobile SDK configuration
• BTest API request and response cycles
• CEnsure profile scripts are mobile-compatible
• DCheck server-side delivery configurations

• A
  83% (40)
• B
  4% (2)
• C
  10% (5)
• D
  2% (1)

Explanation

Option A is correct because at.js is Adobe Target's web JavaScript library - it has no bearing on mobile app activity delivery. Mobile apps require the Adobe Target Mobile SDK (or equivalent), and if it's misconfigured or missing, activities simply won't render, regardless of how well at.js performs on the web side. Option B (API cycles) is a valid deeper troubleshooting step but skips the foundational question of whether the mobile SDK is even set up correctly. Option C (profile scripts) governs audience targeting and segmentation, not activity rendering itself. Option D (server-side delivery) is a separate implementation pattern unrelated to standard mobile SDK delivery.

Memory tip: Think "at.js = web only." Any time you see a mobile app problem paired with at.js working fine, that's a deliberate misdirection - the real gap is always the mobile SDK, not the web library.

No community discussion yet for this question.