Skip to main content
Michael_Soprano
Michael_Soprano
Level 10
July 29, 2026
Solved

Adobe Target destination

  • July 29, 2026
  • 3 replies
  • 69 views

I got the case like this: 

  1. Would have multiple identities for the logged user in my AEP implementation - however its easily done using IdentityMap. I would have multiple business entities
  2. However in AT there can be only one Identity - Target Third Party ID Namespace (so Target Profile can recognize only one Identity from IdentityMap
  3. How the user recognition works? AEP connects with AT on Edge so I assume its based on the IdentityMap not Target Third Party ID Namespace? 

Did you have the case like that? 

    Best answer by Gokul_Agiwal

    Hi ​@Michael_Soprano  - Interesting discussion - Adding points from my understanding 

     

    In an AEP + Adobe Target integration, identity resolution and profile stitching primarily happen within AEP Identity Service. Multiple identities such as CRM ID, Loyalty ID, Account ID, Email, and ECID can coexist in the identityMap and be stitched together into a unified profile through the identity graph.  

     

    More Reference - 

     

    When Target is integrated through Web SDK and Edge Network, Target can leverage profile and audience information that has already been resolved by AEP. The Edge Network acts as the bridge between AEP and Target, allowing audiences and profile context to be available for personalization. 

     

    While Adobe Target supports only a single namespace as the Target Third Party ID (mbox3rdPartyId), that limitation applies to Target's native profile identifier. It does not prevent AEP from maintaining and stitching multiple identities behind the scenes through the identity graph.

     

    Therefore, in a Web SDK + Edge implementation, audience qualification is driven by AEP's identity resolution capabilities, whereas the Target Third Party ID remains a Target-specific profile identifier used for Target profile recognition. This is one of the key advantages of the Edge-based architecture, where identity stitching and audience evaluation are handled by AEP, and Target consumes that resolved context for personalization.

     

    3 replies

    kalarav.vasavada
    Level 2
    July 29, 2026

    On the AEP Web SDK path, edge stitching happens on the full IdentityMap (usually based on ECID as key). The Target Third-Party ID Namespace only matters when Target needs to recognize a profile under a single external ID mainly for cross-device recognition when ECID isn't stable, like in case of server-side calls, cross-browser login, Target audience library referencing a 3rd-party ID etc.

    So recognition on edge = IdentityMap, but Target's own profile store still keys on ECID + optionally one 3rd-party ID you designate.

    Would be happy to know more for multiple business entities converging on one AT instance.

    • Which namespace did you pick as the Target 3rd-Party ID & how are you handling the other entity IDs? Ignored, or pushed as profile attributes into Target instead of as identities?
    • Are you seeing an actual profile fragmentation symptom in Target like duplicate profiles or is this concern before go-live?
      Michael_Soprano
      Michael_SopranoAuthor
      Level 10
      September 29, 2026

      There is no chance to resolve such a confilicts in Target when it comes to multiple business entities. Additionally Target on one instance has one shared database for Visitor Profiles. Sitching is kept at AEP level. 

      Gokul_Agiwal
      Community Advisor
      Gokul_AgiwalCommunity AdvisorAccepted solution
      Community Advisor
      August 4, 2026

      Hi ​@Michael_Soprano  - Interesting discussion - Adding points from my understanding 

       

      In an AEP + Adobe Target integration, identity resolution and profile stitching primarily happen within AEP Identity Service. Multiple identities such as CRM ID, Loyalty ID, Account ID, Email, and ECID can coexist in the identityMap and be stitched together into a unified profile through the identity graph.  

       

      More Reference - 

       

      When Target is integrated through Web SDK and Edge Network, Target can leverage profile and audience information that has already been resolved by AEP. The Edge Network acts as the bridge between AEP and Target, allowing audiences and profile context to be available for personalization. 

       

      While Adobe Target supports only a single namespace as the Target Third Party ID (mbox3rdPartyId), that limitation applies to Target's native profile identifier. It does not prevent AEP from maintaining and stitching multiple identities behind the scenes through the identity graph.

       

      Therefore, in a Web SDK + Edge implementation, audience qualification is driven by AEP's identity resolution capabilities, whereas the Target Third Party ID remains a Target-specific profile identifier used for Target profile recognition. This is one of the key advantages of the Edge-based architecture, where identity stitching and audience evaluation are handled by AEP, and Target consumes that resolved context for personalization.

       

      Thanks, Gokul
        Terms & ConditionsAccessibility statement

        Loading footer...