The tricky part is that sites don't look at one identifier in isolation, they build a picture from a bunch of browser and device signals together. That's also why changing a couple of obvious values usually doesn't solve the underlying problem. It's worth reading how browser fingerprint spoofing works and why antidetect browsers are used for it here: https://gologin.com/blog/browser-fingerprint-spoofing-how-to-prevent-tracking/ . The article breaks down what makes up a browser fingerprint and how antidetect browsers replace those signals across separate profiles. It also explains why the values need to look like they belong to the same device rather than a random collection of settings.