Third-Party Scripts
Decide which third-party scripts and tracking pixels to keep, how many is too many, and whether server-side tracking helps speed.
Select Subcategory
Common Questions
How many tracking pixels and third-party scripts is 'too many' before they measurably hurt Shopify conversion rate?
Third-party scripts hurt Shopify conversion when they block the main thread, not at a set count, and neither Shopify nor Google publishes a safe number. The measurable line is Interaction to Next Paint (INP): above 200 milliseconds, a page's responsiveness stops being good (web.dev, October 2026). So count the scripts that run before a shopper can tap, not the pixels.
What's the right way to prioritize which third-party scripts to keep versus cut when a performance audit flags too many running simultaneously?
Third-party scripts sort into keep or cut on two axes, measured browser time and a named business owner, so costly scripts with no owner go first. Find them on four routes: theme code and app embeds, Customer Events pixels, the tag manager, and app script tags. Shopify stops running script tags on 1 March 2027 (Shopify developer docs, October 2026).
Should a mid-market Shopify merchant move to server-side tracking primarily to improve data accuracy, primarily for page speed, or both equally?
Server-side tracking on Shopify earns its cost in data accuracy, not page speed, because server-to-server events "can't be blocked by browser-based ad blockers" (Shopify Help Center, October 2026). Shopify's Facebook & Instagram app sends purchases that way at Enhanced or Maximum data sharing. Google prices a tagging server at about $45 a month, two recommended (Google for Developers, October 2026).