An Adobe Target architect is designing an implementation that requires the use of Analytics for Target (A4T). Which script must be loaded first?

Question

Options

• Aat.js
• BappMeasurement.js
• CVisitorAPI.js
• Dmbox.js

• A
  5% (1)
• B
  15% (3)
• C
  70% (14)
• D
  10% (2)

Explanation

VisitorAPI.js must load first because it provides the Experience Cloud Visitor ID (ECID/MID) service, which generates the shared visitor identifier that both Adobe Target and Adobe Analytics use to stitch data together - without it initialized first, neither library can properly identify the visitor for cross-solution tracking.

Why the distractors are wrong:

• A. at.js - Adobe Target's main library must load after VisitorAPI.js so it can access the visitor ID at initialization time.
• B. appMeasurement.js - Adobe Analytics' library also depends on VisitorAPI.js being available; it loads second in the required sequence.
• D. mbox.js - The legacy predecessor to at.js; it's deprecated and not the correct library for modern A4T implementations regardless.

Memory tip: Think of it as "ID first, then measure, then target" - VisitorAPI → AppMeasurement → at.js (VAA), because you can't measure or target what you haven't identified.

No community discussion yet for this question.