When specifying a server-side implementation of Adobe Target, which ID will be generated if not explicitly defined?

Question

Options

• AaamUUID
• BtntId
• CthirdPartyId
• DindexId

• A
  17% (10)
• B
  72% (42)
• C
  3% (2)
• D
  7% (4)

Explanation

When a server-side Adobe Target implementation makes a delivery API request without specifying a visitor ID, Target automatically generates a tntId - a unique identifier that follows the format id.sessionId and is used to track the visitor across interactions. This is Target's native visitor identifier, created and owned by the Target service itself.

Why the distractors are wrong:

• A (aamUUID): This is Adobe Audience Manager's identifier, not generated by Target - it requires AAM integration and is passed in, not auto-created by Target.
• C (thirdPartyId): By definition, this is an ID you supply (e.g., a CRM or loyalty ID); Target never auto-generates it.
• D (indexId): Not a real Adobe Target identifier - this is a distractor with no role in the Target ID ecosystem.

Memory tip: Think "tnt = Target's Native Tracker." If you don't bring your own ID (thirdPartyId) or a partner's ID (aamUUID), Target lights the fuse and generates a tntId for you automatically.

No community discussion yet for this question.