search

microsoft / clarity

A behavioral analytics library that uses dom mutations and user interactions to generate aggregated insights.
https://clarity.microsoft.com
MIT License
2.17k stars 217 forks source link

IP Blocking Does Not Work #627

Open GrindstoneDesign opened 5 months ago

GrindstoneDesign commented 5 months ago

Of my 15 projects, not 1 has effectively blocked our office IP after being set in the settings page.

bdinnerv commented 4 months ago

I am having the same issue, the IP blocking does not work - I have checked the Javascript console in Edge, Chrome and Firefox and none of them show the message that the IP is being blocked and all my sessions when testing the sites come up in Clarity

SamuelAshbrook commented 4 months ago

I am also experiencing this issue.

dionduodeka commented 4 months ago

Me 2

SteveElmer commented 4 months ago

Same here

ClaritySupport commented 3 months ago

Clarity only supports IPv4 addresses. We do not support IPv6 or dynamic IP addresses (for example, VPN). However, we couldn't block IP addresses if the user has both IPv4 and IPv6 as its non-deterministic.https://learn.microsoft.com/en-us/clarity/setup-and-installation/ip-exclusion#verify-if-an-ip-address-is-blocked-for-a-webpage

GrindstoneDesign commented 3 months ago

Clarity only supports IPv4 addresses. We do not support IPv6 or dynamic IP addresses (for example, VPN). However, we couldn't block IP addresses if the user has both IPv4 and IPv6 as its non-deterministic.https://learn.microsoft.com/en-us/clarity/setup-and-installation/ip-exclusion#verify-if-an-ip-address-is-blocked-for-a-webpage

It seems that more and more addresses use v6 and v4, leaving a pretty large gap in the number of users who will not be able to filter traffic. Are there any plans to block IPs that use both 6 and 4? Or possibly a feature to exclude certain users from results based on their user ID?

While it would be a workaround, if I was able to mark my profile/ my teams profiles, and filter out the respective recorded sessions, that would be an alternative way to clean up false sessions.

EDIT: didn't mean to close thread