Issue
Some of our users have Chrome extensions that prevent Sentry API envelope calls from going through. We want to inform or prompt those users that their events are not reaching Sentry.
Applies To
All SaaS Customers
Resolution
No, Sentry has no built-in way to detect this. The Sentry SDK does not expose anything in the error event that flags a Chrome extension or ad blocker as the cause, so you cannot detect this directly in Sentry.
You have a few options:
Use the tunnel option. Bundle the SDK with our NPM packages and route events through your own endpoint to work around ad blockers. See Dealing with Ad-Blockers and Using the tunnel Option.
Set up a Relay as a proxy. It sends your events to your own domain first and then to Sentry, which is less likely to trigger Chrome extensions.
Detect failures in your own code. Add error handling that detects failed Sentry API calls and shows a user-friendly message explaining that an ad blocker or security extension may be interfering with error reporting. Provide instructions to allowlist your domain and Sentry's IP ranges and domains, or to disable the ad blocker for your site. Users ultimately choose whether to change their browser settings.