The Taboo Subject Most Marketing Agencies Do Not Discuss with Their Clients

Published by Thomas dans la catégorie Best Practices on 12.02.2026 Last update : 29.09.2026 à 09h42


Table of content

You have invested in a great website, expensive campaigns and a solid content strategy. Every month, your agency shows you curves, clicks and impressions. Everything seems fine.

Yet a silent reality is eating into your budget and may expose you legally, and few agencies raise it on their own: your tracking may be outdated, poorly wired to consent, and costing you money.

In short

  • Ad blockers, browser restrictions and cookie refusals deprive your campaigns of part of their conversions.

  • Many setups do not truly respect the visitor's choice: that is an FADP and GDPR risk.

  • Server-side tracking makes measurement more reliable and more controllable, without ever overriding a refusal.

  • Agencies and brands both benefit from putting the topic on the table.

The lie of omission of client-side tracking

Funnel of client-side tracking losses: three walls, browser restrictions, consent refusals and ad blockers, reduce the conversions that reach the ad platforms.

Most websites still rely on tracking that runs in the browser, such as the Meta pixel or the standard Google Analytics tag. Three problems follow:

  1. Legal risk: many tags fire before the visitor's choice or ignore a refusal. In Switzerland, the FADP provides for fines of up to CHF 250,000 against the individuals responsible, for intentional violations; in the EU, the GDPR goes up to EUR 20 million or 4% of worldwide turnover.

  2. Data loss: according to GWI (Q2 2025), 30.9% of Swiss internet users run an ad blocker; Safari caps cookies set by JavaScript at 7 days (ITP); and every cookie refusal legitimately reduces the observed volume.

  3. Eroding performance: fewer conversions reported, and Google Ads and Meta algorithms optimise on an incomplete picture. ROAS drops, not because your ads are bad, but because measurement is failing.

Why your agency does not talk about it

This is the heart of the taboo. For a creative or media agency, raising the subject often means acknowledging a technical and legal complexity outside its core business:

  • Technical complexity: server-side tracking requires data engineering skills, not just marketing.

  • A cost that is hard to sell: without some education on data governance, the client does not see the point.

Result: the status quo is maintained, at the expense of the client's performance.

The solution: server-side tracking and compliance

With server-side tracking, the browser sends a single stream to a server you control, on a subdomain of your site, which then passes the data on to the platforms. The benefits:

  • Control: you decide which data goes to Google, Meta or LinkedIn, and you strip what is not needed (IP, sensitive parameters).

  • Reliability: first-party measurement, resilient to the technical restrictions of browsers and blockers.

  • Performance: consented conversions passed on more reliably, deduplicated, sometimes enriched (enhanced conversions), for better fed algorithms.

What server-side tracking does not do: replace the cookie banner or track a visitor who refused. A refusal stays a refusal. Details in our FADP and GDPR compliance guide.

A-Track: a technical partner for agencies and brands

We are not a media agency: we specialise in marketing measurement and data governance. Agencies excel at creation and strategy; we handle tracking and compliance, alongside them.

  • For brands: every franc invested is measured correctly, in line with the law.

  • For agencies: you stay focused on performance and creativity, without carrying the technical complexity.

Conclusion: the questions to ask your agency

Checklist of six questions to ask your agency about server-side tracking and compliance: consent, Consent Mode v2, conversion gap, own server and monitoring.

Before your next monthly report, ask:

  1. Do our tags really wait for the visitor's choice?

  2. Is Consent Mode v2 active and verified?

  3. What is the gap between Google Ads, Meta conversions and our real sales?

  4. Do our conversions go through a server we control?

If the answers are vague, an audit is needed. For the method, see our tracking audit checklist.

Finally ask your agency the tracking question

Agency or brand, A-Track checks how consent is wired, whether Consent Mode v2 works and how large your conversion gap is, then helps you discuss it openly.

Start with a 30-minute call with an expert.

Talk to a tracking expert

Questions fréquemment posées

How long does Server-Side compliance and installation take?

▾
For a standard site, it takes between 3 to 7 business days for the audit, configuration, testing phase, and going live.

Is it complicated to migrate to Server-Side?

▾
It requires technical expertise (DNS, web and server GTM configuration, platform APIs, consent). This is the core business of specialists like A-Track. A poor configuration can cause data loss or duplicates, or even non-compliant sends: hence the importance of a testing phase before going live.

Is Server-Side tracking reserved for large companies?

▾
No. With hosting providers such as Stape, the infrastructure has become accessible to SMEs. It is especially useful as soon as you invest regularly in advertising or sell online: reliable conversion data then matters directly for your campaigns.

An initial audit shows whether the investment is justified for your site.

Can I use GTM Server-Side for tools other than Google?

▾
Yes. You can send data to Facebook, TikTok, Pinterest, LinkedIn, Klaviyo, or even your own SQL/BigQuery database from the same server.

What is "Server-Side" tracking?

▾
It is a method where the browser sends data to your intermediary server (proxy), which cleans it and then forwards it to the platforms. You maintain full control of the data before it goes to the GAFAM.

What are the major advantages of Server-Side?

▾
First-party measurement on your own subdomain, more resilient to browser restrictions and ad blockers, always respecting the visitor's choice.

Cookies set by the server, which can last longer than JavaScript cookies capped at 7 days by Safari (if the server is properly aligned with your domain).

Data control: filtering, hashing or removing sensitive information before it is sent to the platforms.

A potentially lighter page, if pixels are removed from the browser.