JournalTracking and ads

Consent and server-side tracking: what to settle before you switch it on

Sending data from your server does not make it exempt from consent. These are the questions to answer first.

A reeded glass shop door with an open sign seen from outside.

Moving tracking to the server gives you more reliable data. It does not give you permission to collect more of it. The rules about what you may send follow the visitor, not the pipe.

This is a practical guide, not legal advice. Your own lawyer should confirm what applies to your shop and your customers.

Settle these first

  1. Where do your customers live? Different places have different rules, and you may be subject to several at once.
  2. What does your cookie banner actually do? If it records a choice but the tags ignore it, the banner is decoration.
  3. Which fields will you send? An order value is one thing. A hashed email and phone number are another.
  4. Can the server see the consent state? If it cannot, it cannot respect it.
  5. What does your privacy policy say? It must describe what you do, not what you meant to do.

Make the server obey the banner

The cleanest design is for the browser to pass the visitor's consent choice to the server along with each event. The server then sends the full event, with customer fields, only where consent allows, and a reduced event where it does not.

Keep a record

Write down what is sent, to whom, and under what condition. It helps when a customer asks, when a platform audits you, and when someone new joins the team.

What we do

We build the server events so consent is an input, not an afterthought, and we leave you with a plain description of what is collected. We also leave the legal review to a lawyer, because that is their job.

Photograph from Unsplash.

Bring us the account that is stuck.

Replies usually within 6 hours. Remote, working across UK, EU and US Eastern hours from UTC+1.