(Sorry for long post)
Web Pixels are marketed as the the safe and reliable way to standardize customer event tracking (while respecting their privacy).
Recently, Shopify Web Pixels sandbox URL were added to Ublock Origin list uBlockOrigin/uAssets/commit/cedb92b. the blacklist is on the path /wpm@*/web-pixel-
usually the issue was that the receiving service is blacklisted, google ads, facebook pixel etc… a workaround was to wrap the receiving endpoint through a reverse proxy to bypass the blacklist. (big companies probably have access to Server Pixels circumventing this issue altogether - but what about smaller apps ?)
however today it is the loading service (Shopify Web Pixels sandbox) that is blacklisted. developers currently have no way to adapt to this situation because we don’t have the necessary control over the infrastructure.
What this means is that developers will need to quit Web Pixels Sandbox and offer direct scripts to be added on theme to bypass the blacklist. defeating the purpose of Web Pixels and harming adoption (Web Pixel less accurate results than going raw). this gets even trickier for checkout events that are only available through Web Pixels.
Proposition: Add a feature similar to App Proxy URL to allow the MERCHANTS (and a default value by App Developers) to change the Web Pixel loading URL thus decentralizing the blacklisting efforts of tracking blockers. this should be available for both Custom and App Pixels.
another alternative which I believe is less likely is to launch Server Pixels for the general public.
