Server-side tracking

Server-side tracking

Affiliates

Server-side tracking is recording clicks, orders and conversions from a server rather than from scripts running in the shopper’s browser.

What is Server-side tracking?

Browser-based tracking relies on pixels and cookies that ad blockers, privacy settings and short cookie lifetimes can stop. Server-side tracking sends the events from a server the brand or its software controls, so fewer conversions are lost. Common forms: an ad platform’s conversions API fed from the store’s order data, a tracking server that records link clicks before redirecting, and webhooks that report orders straight from the store. Not magic: the server still needs something to link an order back to a click, such as a click ID saved with the order. Without that link, server-side tracking can’t credit the sale.

Example

Instead of relying only on a thank-you-page pixel, a brand sends each Shopify order to its ad platform from the server, including the click ID saved at checkout.

Why Server-side tracking Matters

Lost conversions make good channels look bad and underpay partners. Server-side data closes much of that gap.

Server-side tracking FAQ

Does server-side tracking get around cookie consent?

No. Privacy and consent rules still apply to data sent from a server.

How does Spark! track creator sales?

Spark! records each click on a creator’s tracked link and saves a click token with the shopper’s cart. When the order comes in, Spark! reads that token from the order and credits the creator.

Explore More Terms

Browse our complete glossary of e-commerce and subscription terms.

View Full Glossary
Space, at your fingertips

What would you do with 22% more revenue?