Short answer: server-side tracking and cookies are not a choice between two things. A cookie remembers in the browser where a visitor came from. Server-side tracking changes the route: your measurements first go through your own server to Google and Meta. So you still use cookies, and you still need consent. What you gain: cookies often last longer and more sales reach your ad platforms.
What a cookie does
A cookie is a small file in your visitor’s browser. It remembers, for example, that someone arrived through an ad. If that person buys two days later, the ad platform can link the purchase to that ad. Without a cookie, the platform doesn’t know where the buyer came from.
What server-side tracking does
With regular tracking, your visitor’s browser sends measurements straight to Google, Meta and LinkedIn. With server-side tracking, those measurements first go to a server of your own, which forwards them. So you decide what goes to which platform. The difference between the two routes is explained in client-side vs server-side tracking.
Server-side tracking still uses cookies. It changes the route of your data, not whether you recognise visitors.
Where the difference is
Who sets the cookie. With regular tracking, a script in the browser sets the cookie. Safari limits such cookies, sometimes to one day when someone arrives through an ad link. With server-side tracking your own server can set the cookie on your own domain, and it often lasts longer.
Who forwards the data. With server-side tracking the measurement goes through your server. Ad blockers and browser limits hit that route less often than Google or Meta scripts in the browser.
What is sent along. On your own server you can remove or add data before it goes to a platform, for example dropping an IP address or adding the margin of an order.
What it means for your ads
If a cookie disappears after a day, a purchase three days later no longer counts for the ad that brought it in. Google Ads and Meta then think that ad did nothing, and give it less budget. If the cookie lasts longer and more measurements arrive, the platform sees more of your real sales and distributes your budget better.
How much that makes a difference depends on the site: how many visitors use Safari or an ad blocker, and how long people think before they buy.
What doesn’t change
Consent is still needed. Cookies that track visitors need consent, server-side tracking included. If someone declines, you don’t measure that person.
A tracking mistake stays a mistake. If you measure the wrong button, your server simply forwards that mistake.
It is not a trick to get around privacy rules. It actually gives you more control over what you share.
How consent works with Google is in Consent Mode v2 in GTM.
How to decide whether it makes sense for you or your client
Check how many visitors use Safari in GA4 (Reports › Tech). The bigger that share, the more you gain.
Put store sales next to Google Ads and Meta over a month. A large gap points to measurements getting lost.
Look at how long customers think. If they usually buy after a few days or weeks, a cookie that lasts longer counts for more.
Read on in server-side tagging explained if you want to know how it works.
TrackLead makes sure sales and leads reach Google, Meta and LinkedIn properly, and tells you when something breaks. Take a look at tracklead.eu.
Frequently asked questions
Do I still need a cookie banner with server-side tracking?
Yes. Cookies and similar techniques that track visitors need consent under EU rules. That applies even when measurement runs through your own server.
Does server-side tracking work without cookies?
Partly. You can send a purchase without a cookie, but the platform then knows less about which ad led to it. Cookies and server-side tracking work best together.
Do cookies last longer with server-side tracking?
Often, when your own server sets the cookie on your own domain. Safari checks whether that server really belongs to your site. How to set that up is in our blog on setting up server-side tracking.
Is server-side tracking the same as cookieless tracking?
No. Cookieless tracking is a different approach in which you don’t recognise visitors. Server-side tracking changes the route of your measurements, not whether you use cookies.