Server-side tracking moves data collection from the visitor’s browser to a server you control, eliminating the reliability problems that plague traditional JavaScript pixels.Documentation Index
Fetch the complete documentation index at: https://docs.upstackdata.com/llms.txt
Use this file to discover all available pages before exploring further.
Why It Matters
Traditional client-side pixels depend on JavaScript executing inside a visitor’s browser. That model is breaking. Safari’s ITP caps cookie lifetimes at 7 days (or 24 hours for link-decorated traffic). Firefox blocks known trackers by default. Ad blockers strip tracking scripts before they load. iOS 14.5+ App Tracking Transparency further limits signal availability across the Apple ecosystem. For Shopify merchants, every lost event is a lost signal — attribution gaps widen, retargeting audiences shrink, and ad platform algorithms receive incomplete conversion data. The downstream cost compounds: Meta’s algorithm optimizes toward the wrong audience, ROAS reporting becomes unreliable, and you over-invest in channels that only appear to perform. Server-side tracking sidesteps these problems entirely. Because the data collection happens at the server layer — outside the browser sandbox — ad blockers, cookie restrictions, and JavaScript failures have no effect on data capture.How It Works
Upstack Pixel operates at the Capture stage of the data pipeline. When a shopper interacts with your Shopify storefront, the Upstack theme extension fires lightweight first-party requests to Cloudflare’s edge network — the same infrastructure that serves your site assets. At the edge, Upstack performs three critical steps before the event enters the pipeline:- Bot filtering — Known bot signatures and suspicious traffic patterns are stripped so only human interactions proceed.
- First-party cookie management — A durable first-party cookie is set under your store’s domain, immune to ITP restrictions because it is issued server-side.
- Event normalization — Raw interaction data is transformed into a canonical event schema, ready for identity resolution and forwarding downstream.
Key Terms
| Term | Definition |
|---|---|
| Client-side pixel | A JavaScript tag running in the visitor’s browser — vulnerable to blockers and cookie restrictions. |
| Server-side tracking | Data collection handled by a server, outside the browser sandbox. |
| ITP (Intelligent Tracking Prevention) | Apple’s Safari feature that limits cookie lifetimes and blocks cross-site tracking. |
| First-party cookie | A cookie set under your store’s own domain, subject to fewer restrictions than third-party cookies. |
| Bot filtering | Automated removal of non-human traffic before events enter your data pipeline. |
| Edge network | A globally distributed server layer (Cloudflare) where Upstack processes events close to the visitor. |
Quick Start: Install Upstack Pixel
Get server-side tracking running on your Shopify store in under 10 minutes.
Events Taxonomy
See every event Upstack Pixel captures and its schema.