Hacker News Reader

I was implementing Segment this week, and I was excited to see that they do far more than customer analytics now. With a single installation of analytics.js, you can turn on tools like Sentry.io error tracking, HelloBar announcements, or secure user accounts with Castle.io. With a single integration, Segment is becoming an app store for websites.

View on HN

As we learned in another post, having the name analytics.js can get you blocked by Ad block extensions. Expect analytics.js to not run in your apps.

To me this is the primary challenge of outsourcing your client side tracking -- you risk a wholesale block of your analytics if the Segment file gets blacklisted.

this is definitely a deal breaker. other than server-side, are there any other work arounds? like roll your own domain proxy or something?

I've looked deeply into this and it works to a point, but you still end up in situations where vital things get blocked.

Just bundle it in with the rest of JS payload with something like webpack. Individual calls to certain domains (GA, Heap, etc) might still get blocked, but the payload itself will be fine.

Does that cause problems with segment's servers being unable to see the user's remote address?

Reply on news.ycombinator.com