Show HN: I built a proxy to bypass adblock for OneSignal and Google Tag Manager
2 egorzudin 3 7/17/2025, 11:21:58 AM
Adblockers often block scripts like OneSignal (cdn.onesignal.com) and Google Tag Manager (googletagmanager.com), breaking push notifications and analytics on many websites. I needed a simple solution to restore functionality without requiring deep client-side changes or defeating user privacy.
So I built an open-source proxy you can self-host, deploy to Cloudflare Workers, and point your site to. It supports OneSignal and can be extended for GTM and others.
GitHub: https://github.com/verificatorrus/onesignal-proxy
Use cases:
Websites relying on push notifications or GTM metrics that get broken by uBlock
Landing pages needing basic analytics and events with fallback
SSR-friendly, no React/Vue required
From an Adblock user perspective, that was kinda the point, I don't want a site tracking me and I don't really care if I break notifications (which in most cases I don't want anyway). If I want the broken functionality I'll add a site to an allowlist once they're trusted. In the adblock arms race this is a bandaid that will get fingerprinted and blocked as well eventually
Ultimately the question is if the analytics data / notification functionality for roughly 30% of internet traffic (based on quick google search, who knows if that's accurate) so valuable to take on the burden of care and feeding of another web service?
But here's the nuance: most people install ad blockers to remove intrusive ads, not realizing that this often breaks useful functionality — like notifications they explicitly agreed to receive, or analytics that help improve the user experience.
My proxy isn’t trying to trick the user. It's meant for situations where the user has given explicit consent, but the OneSignal script simply fails to load because of blanket blocking.
By the way, this isn’t just about Adblock — there have been cases where entire countries have blocked onesignal.com, making notifications completely unusable even when the user trusts the site.
In that sense, this isn't about "bypassing" blockers, but rather restoring transparency: if a user agreed to a feature, it should be allowed to work.