Preventing profiles from stitching even with common identities | Community
Skip to main content
A
akwankl
New Participant
July 24, 2024
Solved

Preventing profiles from stitching even with common identities

  • July 24, 2024
  • 4 replies
  • 1345 views

Hi there,

 

Our company can have multiple online logins for the same set customer identities, but each login has a different permission level. For example:

 

1) Online Login A, owner permission, Account A,B,C

2) Online Login B, manager permission, Account A,B,C

3) Online Login C, subscriber permission, Account C

 

The challenge is, currently all these will stitch together as one single profile because of the connection between accounts. (Login C <-> Account C <-> Login B <-> Account A,B,C <-> Login A)

 

Is there a way to keep all the logins unique with their own profile, yet retain the same identities underneath each profile?

 

Thanks.

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by _Manoj_Kumar_

    Hey @akwankl  this is not an existing feature. It is more about what could be the new feature where at the data ingestion time we can decide if this data should be merged or not, by utilizing the existing merge policies available in platform.

    4 replies

    kautuk_sahni
    kautuk_sahni
    Employee
    September 16, 2024

    @akwankl Did you find the suggestion helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!

    Kautuk Sahni
    arpan-garg
    arpan-garg
    New Participant
    September 12, 2024

    Hi @akwankl  - Did you already tested this beta feature https://experienceleague.adobe.com/en/docs/experience-platform/identity/features/identity-graph-linking-rules/namespace-priority

     

    Thanks,

    Arpan

      _Manoj_Kumar_
      _Manoj_Kumar_
      New Participant
      July 25, 2024

      Hello @akwankl 

       

      To achieve this you will have to rethink the identities and make the identity unique somehow.

      One possibility is to combine entity based on a combination of account + loginType.

      Or 

      The product should support sending the merge policy at the time of data ingestion.

       

      Also, What is the use case for 3 different profiles? Can it be achieve by using merge policies for segmentation or another way

           Manoj     Find me on LinkedIn
        A
        akwanklAuthor
        New Participant
        July 25, 2024

        Hi @_manoj_kumar_ ,

         

        Thanks, the combination of account + loginType is one idea. Can you elaborate on the merge policy part please?

         

        Thanks,

        Alan

          _Manoj_Kumar_
          _Manoj_Kumar_Accepted solution
          New Participant
          July 26, 2024

          Hey @akwankl  this is not an existing feature. It is more about what could be the new feature where at the data ingestion time we can decide if this data should be merged or not, by utilizing the existing merge policies available in platform.

               Manoj     Find me on LinkedIn
            DavidRoss91
            DavidRoss91
            New Participant
            July 24, 2024

            Hi @akwankl 

            From my understanding, this is a known issue within the identity stitching of AEP. I have heard there are active investigations of the hope to correct this, but as of now, it cannot be avoided.

             

            David

              Terms & ConditionsAccessibility statement

              Loading footer...