Server-side tracking

What it means

Server-side tracking is a way of measuring traffic and conversions in which the visitor's browser does not send data directly to third-party analytics and advertising tools. The data first go to a server controlled by the company, which processes them and passes them on. In classic client-side measurement, the browser itself sends data through each tool's scripts.

The main reasons are accuracy and control. Ad blockers, browser restrictions and short cookie lifetimes mean classic measurement captures only part of visits. A server-side set-up is more resilient to these limits. The company also decides which data leave for third parties and in what form, and can, for example, truncate IP addresses.

Server-side tracking does not change the legal rules. If information is stored on or read from the visitor's device for measurement, cookie consent is still required, and processing personal data needs a legal basis under the GDPR. The technique must not be used to get around a refusal of consent.

How it works in practice

A typical deployment uses a server-side tag manager container running on the company's subdomain and sending data to web analytics and ad platforms. On the advertising side, server-to-server conversion APIs are used, improving campaign optimisation and the accuracy of retargeting.

The company gets more accurate figures on conversions and traffic sources, especially when measurement is combined with UTM parameters and CRM data. This helps allocate the marketing budget better. For online stores it can also be linked to data on returns and actual margin.

Deployment requires a server, its administration and running costs that grow with traffic. For a smaller company website it is worth considering whether the extra accuracy justifies the cost. With a larger ad budget the investment usually pays back through better campaign optimisation.

What to watch out for

The biggest risk is configuring server-side measurement to send data about visitors who refused consent as well. That breaches both cookie rules and the GDPR and can lead to a fine. The administrator must ensure the server container respects consent status exactly as browser measurement does.

Mind the information duty too. Visitors should know which tools are used and to whom data are passed, even if it goes through the company's server. The privacy notice and cookie banner need updating when moving to server-side measurement.