Server-side tracking

Server-side tracking sends conversion events from a server the business controls, instead of relying only on the visitor's browser. It can keep an event that the browser lost, but it does not add data that consent and other rules do not allow.

Stock photos and example labels, not customers.

Definition

Server-side tracking sends conversion events from a server the business controls, instead of relying only on the visitor's browser. It can keep an event that the browser lost, but it does not add data that consent and other rules do not allow.

Example with made-up numbers. Made-up scenario: 100 orders are placed in a day, and the browser event fires for only 85 of them because some visitors block scripts or leave early. A server event sent from the order system reaches the analytics tool for all 100, and the team counts each order once by its order ID.

How to use it

A browser event can be lost when a visitor leaves early, when a blocker stops the script or when a redirect drops the event. A server event is sent from the order system after the order is confirmed, so it does not depend on the browser staying open. The two events have to be matched, usually by the same order ID, so that one order is not counted twice.

Setting it up needs hosting, maintenance and a named person who owns the event names. Consent and retention rules still apply to what is sent, and each receiving tool has its own format and rules. Check the current documentation of each tool, and test a few orders end to end before trusting the numbers.

Built for shop owners, creators and agencies. Stock photos, not customers.

Run the next client review from one screen.

We open one agency at a time, with your own accounts connected read-only first.

Request access

How we plan to price it