AD0-E409 · Question #117
A client has users that authenticate on their site on every visit, but they also tend to utilize the site on multiple different devices, including laptops, mobile, and tablets at different times of…
The correct answer is D. Populate the mbox3rdPartyId Adobe Target request (mbox) parameter with the user's ID. E. Use the Adobe Experience Cloud Visitor API method setCustomerIDs with the user's ID and. Options D and E are correct because Adobe Target has two dedicated mechanisms for cross-device identity stitching on authenticated users: mbox3rdPartyId (D) is a reserved Target parameter specifically designed to link visitor profiles by a known user ID across sessions and…
Question
A client has users that authenticate on their site on every visit, but they also tend to utilize the site on multiple different devices, including laptops, mobile, and tablets at different times of the day. The client wants to ensure that a user has a consistent experience of their site across each of their devices, including showing the same user the same experience from an Adobe Target activity, regardless of what device they have authenticated on. Which two options will ensure that a user is delivered the same experience across all of their authenticated devices? (Choose two.)
Options
- APopulate a custom Adobe Target request (mbox) parameter with the user's email address.
- BUtilize Customer Attributes in the Adobe Experience Cloud.
- CUse Adobe Experience Cloud Triggers to know when a specific user is visiting the site.
- DPopulate the mbox3rdPartyId Adobe Target request (mbox) parameter with the user's ID.
- EUse the Adobe Experience Cloud Visitor API method setCustomerIDs with the user's ID and
How the community answered
(21 responses)- A14% (3)
- B5% (1)
- C5% (1)
- D76% (16)
Explanation
Options D and E are correct because Adobe Target has two dedicated mechanisms for cross-device identity stitching on authenticated users: mbox3rdPartyId (D) is a reserved Target parameter specifically designed to link visitor profiles by a known user ID across sessions and devices, while setCustomerIDs (E) from the Experience Cloud Visitor API registers the same known ID at the ECID (Identity Service) layer, enabling profile synchronization across all Experience Cloud solutions including Target.
Why the distractors fail:
- A - Passing email as a custom mbox parameter makes it available for targeting rules, but it does NOT trigger Adobe's profile-linking mechanism; only the reserved
mbox3rdPartyIdfield does that. - B - Customer Attributes enrich user profiles with CRM/offline data but don't solve the cross-device identity problem; they assume a profile already exists to attach to.
- C - Experience Cloud Triggers detect behavioral signals (e.g., cart abandonment) to fire downstream actions like emails; they have no role in ensuring consistent Target activity delivery.
Memory tip: Think of D and E as two layers of the same lock - mbox3rdPartyId tells Target "this is a known user," while setCustomerIDs tells the entire Experience Cloud the same thing. You need both because they operate at different levels of the Adobe stack.
Topics
Community Discussion
No community discussion yet for this question.