Implementing Customer Attributes with Target - mbox3rdPartyID vs. customerId | Community
Skip to main content
K
KMarchewa
Level 3
January 14, 2022
Solved

Implementing Customer Attributes with Target - mbox3rdPartyID vs. customerId

  • January 14, 2022
  • 2 replies
  • 2173 views

Hello,

 

We are looking at implementing the customer attributes feature. I have reviewed the documentation both in the Target section as well as the "Experience Cloud Interface Component" docs.

 

 I understand you upload customer IDs and associated attributes to the platform and that you must send this ID to the platform on the page level after the user logs in. However, based on Adobe's docs (primarily https://experienceleague.adobe.com/docs/target/using/audiences/visitor-profiles/working-with-customer-attributes.html?lang=en and https://experienceleague.adobe.com/docs/target/using/audiences/visitor-profiles/working-with-customer-attributes.html?lang=en) I am unclear on the relationship between the customerID functions from the ECID lbirary and Target's `mbox3rdPartyID`. Specifically, does one: (1) send the ID in the `mbox3rdPartyID`, (2) use `setCustomerID()`of the ECID service, or (3) both?

 

Thanks!

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Gaurav_Singh_02

@kmarchewa You have to only use any one of these 2 approaches :

1. setCustomerID()`of the ECID service: Using the customer ID sync with the Experience Cloud ID service (aka ECID). With a proper ECID and Target implementation, this will ensure Target is linked to the proper customer ID used in Customer Attributes.

2. Send the ID as a `mbox3rdPartyID` in mbox call : Send the customer ID used in the Customer Attributes upload directly to Target as an mbox third party ID. in the following format : 

 

function targetPageParams() { return 'mbox3rdPartyId=******'; }

 

2 replies

G
Adobe Employee
Gaurav_Singh_02Adobe EmployeeAccepted solution
Adobe Employee
January 14, 2022

@kmarchewa You have to only use any one of these 2 approaches :

1. setCustomerID()`of the ECID service: Using the customer ID sync with the Experience Cloud ID service (aka ECID). With a proper ECID and Target implementation, this will ensure Target is linked to the proper customer ID used in Customer Attributes.

2. Send the ID as a `mbox3rdPartyID` in mbox call : Send the customer ID used in the Customer Attributes upload directly to Target as an mbox third party ID. in the following format : 

 

function targetPageParams() { return 'mbox3rdPartyId=******'; }

 

    M
    mattg27197046
    January 24, 2022

    @gaurav_singh_02 when using mbox3rdPartyId do you know what to put as alias when setting up a customer atribute. 

     

    for setCustomerID approach is is the key used in the Visitor ID code, but that's not relevant for mbox3rdPartyId approach?

    Thanks!

    Matt

    kchaitanya
    kchaitanya
    Level 3
    January 24, 2022

    You are right Matt, the alias is only relevant for setCustomerID() approach. For mbox3rdPartyId the code that Gaurav shared above is sufficient. No alias required. 

     

    Regards,

    Chaitanya

    Brian_Hawkins_MiaProva
    Brian_Hawkins_MiaProva
    Level 3
    January 17, 2022

    The mbox3rdPartyId is the approach favored by most of the organizations I work with, given the APIs available to push/pull data for it.  Additionally, that approach creates a dependency on the visitor service, which may not be available if you do server-side testing and don't move the service server-side.  

     

    mbox3rdPartyId also supports real-time cross-device coordination.  I do not know if the ECID supports it at the moment.  

      Terms & ConditionsAccessibility statement

      Loading footer...