Customer Attributes for Target with the Web SDK | Adobe Higher Education
Skip to main content
K
KMarchewa
Level 3
March 8, 2023
Beantwortet

Customer Attributes for Target with the Web SDK

  • March 8, 2023
  • 2 Antworten
  • 3313 Ansichten

Hello,

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?

 

Thanks.

    Dieses Thema wurde für Antworten geschlossen.
    Beste Antwort von alexbishop

    You can continue to use Customer Attributes with Web SDK data collection, you just need to ensure two things:
    i) You pass your customerID as part of the XDM identityMap object, more details here
    ii) You configure your datastream with reference to that same Third Party ID, more details here

    2 Antworten

    nnakirikanti
    Community Advisor
    nnakirikantiCommunity Advisor
    Community Advisor
    March 8, 2023

    @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/adobe-target-connection.html?lang=en) 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.

      K
      KMarchewaAutor
      Level 3
      March 8, 2023

      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-aep-web-sdk/ba-p/423234

       

      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?

        nnakirikanti
        Community Advisor
        nnakirikantiCommunity Advisor
        Community Advisor
        March 8, 2023

        @kmarchewa Interesting, let me look into some other documents.

          alexbishop
          Adobe Employee
          alexbishopAdobe EmployeeAntwort
          Adobe Employee
          March 9, 2023

          You can continue to use Customer Attributes with Web SDK data collection, you just need to ensure two things:
          i) You pass your customerID as part of the XDM identityMap object, more details here
          ii) You configure your datastream with reference to that same Third Party ID, more details here

            nnakirikanti
            Community Advisor
            nnakirikantiCommunity Advisor
            Community Advisor
            March 9, 2023

            @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: Thirdpartyid https://experienceleague.adobe.com/docs/target/using/audiences/visitor-profiles/3rd-party-id.html?lang=en

            Reference Customer Attributes: https://experienceleague.adobe.com/docs/id-service/using/reference/authenticated-state.html?lang=en#section-68ad4065dfaa437d9070832d6e2bf85c

             

              Allgemeine NutzungsbedingungenAccessibility statement

              Loading footer...