What platforms and configurations are required to know the email identity of an authenticated user that clicks on a specific website link? | Community
Skip to main content
N
nilsjohn
November 29, 2022
Solved

What platforms and configurations are required to know the email identity of an authenticated user that clicks on a specific website link?

  • November 29, 2022
  • 1 reply
  • 1386 views

For example, how do I use the AuthGuid metric (or other metric?) in Adobe Analytics to find a user's email address (the same address used during login authentication)?

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 Jennifer_Dungan

It really depends on your implementation... our authentication systems has a unique user GUID (not the mac address)... When the user logs into the site and every page/action they visit or interaction with while they are logged in, I capture that GUID in an eVar. If the user doesn't log out, that GUID is captured when they return to the site. When they log out, the GUID is cleared from the systems and subsequently from tracking. (I know some implementations set their eVar to never expire... but with shared devices, we treat "sign out" like a clean slate. Therefore I rely on passing the GUID on each call.)

 

I don't know enough about your implementation to know if what you are capturing is tied to the user's device, or tied to the account... Or are you talking about the user's ECID? which is Adobe's users identification GUID? If that's the case, then yes, that is just your Adobe UV identifier.... You would need to see how your authentication system works, where the data is stored (cookie? session storage? etc) and how to extract it... then you need to know if this is an actual user id, or just an authentication token.

 

An Authentication Token would be a different value on each log in, and basically acts as an interface between your site and the authentication portal to say "this is a valid login session"... but overall, that data wouldn't be helpful to you.

 

You may need to reach out to your developers to explain what you are trying to do, and work together to find a solution.

1 reply

Jennifer_Dungan
Community Advisor and Adobe Champion
Jennifer_DunganCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
November 29, 2022

Personally, I wouldn't track a user's email address in Analytics as this is a privacy concern.... 

 

In my own company, we track the unique User GUID... IF that user's email needs to be known, it has to go through a few channels of approval where the guid can be looked up in the user authentication service, which not everyone has access to.

 

Or is that what you are asking? You have a GUID and you want to find the email address? You will need to contact the team that manages your authentications and ask them to look it up...

    N
    nilsjohnAuthor
    November 29, 2022

    Thanks! Yes, 100% agree that identifying visitors is not best practice. In fact, I need this information to convince my manager not to do this. Would the team that manages our authentications simply need to look up the email according to the custguid or authguid, or is there more to it? I thought custguid was mapped to a machine's mac address, so would they need the authguid? Any insight is appreciated.

    Jennifer_Dungan
    Community Advisor and Adobe Champion
    Jennifer_DunganCommunity Advisor and Adobe ChampionAccepted solution
    Community Advisor and Adobe Champion
    November 29, 2022

    It really depends on your implementation... our authentication systems has a unique user GUID (not the mac address)... When the user logs into the site and every page/action they visit or interaction with while they are logged in, I capture that GUID in an eVar. If the user doesn't log out, that GUID is captured when they return to the site. When they log out, the GUID is cleared from the systems and subsequently from tracking. (I know some implementations set their eVar to never expire... but with shared devices, we treat "sign out" like a clean slate. Therefore I rely on passing the GUID on each call.)

     

    I don't know enough about your implementation to know if what you are capturing is tied to the user's device, or tied to the account... Or are you talking about the user's ECID? which is Adobe's users identification GUID? If that's the case, then yes, that is just your Adobe UV identifier.... You would need to see how your authentication system works, where the data is stored (cookie? session storage? etc) and how to extract it... then you need to know if this is an actual user id, or just an authentication token.

     

    An Authentication Token would be a different value on each log in, and basically acts as an interface between your site and the authentication portal to say "this is a valid login session"... but overall, that data wouldn't be helpful to you.

     

    You may need to reach out to your developers to explain what you are trying to do, and work together to find a solution.

    Terms & ConditionsAccessibility statement

    Loading footer...