Web SDK - predefined method to reset all Identities | Community
Skip to main content
Michael_Soprano
Michael_Soprano
Level 10
September 28, 2025
Solved

Web SDK - predefined method to reset all Identities

  • September 28, 2025
  • 1 reply
  • 530 views

Assume that the users log-out in Web SDK and we would like to reset all identities. Is there any such a method in Web SDK? 

Best answer by bjoern__koth

Well, you can send the authenticatedState of "loggedOut" in your identityMap XDM payload. 

You should only have to send this once upon logout with the identities to disassociate them from the current ECID for calls that happen afterwards.

1 reply

bjoern__koth
Community Advisor and Adobe Champion
bjoern__kothCommunity Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
September 29, 2025

Well, you can send the authenticatedState of "loggedOut" in your identityMap XDM payload. 

You should only have to send this once upon logout with the identities to disassociate them from the current ECID for calls that happen afterwards.

Cheers from Switzerland!
    Michael_Soprano
    Michael_SopranoAuthor
    Level 10
    September 29, 2025

    @bjoern__koth thanks! So if I send logout then all of the events which are sent after that are assigned to separate new profile in RTCP? 

    bjoern__koth
    Community Advisor and Adobe Champion
    bjoern__kothCommunity Advisor and Adobe Champion
    Community Advisor and Adobe Champion
    September 29, 2025

    That is a good question tbh., and I had to look it up as well. This below is AI generated, but sounds reasonable.  

     

    The loggedOut state marks an identity as formerly authenticated, differentiating current anonymous vs. previously known users.


    Data sent with loggedOut identities can still be associated with the real-time profile, but the platform will treat these data points as lower confidence compared to those sent with authenticated state.


    Events and attributes tied to a loggedOut identity will continue to merge into the existing profile, unless the schema or segmentation definitions specify conditions based on authentication state.


    The system can use this state to avoid stitching new, authenticated data to a profile during non-authenticated sessions, improving accuracy in profile merging and reducing misattribution or duplicate profiles.

    Cheers from Switzerland!
      Terms & ConditionsAccessibility statement

      Loading footer...