nairmanu
nairmanu
I'm facing the same issue with iOS devices when running the app locally. (using http and localhost).
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...
Please provide a URL with Clarity enabled for us to further investigate the issue.
Closing this issue due to inactivity.
Fix to address this is available in the latest release. Please let us know if you are still facing the issue in latest version of clarity-js
For issues you're seeing in https://clarity.microsoft.com please reach out to [email protected] with the details of your bug along with your project ID or a link to your project page.
@erikatsg Consent Mode is enabled by default for all users originating from the European Economic Area (EEA), United Kingdom (UK), and Switzerland (CH). If consent is not given, each page...
Can you please provide the website URL where this is happening? Are you manually calling `window.clarity('start')`?
I'm unable to reproduce this issue on your website. Is it happening in any specific browsers/devices/pages in the website?
@copilot are these instructions also used when Copilot reviews the code? I want to add a instruction that says if cookie.ts or metadata.ts or any of the similar files except...