Cannot unmask Custom User ID in Visitor's Profile

[atanasivanovv]

Describe the bug

I've integrated with the Microsoft Clarity API from my Client and I've added the Identify API so that I send a unique identifier for each of the customers which we can filter by, starting with MS....

The problem is that once I go to the specific Video of the user I can see only the masked ID.

This is not doing us any favor, as we don't know which customer has done these actions and we cannot make adequate analytics for that.

Is there a way this Custom User ID can be unmasked, through the API or the dashboard as I didn't see such an option in either of those?

Repro Steps

1. Use identify API in your code

window.clarity('identify', <some-unique-id>);

2. Go to a specific Visitor's details page

Screenshots

Browser info:

• OS: iOS
• Browser: Chrome

[cygnus-dawn]

Experiencing the same with my project. Used clarity("set", "userId", email) instead of "identity". I also have masking in the relaxed setting since the beginning of my project. This custom id is now not usefull to any end users who have access to the project including admins.

[umair-me]

Having the same issue. This is no use if we can not see the identifier.

[cygnus-dawn]

2 months in. Our CSAM literally said "iT's OpEn SoUrCe, CoNtRiBuTiOnS aRe AlWaYs WeLcOmEd". I know this repo is just the library to log metrics which is not even the problem here. Both the backend and front end to view the data are closed source. Never heard back from the team hiding behind the feedback button on the site itself.

[ramicaza]

+1

[ebezares]

Any update on this?

[cygnus-dawn]

@ClaritySupport do your job pls

[nairmanu]

Clarity securely hashes the custom-id on the client before being sent to Clarity servers. Clarity doesn't store custom identifier as plain text. Instead, the custom ID is hashed on the client before being sent to the servers. To better view custom-user-id on the clarity dashboard UI you can use friendly name parameter, and this value is shown on the dashboard instead of the hashed value that is stored. You can find more information in our documentation https://learn.microsoft.com/en-us/clarity/setup-and-installation/identify-api#example-with-friendly-name

[cygnus-dawn]

What's stopping me from just the same value as the friendly value. This doesn't scale when you have thousands of ids that you have no idea is there so that use case of "oh but we hash your searches! So it's okay!" is completely irrelevant on why this is a problem in the dashboard.

window.clarity("identify", "[email protected]", "custom-session-123", "custom-page-123", "[email protected]")