If you're talking about widgets that track things like CDN performance and errors, like NewRelic's[1], then... maybe. I love that people are blocking tracking widgets, but there are some companies that provide useful gadgets that don't compromise privacy and I'd hate for them to be blocked as well. That said, I can't wait for Facebook tracking widgets to go away.

1) https://blog.newrelic.com/2014/03/13/javascript-error-report...

I don't think OP is talking about products which consist entirely of front-end code, but rather analytics or tracking services which rely on front-end JS to collect user data, which is then used by the main product.

For cases like MixPanel, I don't see why the traffic wouldn't be proxied through the original domain. Unless MixPanel needs to (i) ensure that the property is not faking their stats/events, or (ii) track visitors across sites, the fact that the JS etc. is served from MixPanel directly is more of a convenience than a necessity.

The same would not apply if MixPanel were providing a verification service to third parties, who were advertising on or wanting to buy MixPanel's customer's site.

with the advent of community driven filtering, how long until the self hosted tracking scripts get blocked also? and who would notice?