>> because of the cost to the advertisers Odds are that this addon doesn't actually trick the major advertisers whatsoever. 1. Any user/session that is seen c

>> because of the cost to the advertisers Odds are that this addon doesn't actually trick the major advertisers whatsoever. 1. Any user/session that is seen clicking many ads across many different domains will quickly have their entire history ignored. You can bet that if your browser is seen clicking 1,000 ads across 10 domains in one day, that your assault will be completely ignored and have exactly zero effect against the network or its advertisers. 2. If the addon manually triggers click events on hidden elements, then the ad network likely has javascript detecting these clicks as invalid and ignoring those impressions. a) Any element that is not visible on screen has events ignored - it will check for display:none, visibility:hidden, as well as common off-viewport positioning, transparency tricks, etc. b) When you manually trigger a browser event on an element, no event object is passed to the event handler, meaning those events are easy to detect and dismiss. Networks aren't guaranteed to implement #2, and any implementation may not be very sophisticated, but I'd bet a good penny that there is at least a basic client-side line of defense. If you manage to outsmart the client-side implementation, you're still very unlikely to outsmart the server-side analytics, where people who live and breathe this industry have spent over a decade writing software to analyze every ad click, specifically to not be fooled by such a naive attempt to hurt their business.