Skip to content
Articles on Web Development

Server-side tracking: what changes for your shop’s data and for privacy

Server-side tracking moves the sending of data from the browser to the server. It helps you lose fewer events and keep better control of what leaves your site, without removing the need for consent.

· 4 min read

In this article

Want to talk it through for your business?

Message us on WhatsApp (opens in a new window) or by email
In this article

    In short: Server-side tracking sends events (visits, baskets, purchases) to analytics and advertising tools from your server rather than from the browser. It gives you more control over the data that leaves your site, more complete events and lighter pages. It does not remove the obligation to provide a privacy notice and obtain consent: data is sent only after the visitor has made a choice.

    When a customer browses your shop, tools such as Google Analytics or the Meta and TikTok pixels record what they do: visits, baskets, purchases. They usually do this with small programs (scripts) that run in the customer's browser. With server-side tracking, that data passes through your server first, and your server sends it on to the tools.

    Why it's being talked about

    • Browsers and ad blockers restrict third-party scripts. Some events never arrive and the statistics under-count orders.
    • Advertising campaigns optimise better when they receive complete purchase data.
    • On a site weighed down by lots of scripts, moving to the server can make pages lighter.

    How it works, simplified

    1. The site sends events (visit, add to basket, purchase) to a collection point on your own domain.
    2. That point, the ‘tag server’, checks and prepares them.
    3. It forwards them to the chosen tools (analytics, advertising) with only the data you decide to send.

    Options include server-side Google Tag Manager and the conversion interfaces offered by the advertising platforms (Meta's Conversions API is one example). Shopify also offers built-in ways to send purchase events.

    The real benefits

    • Control. You decide which data leaves. Before sending, you can strip out information that isn't needed (the full IP address, for example).
    • More complete data on purchases, especially those confirmed by the server.
    • Lighter pages, because the browser runs less external code.
    • Less dependence on individual browsers.

    What doesn't change: consent

    This is where the most common misunderstanding lies. Moving the sending from the browser to the server does not remove the obligation to inform people and ask for their consent when the tools use identifiers or follow a person over time. The processing of personal data is still processing. The rules on consent and privacy notices stay the same. So:

    • Data must be sent only after the customer has made their choice in the banner.
    • A refusal must be respected on the server side too.
    • The privacy notice must name the providers that receive the data.

    US providers raise the issue of data transfers to countries outside Europe. European data protection authorities, including Italy's (the Garante), have already ruled on some analytics tools. Check your provider's terms and update your privacy notices. You'll find the overall picture in privacy for an online shop.

    An alternative: more privacy-friendly analytics

    There are statistics tools designed to work without identifying people and with the data stored in Europe. They may be enough if you need traffic figures rather than precise campaign attribution.

    When it makes sense

    • You run paid advertising with significant budgets and need reliable measurement.
    • You have lots of scripts slowing the site down.
    • You want finer control over which data leaves.

    If your traffic is small and you don't run campaigns, a good consent banner and a tidy set-up of traditional analytics are enough.

    Costs and upkeep

    The tag server has a hosting cost and needs configuring and checking. Someone has to verify regularly that events are arriving. It's one more component to keep healthy.

    Further reading: a cookie banner that meets the Italian Garante's guidelines · privacy for an online shop · a slow site sells less

    Frequently asked questions

    What is server-side tracking?

    A way of collecting browsing data in which events pass through a server on your own domain, which forwards them to the chosen tools with only the data you decide to send.

    Does server-side tracking let you avoid cookie consent?

    No. It changes the technical channel, but the processing is still processing: you need a privacy notice and consent when the tools use identifiers or follow a person over time.

    When does it make sense?

    With significant paid campaigns, with lots of scripts slowing the site down, or when you need finer control over the data. For a small site, a good banner and carefully configured analytics are enough.

    Let's talk

    Want to measure your campaigns better while respecting consent?

    We set up server-side tracking and check that nothing is sent before the visitor has made a choice.

    Related service: Marketing and communication