Adobe Target

thomashendrickx · 4/7/22

Hi,

One of our clients is updating their client database internally which will result in a set of clients ( around a 100k and possibly in the future more) getting a new Id. Within this migration process we would like to include a step which will do an equivalent migration in target.

To do this, we are looking for a way to bulk update the mbox3rdPartyID of a bunch of profiles. When researching the admin api of target ( https://developers.adobetarget.com/api/#structure-of-a-target-profile ) we see that there is a bulk update api call, which we today already use in a different usecase, but do not see a way how to use this to change the mbox3rdPartyID.

What is the best approach to tackle this issue?

Our current fallback option, in case of no solution, is to delete all 100k+ profiles and rebuild them from scratch, losing all data until now.

Kr,

Thomas

kchaitanya · 4/7/22

Hi @thomashendrickx ,

Don't think there is an API option for changing mbox3rdPartyId or merging 2 mbox3rdPartyIds directly. One option you can look at is to start passing the new mbox3rdPartyId on the browsers of existing users who had previously logged in on those browsers with old ID. Target merges the profile at backend and the profile attributes will be linked to the PCID as well. When users start signing in with the new ID the profile mergers with the new mbox3rdPartyId and can be used for cross device targeting.

This of course can't resolve for all the 100k clients as some might begin to login with new IDs on new browsers and the history will be lost then. But better than losing all the data!

Reference document: https://experienceleague.adobe.com/docs/target/using/audiences/visitor-profiles/3rd-party-id.html?la...

View solution in original post

kchaitanya · 4/7/22

Hi @thomashendrickx ,

Don't think there is an API option for changing mbox3rdPartyId or merging 2 mbox3rdPartyIds directly. One option you can look at is to start passing the new mbox3rdPartyId on the browsers of existing users who had previously logged in on those browsers with old ID. Target merges the profile at backend and the profile attributes will be linked to the PCID as well. When users start signing in with the new ID the profile mergers with the new mbox3rdPartyId and can be used for cross device targeting.

This of course can't resolve for all the 100k clients as some might begin to login with new IDs on new browsers and the history will be lost then. But better than losing all the data!

Reference document: https://experienceleague.adobe.com/docs/target/using/audiences/visitor-profiles/3rd-party-id.html?la...