Is server-side tracking necessary for ads, and is the agency's extra cost worth it?

We spend around 9.000 Euro a month for our Lille-based clothing store. Before switching to this setup, there was about a twenty percent gap in order numbers between the ad dashboard and our store's backend. After the migration, the match quality noticeably shot up and the ad platform started targeting accurately again.

Data ownership is a business's most valuable asset. When you rely solely on the browser, every privacy decision made by big tech companies directly hits your business. By moving to a server-side architecture, you first collect data in your own pool, filter it, and forward it to ad networks only to the extent permitted. It should be seen as an investment in the future.

What's your AOV and profit margin? If your average order value is low and margins are tight, a fixed monthly cost of 75 Euro could stretch your budget. But if your AOV is high, even just 10-15 extra accurately attributed orders a month will easily make this setup profitable.

There is a critical point agencies won't tell you here: server-side tracking cannot be used to bypass consent regulations. If a user hits reject on your cookie banner sending that data to an ad network via your server is illegal. Keep in mind, it only prevents data loss for users who actually give consent.

Before making the jump, ask your agency for a side-by-side comparison table of ad manager orders versus your store's database orders for the past three months. If the discrepancy is more than 80-100 orders a month, get this set up without wasting any time.

when we switch to server-side tracking, do we completely wipe all tracking scripts and pixels from the site's source code does the site speed up because of that?

edit: typed from phone, sorry for typos.

You don't wipe them completely, it usually runs as a hybrid setup. Meaning both browser and server send data at the same time, but the ad platform uses deduplication keys to prevent duplicate records. Since heavy scripts on the browser side are trimmed down, you do get a nice little boost in page load speeds.

We were very hesitant at first while running a similar spend because it's behind-the-scenes infrastructure work you can't see with your eyes. But when the ad platform's machine learning isn't fed properly, ad costs snowball every single month. If your budget is 8.500 Euro, this investment is no longer a luxury, it's a shield protecting your ad capital.

if youre going this route sort this out first. honestly if you dont write this down from the start, it leads to arguments later.

if you have questions write them; I'll answer as best I can.

I'd appreciate it if you shared the outcome. Everyone rushing into server-side tracking gets stuck at the same point.

This thread is archived.

There's a trap here, let me mention it. Most time waste accumulates in tasks waiting for approval.

I'm also curious if anyone does it differently.

I'm curious too. When you try to change everything at once nothing settles.

The answer varies greatly by industry; there is no one-size-fits-all rule. Hope this helps.

There's a trap here, let me mention it. Any unwritten clause becomes a point of disagreement later, as both sides remember it differently.

Correct me if I'm wrong.

We experienced almost the exact same thing last year. Just because everyone does it doesn't mean it's right.

Proven by experience.

I'd appreciate it if you shared the outcome. Map listings bring more business than blog posts for most local businesses.

Hope this helps.

Good call starting this thread.

The answer above hits the nail on the head. When you try to change everything at once, nothing settles.

Mistakes made on the server-side tracking side are usually reversible but expensive. If you post the result here, it will help others too.