Yes, that rejection email confirms you must migrate your tracker from the ScriptTag API to the modern Web Pixels API. Shopify now requires this for all public tracking apps for security reasons.
Your fear is valid; this change will break your current tracker. The Web Pixels API runs in a secure sandbox and cannot access the page’s HTML or document.
The only solution is to rewrite your tracker. Instead of scraping the page, your script must now “subscribe” to the standard e-commerce events (like product_viewed or add_to_cart) that the Web Pixels API provides. This is the only compliant path forward.
You mean, literally there is no way I can use my remote asset (tracker.js) and 100% depend only on the shopify web pixel api, just for this compliant path? or there is any workaround?
This seems to be like a middleman passing things to my api endpoint, skipping my main tracker entirely.