Storefront error library · Requests and cart · Reviewed November 15, 2026
ERR_BLOCKED_BY_CLIENT
on a Shopify store.
net::ERR_BLOCKED_BY_CLIENT means a browser extension blocked a request. Why Shopify stores see it on pixels and analytics, and the one case where it breaks your store.
The short answer
A browser extension or built-in blocker cancelled the request. Usually none: the shopper browses and buys while the pixel is blocked. It matters in one case: your own code waits for or calls a blocked script. A product form that calls fbq() or gtag() before adding to cart throws “fbq is not defined” for every shopper with a blocker, and the add never happens.
At a glance
ERR_BLOCKED_BY_CLIENT in three lines.
| Who can fix it | Nobody, unless your own code depends on the blocked script |
|---|---|
| Does it cost sales? | Rarely; yes when a pixel call sits in front of Add to cart |
| What Dozenfold does with it | Ignores known tracker requests; a theme error caused by a missing pixel opens an issue |
| Group | Requests and cart |
| Last reviewed |
What you see
The exact messages.
The same problem is worded differently by each browser and tool. Search your console and error tracker for all of them.
What it means
In plain English.
The request never left the browser. Something running in the shopper’s browser, usually an ad or privacy blocker such as uBlock Origin, AdBlock or Brave Shields, matched it against a filter list and cancelled it.
It is not your server and not Shopify. You will see it on your own machine whenever a blocker is on.
Does it cost sales?
Which steps it can break.
When it happens on the path to purchase, look first at:
- Add to cart handlers that fire a pixel first
- Checkout buttons wrapped in tracking calls
- Your own assets caught by a filter pattern
Why it happens on Shopify
The usual causes.
Ad and analytics pixels
Google Ads, Google Analytics, Meta, TikTok, Pinterest, Bing and Snapchat tags are on every major filter list.
Shopify’s own analytics calls
Some blockers also stop Shopify’s storefront analytics requests.
Your own files with tracking-like names
Filter lists match URL patterns. A theme asset or endpoint named like ads.js, tracking.js or banner can be blocked by mistake.
Real problem or noise?
Check this before anyone debugs.
Most stores log this error at some level. These signals tell you whether real shoppers are affected.
- NoiseThe URL belongs to Google, Meta, TikTok or another ad or analytics host.
- RealAn “fbq is not defined” or “gtag is not defined” error follows it.
- RealThe blocked file is one of your own theme assets.
How to fix it
Reproduce, then fix.
- 01
Never let tracking block the action
Call pixels only if they loaded, and do the shopper’s action first.
addToCart(variantId).then(() => { if (typeof window.fbq === 'function') window.fbq('track', 'AddToCart'); }); - 02
Test with a blocker on
Keep a browser profile with uBlock Origin installed and run through product page, cart and checkout before each theme publish.
- 03
Rename assets that get caught
If one of your own files is blocked, rename it away from words like ads, banner, track or analytics.
- 04
Use Shopify’s customer events for pixels
Pixels added through Customer events run in a sandbox, separate from your theme code.
Find it automatically
Know which errors cost orders.
Requests to known ad and tracking hosts that content blockers stop never become issues in Dozenfold; the list is fixed and shown read-only in Settings under HTTP monitoring scope.
What does matter is caught: if your theme throws because a blocked pixel is missing, that error opens an issue with the theme line, the share of sessions it hits and the orders it is estimated to cost.
14-day trial · From $49 a month · Billed through Shopify
Questions
ERR_BLOCKED_BY_CLIENT: FAQ.
Can I stop ad blockers from blocking my pixels?
Not reliably, and you should not try to hide tags from them. Make sure the store works when they are blocked.
Does ERR_BLOCKED_BY_CLIENT hurt SEO?
No. Search engine crawlers do not run ad blockers, and the error happens only in the shopper’s browser.
Why do I see it on my own computer?
You have a blocker or a privacy feature turned on. Test in a clean profile to see what most shoppers get.
How many shoppers use ad blockers?
It varies by audience and device; desktop and technical audiences block more. Measure it on your own store instead of relying on a global figure.
Written by the Dozenfold team, who build storefront error monitoring for Shopify. Reviewed November 15, 2026 against Chromium net error list (ERR_BLOCKED_BY_CLIENT) and Shopify: Customer events and pixels.