This Safari query parameter removal thing is just going to become a cat-and-mouse game, right? Google can easily start using gclid2 or even switch to using something like “a,” that you'd be less willing to indiscriminately chop off the URL. Eventually, you could even imagine a dynamic query key scheme, where you can identify it with a credit-card-style hash function. For example, if f(KEY) = (char1 + char2 + .. .+ charN) % 64 = 39, then it knows that that query key is its tracking ID.
Conversation
Notices
-
Embed this notice
Francisco Tolmasky (tolmasky@mastodon.social)'s status on Tuesday, 25-Jul-2023 22:59:43 JST Francisco Tolmasky
-
Embed this notice
Thomas 🔭✨ (thomasfuchs@hachyderm.io)'s status on Tuesday, 25-Jul-2023 22:59:43 JST Thomas 🔭✨
@tolmasky yes, but it would be very disruptive and provide incomplete data which will be at least to some extend unusable.
I think a better approach instead could be to not remove the parameters but stuff them with random data.
-
Embed this notice