We are currently leveraging Customer Attributes for Target. We set the ID via the ECID services (visitor.js). We are looking at migrating to the Web SDK (alloy.js).
I understand the concept of Identity Maps using the SDK. However, I want to ensure that Customer Attributes will continue to function as expected for Target. For example, say I have a Customer Attributes setup with an integration code of "customUserId". I am currently using the ECID Extension in Launch to set this ID using the "Set Customer IDs" Action and "customUserId" integration code. If I create a custom namespace matching the integration code from Customer Attributes ("customUserId") and, using the SDK, set the ID under the "customUserId" namespace of the indentityMap, will the Customer Attributes data continue to be available in Target? That is, is there a more or less direct migration path from the "Integration Codes" in the ECID extension to Identity Maps in the SDK/AEP?
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
@KMarchewa As per my knowledge no customer attributes support with websdk, with AEP you should inject the same data to profile and use the data for segmentation.
There is only edge Segmentation where profile data can't be shared only segments are shared across.There is beta
version of Adobe target V2 destination(https://experienceleague.adobe.com/docs/experience-platform/destinations/catalog/personalization/ado...) which says profile data can be shared, check with Adobe to enable for you to see how it works.
Let me know if you need further details.
Thanks for the response. This article seems to indicate that one can directly migrate from the ECID library to the SDK and that data ingestion would continue to function: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-platform-blogs/ecid-migration-with...
Is this not the case? We don't have any AEP licensing (aside from the features available to all AEC customers). Is there no way to ingest offline data (as is possible with at.js, visitor.js and Customer Attributes) with the Web SDK if we don't have additional AEP licenses?
@alexbishop thirdpartyid and customer attributes implementations are different.
targeting without authentication consideration then your recommendation works, if authentication comes into picture then it wont work.
Reference Customer Attributes: https://experienceleague.adobe.com/docs/id-service/using/reference/authenticated-state.html?lang=en#...