Mixpanel Not Tracking: Blocked by Ad Blocker

How to fix it

Try these in order — the most common fix is first.

1. 1. Proxy through your own domain

   Copy steps
   1. Set api_host to your proxy domain in mixpanel.init()
   2. If you use Session Replay, also set lib_base_path
   3. Set MIXPANEL_CUSTOM_LIB_URL before the snippet to load the SDK via the proxy (not needed with npm)
   4. Forward Authorization and Content-Encoding headers and strip the path prefix correctly
   Did this fix it? Yes No

2. 2. Review consent and DNT settings

   Copy steps
   1. Check ignore_dnt: true if DNT should not count as opt-out
   2. Call has_opted_out_tracking() to see current status
   3. Check opt_out_tracking_by_default is not set unintentionally
   Did this fix it? Yes No

3. 3. Enterprise: first-party domains

   1. Enterprise customers can use First-Party Domains instead of a proxy (SDK assets are not covered)
   Did this fix it? Yes No

Symptoms

Events from some users never arrive; the Network tab shows blocked requests to api-js.mixpanel.com or cdn.mxpnl.com.

Why it happens

• Browser extensions block mixpanel.com and mxpnl.com
• Do Not Track treated as opt-out
• SDK or recorder modules still load from cdn.mxpnl.com
• Opt-out status stored in __mp_opt_in_out_<token>

This guide also covers

• mixpanel blocked by adblock
• mixpanel not tracking
• mixpanel proxy ad blocker

The same problem in other apps

All plan limits, paywalls & watermarks guides →

• Amplitude Event Volume Limit Exceeded (Amplitude)
• PostHog Blocked by Ad Blockers (PostHog)

Other Mixpanel errors

• Mixpanel Events Not Showing
• Mixpanel Identify Not Merging Users
• Mixpanel Data Delay: Events Late in Reports
• Mixpanel Import Failed or Events Dropped
• Mixpanel Event Limit Exceeded and Overage Bill
• Mixpanel Session Replay Not Working
• Mixpanel Users Reset Across Subdomains
• Mixpanel /decide and /flags Requests Failing