Adobe Target destination | Adobe Higher Education
Skip to main content
Michael_Soprano
Michael_Soprano
Level 10
July 29, 2026
Frage

Adobe Target destination

  • July 29, 2026
  • 1 Antwort
  • 7 Ansichten

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? 

    1 Antwort

    K
    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?
    0
    Allgemeine NutzungsbedingungenAccessibility statement

    Loading footer...