Script Engineering & Attribution
Managing Third-Party Scripts & Migrating to CAPI
Why client-side advertising pixels destroy mobile checkout responsiveness, and how server-side tracking preserves 100% conversion attribution while recovering 400ms of CPU execution.
The True Cost of Marketing Pixels
When marketing teams install the Meta Pixel, TikTok Pixel, Google Ads Tag, Hotjar, Klaviyo, and Yotpo directly into theme.liquid, every customer phone must download, parse, and execute over 1.2 MB of external JavaScript.
Average Execution Cost of Common E-Commerce Trackers:
Meta Pixel (fbevents.js)~110ms Main-Thread CPU | 84 KB Transfer
Google Tag Manager (gtm.js)~140ms Main-Thread CPU | 120 KB Transfer
Hotjar / Session Replay~220ms Main-Thread CPU | 165 KB Transfer
The Solution: Server-Side Conversions API (CAPI)
Server-side tracking shifts event dispatching from the customer's mobile browser to a Cloudflare Worker or edge container. When a purchase occurs:
- Shopify fires a secure backend webhook to your edge proxy.
- The edge proxy hashes customer parameters (SHA-256) and sends the event directly to Meta's Graph API and Google Analytics Measurement Protocol.
- Zero client-side CPU is consumed, and attribution is immune to browser ad-blockers and iOS Safari ITP cookie deletion.
Audit Your Store's Third-Party Script Cost
Run our free explorer to identify blocking scripts and CAPI candidates.