You wouldn't spoof it with an open proxy. This wouldn't be organized crime trying to screw up your A/B testing. This would be individual consumer advocates and reactionaries with a GreaseMonkey script that intentionally sent back wrong numbers or dupes.
And they'd be doing it because of a principle like "these companies don't tell us that they gather and make money off this consumer data. If they won't admit it up front, let's just not give the data to them."
Go ahead, tell me that won't happen at least a few times in the next 5-10 years.
Comments
1. Considering most client-side analytics are based on IP address, you will require a large number of IPs.
2. It should not be terribly hard to filter out known open proxies or sessions with a specific nefarious pattern.
Overall, I think this post addresses a problem that doesn't quite exist yet; and if/when it does, it can be addresses in many ways.
You wouldn't spoof it with an open proxy. This wouldn't be organized crime trying to screw up your A/B testing. This would be individual consumer advocates and reactionaries with a GreaseMonkey script that intentionally sent back wrong numbers or dupes.
And they'd be doing it because of a principle like "these companies don't tell us that they gather and make money off this consumer data. If they won't admit it up front, let's just not give the data to them."
Go ahead, tell me that won't happen at least a few times in the next 5-10 years.
I also don't think this guy actually implemented the spoof he talks about..