Server-Side Tracking

What Is Server-Side Tracking?

Server-side tracking collects and transmits marketing events from your server rather than from the visitor’s browser. In traditional client-side tracking, a JavaScript pixel fires in the browser and sends data to ad platforms. In server-side tracking, your server sends that data directly.

The fundamental difference is who sends the event data:

• Client-side (pixel): Visitor’s browser sends data to Meta, Google, etc.
• Server-side: Your server sends data to Meta, Google, etc.

Why Server-Side Tracking Matters

Browser-based tracking has become unreliable. Several forces are degrading pixel accuracy:

Ad Blockers

An estimated 30-40% of web users run ad blockers that prevent tracking pixels from loading. Every blocked pixel is a missed conversion that your ad platform cannot see.

iOS Privacy (ATT)

Apple’s App Tracking Transparency requires apps to ask permission before tracking. Most users deny it, which means the Meta Pixel and similar tools lose visibility into a large share of mobile users.

Browser Cookie Restrictions

Safari’s Intelligent Tracking Prevention (ITP) limits third-party cookies to 7 days and first-party cookies set by JavaScript to 24 hours. Firefox and other browsers have similar restrictions. This breaks the pixel’s ability to identify returning visitors.

Consent Regulations

GDPR and similar privacy laws require explicit consent before setting tracking cookies. Visitors who decline consent are invisible to browser-based pixels.

How Server-Side Tracking Works

A typical server-side tracking flow for a Shopify purchase:

1. Customer places an order on your Shopify store
2. Shopify triggers an order webhook to your server
3. Your server collects order data: revenue, products, customer email (hashed)
4. Your server sends the event to ad platforms via their server APIs (e.g., Meta Conversions API, Google Ads API)
5. The ad platform matches the event to the original ad click

Because the data never touches the customer’s browser, ad blockers, cookie restrictions, and privacy settings do not affect it.

Server-Side vs Client-Side Comparison

Aspect	Client-Side (Pixel)	Server-Side
Blocked by ad blockers	Yes	No
Affected by iOS ATT	Yes	Partially
Cookie dependent	Yes	No
Data you control	Limited	Full control
Setup effort	Low	Medium to high
Event accuracy	50-70% of events	85-95% of events

Server-Side Tracking for Shopify

Implementing server-side tracking on Shopify typically involves:

1. Setting up webhook listeners for order events
2. Integrating with ad platform APIs (CAPI for Meta, Google Ads API, etc.)
3. Hashing and sending customer match keys
4. Deduplicating with any existing pixel events

This is technically involved, which is why many merchants use tools that handle the integration automatically.

Server-Side Tracking in Detectly

Detectly handles server-side tracking out of the box. When you install the app, it automatically listens for Shopify order events and sends conversion data to connected ad platforms via their server APIs. No coding or webhook configuration required. Combined with UTM-based attribution, this gives you both accurate platform reporting and independent order-level attribution.