Server-Side Tracking: +40% More Data for Clinik.ch (Client Case)

Server-Side Tracking: +40% More Data for Clinik.ch (Client Case)

Published by Thomas dans la catégorie Practical Cases on 31.10.2025 Last update : 29.09.2026 à 22h59

Table of content

Conversions vanishing from reports, a CPA climbing for no obvious reason, social channels that seem to deliver nothing: that was daily life at Clinik.ch before it moved to server-side tracking. The culprit was browser-only tracking, exposed to ad blockers, Safari's limits and cookie refusals.

Here is how A-Track, working with Lausanne agency Emblematik, rebuilt Clinik.ch's measurement, and what the numbers showed in the very first month.

In short

  • Client: Clinik.ch, a Swiss network of laser hair removal and medical aesthetics clinics.

  • Solution: server GTM hosted on Stape under a first-party subdomain, Meta, TikTok, Pinterest and Snapchat conversion APIs, CMP and Consent Mode v2.

  • Measured result: +40.41% more usable data in November 2025 versus September and October.

  • Google Ads: +33% conversions and a 22% lower CPA on a near-stable budget.

The client: Clinik.ch, an aesthetics clinic that bets on technology

Clinik.ch lists 11 clinics in Switzerland and more than 450,000 treatments on its website. Its positioning is premium:

  • Advanced medical technology: latest-generation medical lasers and VISIA skin analysis.

  • Medical supervision for safe treatments (permanent hair removal, rejuvenation).

  • Personalised approach: free consultation and tailored treatment plans.

A business that invests in cutting-edge equipment cannot steer its acquisition on approximate data. The digital infrastructure had to keep up.

The challenge: client-side tracking that was losing conversions

Before A-Track stepped in, every channel ran through the browser: GA4, Google Ads, Meta, Microsoft Ads. Three things were draining the data:

  • Ad blockers and VPNs: they stop measurement scripts from loading. According to GWI (Q2 2025), 30.9% of Swiss internet users use an ad blocker.

  • Safari and ITP: according to WebKit, cookies set in JavaScript are deleted after 7 days without interaction, and after 24 hours in some link-tracking cases. Conversion attribution breaks.

  • Cookie refusals: the site's Cookie-Script CMP statistics showed around 21% of visitors refusing cookies. Those conversions vanished from reports.

The result: an artificially high CPA and campaigns steered blind, especially on social media.

The A-Track solution: a full server-side architecture

Diagram of Clinik.ch's server-side tracking: the browser sends events to a server GTM container on a first-party subdomain, which applies the visitor's choice and then feeds GA4 and the conversion APIs.

We wrote a custom tagging plan, then moved all measurement to a server.

1. A server GTM container on Stape

The Google Tag Manager server container is hosted on Stape, under a first-party subdomain of Clinik.ch.

  • Browser side: the Stape Data Tag sends events to the site's own subdomain.

  • Server side: the Stape Data Client receives the data, cleans it and forwards it to GA4 and the conversion APIs.

This setup does not get around ad blockers or consent. It makes measurement resilient to technical restrictions (blocked third-party scripts, shortened JavaScript cookies) while respecting the visitor's choice: a refusal stays a refusal.

2. Conversion APIs on every social channel

The browser pixel is no longer the only source. Events are also sent server to server to:

  • Meta Conversions API (Facebook and Instagram);

  • TikTok Events API;

  • Pinterest API for Conversions;

  • Snapchat Conversions API.

Each event carries a unique event_id: the platform deduplicates pixel and server, so a conversion is never counted twice. More in our guide to Meta CAPI on server-side.

3. Consent and Consent Mode v2

  • CMP: Cookie-Script, integrated with the IAB TCF 2.2 standard in force at the time (version 2.3 took over in February 2026, see our article on IAB TCF 2.3).

  • Google Consent Mode v2 in advanced mode: without consent, Google tags only send cookieless signals, which Google uses to model missing conversions. According to Google (2021), this modelling recovers on average more than 70% of ad-click-to-conversion journeys lost to refusals.

A-Track tip

In healthcare and medical aesthetics, never send the treatment type or any medical detail to ad platforms. A generic "appointment booked" event is enough for the algorithms, and the server lets you strip those fields before anything leaves.

The results: +40.41% more usable data

We compared November 2025, the first full month after go-live, with the September and October 2025 average. These figures were measured at Clinik.ch over that period: they are not a promise for every website.

  • +38.49% more data captured thanks to server-side tracking, according to the client's Stape dashboard.

  • +1.92% additional data from visitors using ad blockers, VPNs or private browsing.

  • In total: +40.41% more usable data.

For the first time, GA4 also reports reliable conversion values: CHF 134,000 of tracked value over the month. ROAS can finally be calculated on real amounts.

Table of server-side tracking results at Clinik.ch: Google Ads CPA from CHF 75.16 to CHF 58.67, calls from 109 to 437, and more Meta, Pinterest, TikTok and Snapchat appointments within one month.

Google Ads: more conversions at a lower cost

On a near-stable budget (+3.65%):

  • Conversions: +33%, i.e. 1,630 conversions.

  • CPA: -22%, from CHF 75.16 to CHF 58.67.

  • Clicks: -28%. Fewer clicks for more conversions: with richer signals (Enhanced Conversions), Smart Bidding targets better.

  • Calls: from 109 to 437 phone calls measured.

Social media: channels that can finally be measured

Thanks to the conversion APIs, appointment bookings are now attributed to the right channels:

  • Meta: from 77 to 179 appointments (+132%).

  • Pinterest: from 0 to 412 appointments, on a channel that reported no conversions before.

  • TikTok: from 0 to 105 appointments.

  • Snapchat: from 60 to 104 appointments.

Part of this increase comes from better measurement of conversions that already existed. That is exactly the point: a channel that looked dead could finally be assessed and managed.

Conclusion: key takeaways for your website

The Clinik.ch case shows that performance no longer depends only on ads and budget, but on the quality of the technical data. Three actions to get started:

  1. Measure the gap: compare the conversions in your ad platforms with those in your CRM or booking system.

  2. Move key conversions to server-side, with event_id deduplication.

  3. Check consent: an up-to-date CMP and Consent Mode v2 in advanced mode.

To go further, read our guide to marketing performance measurement.

Server-Side Tracking: The Strategy That Increased Data by +40% for Clinik.ch

Do you want to audit your current data loss?

Contact A-Track for an analysis of your setup and take it to the next level.

Switch to Server-Side Tracking

Questions fréquemment posées

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.

Does GTM Server speed up the site?

▾
Not automatically. Server-side only makes the page lighter if scripts are removed from the browser, for example advertising pixels replaced by server-side sends. If every pixel stays in place, the gain is small.

When scripts are removed, loading improves, which benefits user experience and, indirectly, SEO through Core Web Vitals.

Does Server-Side allow tracking everything, even without consent?

▾
No. Technically a server can receive data, but that does not change the rules: the visitor's choice in the cookie banner must be respected, in the browser and on the server alike. A refusal is still a refusal.

Server-side is there to make data more reliable and more minimal, not to collect what the visitor refused.

Does Server-Side tracking help with Email Marketing (Klaviyo/Mailchimp)?

▾
Yes, to some extent. An identification cookie set by your server on your own domain holds up better against the 7-day limit that Safari (ITP) applies to cookies set in JavaScript. Klaviyo or Mailchimp can therefore recognise returning subscribers for longer, and "Abandoned cart" or "Browse abandonment" flows trigger more often.

This tracking still requires the visitor's consent.

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.

Does Server-Side tracking improve SEO?

▾
Indirectly, yes. By moving part of the advertising scripts (Meta Pixel, TikTok Pixel, etc.) from the browser to the server, you lighten the page's code. The site can load faster, and loading speed is part of Google's page experience signals (Core Web Vitals).

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 GTM (Google Tag Manager) Server-Side?

▾
It is the server version of GTM. It allows for receiving web data, manipulating it (cleaning PII, hashing emails), and distributing it to partner APIs (Meta, Google Ads, TikTok).

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 is the monthly cost of a Server-Side infrastructure?

▾
It depends on request volume. At Stape, a free plan covers up to 10,000 requests per month, and the Pro plan costs about USD 17 per month billed annually, for up to 500,000 requests (Stape's published pricing, September 2026). On Google Cloud (Cloud Run), Google estimates about USD 45 per month per server and recommends at least two servers in production.

These hosting costs are not included in A-Track's setup and maintenance services: they come on top.

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.