Does the Identify API allow any sort of hashing when provided two different identifying pieces of information? I’m currently setting the user ID to be the unique ID that our application uses, but we’re currently having many types of users use the same super log in. Are there any out of the box functions that allow the pairing of user ID and another piece of identifying information to further segment these users or would it be better to use a separate hashing system? Thanks!
Best answer by Denis Holmes
View original