nerdexam
Adobe

AD0-E409 · Question #82

A client has recently implemented Adobe Target for an Android application that uses AEP Mobile SDK and passes a custom visitor ID from a CRM system. Which API method can be used to retrieve the custom

The correct answer is C. getThirdPartyId(). getThirdPartyId() is correct because Adobe Target uses the term "third-party ID" specifically to refer to custom visitor identifiers passed in from external systems like a CRM - it is the designated API for retrieving an ID that the client, not Adobe, defines and controls. Why th

Implementation and Integration

Question

A client has recently implemented Adobe Target for an Android application that uses AEP Mobile SDK and passes a custom visitor ID from a CRM system. Which API method can be used to retrieve the custom visitor ID from Adobe Target?

Options

  • AgetTntId()
  • BVisitor.getInstance(`YOUR-UNIQUE-ORG-ID@AdobeOrg').getMarketingCloudVisitorID();
  • CgetThirdPartyId()
  • DgetCustomId()

How the community answered

(41 responses)
  • A
    15% (6)
  • B
    7% (3)
  • C
    73% (30)
  • D
    5% (2)

Explanation

getThirdPartyId() is correct because Adobe Target uses the term "third-party ID" specifically to refer to custom visitor identifiers passed in from external systems like a CRM - it is the designated API for retrieving an ID that the client, not Adobe, defines and controls.

Why the distractors are wrong:

  • A. getTntId() - retrieves the TNT ID, which is Adobe Target's own internally generated visitor identifier, not a custom CRM value.
  • B. Visitor.getInstance(...).getMarketingCloudVisitorID() - retrieves the Adobe Experience Cloud ID (ECID), a cross-solution Adobe identity, which is unrelated to a client-supplied CRM ID.
  • D. getCustomId() - this method does not exist in the Adobe Target or AEP Mobile SDK API; it is a plausible-sounding distractor.

Memory tip: Think "third party = your party." When you (the client) bring an ID from your CRM into Adobe Target, it's treated as a "third-party" ID because it originates outside of Adobe's ecosystem - so the API that handles it is getThirdPartyId().

Topics

#AEP Mobile SDK#custom visitor ID#third-party ID#CRM integration

Community Discussion

No community discussion yet for this question.

Full AD0-E409 Practice