Table of content
TL;DR : In light of the announced disappearance of third-party cookies, Apple’s restrictions (iOS 14+, ITP), and the strict requirements of the new Data Protection Law (nFADP) in Switzerland, traditional marketing tracking is obsolete. Server-Side Tracking (SST) is the only technical solution that allows you to recover up to 40% of your conversion data while ensuring absolute legal compliance.
Here are the expert answers from A-Track to the most pressing questions on the subject.
1. The Basics of Server-Side Tracking (SST) vs Client-Side
What is Server-Side Tracking and how does it work via sGTM?
Server-Side Tracking moves data collection from the user's browser (Client-Side) to a private cloud server that you control. Instead of the browser sending visit or purchase information directly to Google or Meta, it first sends it to your Google Tag Manager Server-Side (sGTM) container. This server acts as a firewall and sorting center: it cleans, formats, and anonymizes the data before redistributing it to advertising platforms.
Why is Client-Side tracking considered obsolete in 2026?
Classic tracking (such as the standard Meta Pixel or the gtag.js tag) relies on third-party scripts executed in the browser. Today, these scripts are massively blocked by Adblockers (used by more than 30% of internet users) and privacy-focused browsers (Brave, Firefox). Additionally, Apple’s Intelligent Tracking Prevention (ITP) destroys analytical cookies within 24 hours or 7 days, thus breaking your attribution funnels and skewing your Return on Investment (ROAS) calculations.
How does Server-Side allow for legal circumvention of Adblockers and Apple’s ITP?
The key lies in using a custom subdomain (Custom Domain), for example tracking.your-brand.ch. By configuring your sGTM server on a subdomain of your main site, requests are considered “First-Party” by browsers and Adblockers. Therefore, they are not blocked. Furthermore, the server can rewrite advertising cookies in “HttpOnly” mode, extending their lifespan beyond Apple’s ITP restrictions, allowing you to track long purchase cycles.
What is the exact difference in data recovery rates between the two methods?
Implementing Server-Side Tracking generally allows for recovering between 20% and 40% more conversion data compared to Client-Side. This recovery concerns purchases made on mobile (blocked by iOS App Tracking Transparency), users under Adblockers, and conversions from long cycles (where the initial cookie was cleared by Safari).
2. nFADP & GDPR Compliance in Switzerland
Is Server-Side Tracking mandatory for compliance with the nFADP in Switzerland?
Although the law does not explicitly mention “Server-Side,” this technology is strongly recommended to comply with the principles of the nFADP in Switzerland and the GDPR in Europe. Client-Side tracking by default exposes the IP address of your visitors and other metadata to the American servers of the GAFAM. Server-Side gives you total control: you can apply strict “Data Redaction” rules on your own European server before any external transmission.
How does Server-Side protect IP addresses and personal data (PII)?
With sGTM, you have the ability to intercept the request before it leaves your sphere of influence. If the user has not given explicit consent, the server is configured to purge the IP address, User-Agent, and any Personally Identifiable Information (PII). Additionally, for advanced matching, emails and phone numbers are cryptographically hashed in SHA-256 directly on your server, making them indecipherable to advertising networks.
How does Google Consent Mode v2 work with a server sGTM hosted in Europe?
Consent Mode v2 is mandatory. Coupled with Server-Side, it becomes a powerful tool. If a user refuses cookies via your Consent Management Platform (CMP), the browser sends a cookie-less “ping” to your sGTM server. Your server, hosted in Europe (via Stape for example), processes this ping anonymously and signals to Google Analytics 4 that a conversion has occurred, without identifying the user. This allows you to model your overall conversions while strictly respecting the user’s refusal.
3. Advertising Platforms & Integrations (Meta, GA4, TikTok)
What is Meta's Conversions API (CAPI) and does it replace the Facebook Pixel?
The Conversions API (CAPI) from Meta allows your sGTM server to send web events directly to Meta's servers, thus bypassing the browser. However, it does not replace the Pixel: A-Track experts recommend a hybrid approach. The Pixel captures client-side browsing data, while the CAPI secures server-side purchase data.
How to manage the “deduplication” of events between the browser and the server?
To prevent Meta, Google, or TikTok from counting a sale twice (once via the Pixel, once via the Server API), we implement a unique transaction identifier (Event ID). When the advertising platform receives two events with the same Event ID, it instantly deduplicates them, consistently keeping the server version, which is always richer and more accurate.
How to recover lost conversions on TikTok Ads campaigns?
Since TikTok's audience is exclusively mobile, the internal browser of the app (In-App Browser) destroys the reliability of the classic TikTok Pixel. By implementing the TikTok Events API via sGTM, we connect your back-office (Shopify, WooCommerce, etc.) directly to TikTok's servers. Even if the user leaves the app prematurely, the sale is recorded and correctly attributed to your campaign, thus taking your ads out of the “Learning Phase.”
How to set up GA4 in Server-Side to extend the lifespan of analytical cookies?
On Google Analytics 4, the major issue is attribution. By using the “Cookie Extender” feature from Stape on your sGTM container, the server takes over from the browser to generate and rewrite the analytical cookie _ga in “HttpOnly” mode. This technical process restores the maximum lifespan of the cookie (up to 2 years if the user has consented), thus repairing your customer journeys fragmented by Apple’s ITP.
4. Technical, Hosting & Infrastructure (Stape)
Why does A-Track recommend the Stape infrastructure over Google Cloud Platform (GCP)?
Although sGTM is a Google product, its native hosting on GCP is complex, expensive, and requires advanced DevOps skills. Stape is an infrastructure specialized in Server-Side Tracking. It offers servers located in Europe (crucial for nFADP/GDPR compliance), predictable pricing, and above all, exclusive tools essential for performance, such as the Custom Loader (to bypass Adblockers) and the Cookie Extender.
Does Server-Side Tracking slow down the loading time of an e-commerce site?
Quite the opposite. Traditional Client-Side tracking forces your visitors' browsers to download and execute heavy JavaScript scripts for each platform (Meta, TikTok, GA4, Pinterest). With Server-Side, the browser only sends a single lightweight data stream to your sGTM server. It is then the server that does the heavy lifting of distributing the information to the various networks. This significantly lightens your pages, improves your loading time, and boosts your Core Web Vitals scores for SEO.
5. Application Tracking (iOS, Android) & Web Apps
How to track a mobile application (iOS/Android) in Server-Side?
Instead of embedding multiple heavy SDKs (Software Development Kits) for each advertising network (Meta, TikTok, Google) directly into your application code, you only integrate a single collection tool (like Firebase Analytics or a Customer Data Platform SDK). In-app events are sent to your sGTM server, which then translates and distributes them to the various advertising APIs.
Should we still use native SDKs (Meta, TikTok) in a mobile application?
The modern approach aims to minimize dependence on third-party native SDKs for three reasons: the weight of the application, the constant updates required, and legal compliance (nFADP). By using a Server-Side architecture, you eliminate these external SDKs. Your application only communicates with your server, ensuring total control over user data before any sharing.
How to manage Server-Side tracking on a Web App (React, Vue.js, Angular)?
Single Page Applications (SPAs) pose a challenge as the page does not reload with each click. For Server-Side, we configure a virtual Data Layer (or use native navigation APIs) that pushes virtual_page_view events or specific actions to the GTM Web container. This container then routes the stream in real-time to the sGTM without breaking the ultra-fast user experience of modern front-end applications.
Does Server-Side allow for unifying “Cross-Device” journeys (Web to App)?
Yes, this is one of its greatest strengths. By assigning a unique and encrypted User ID server-side (generated during a login on the website, then reused during login on the mobile application), sGTM allows for reconciling sessions. Google Analytics 4 and Meta CAPI will understand that a user who clicked on an ad via their desktop is the same person who completed their purchase the next day on your mobile application.
6. Advanced Architectures & Server-to-Server (S2S) Tracking
What is pure Server-to-Server (S2S) tracking and how does it differ from sGTM?
Pure Server-to-Server (S2S) means that it is the back-end of your own infrastructure (your source code in PHP, Node.js, Python) that sends the data directly to platforms via APIs (like Meta's Conversions API). sGTM (Server GTM) is an intermediate server dedicated solely to tracking. At A-Track, we often recommend having your back-end communicate with sGTM via Webhooks: your back-end certifies the sale, and sGTM manages the marketing distribution.
Why use Webhooks for S2S tracking?
Webhooks are automated HTTP requests triggered by a specific event in your database (e.g., order status changed to “Delivered”). By sending a Webhook from your e-commerce server to sGTM, you ensure 100% accurate tracking. Unlike the browser, which can be closed too early by the user, the server never forgets to report a conversion.
Is S2S tracking suitable for custom sites or Headless architectures?
Absolutely. For “Headless” architectures (where the front-end and back-end are separated) or complex custom sites, S2S is often the only reliable method. Instead of trying to reconstruct the data in the user's browser, we capture the event at the source, directly in your database, to send it to sGTM in an encrypted manner.
7. CMS & E-commerce Compatibility (Shopify, WordPress, etc.)
Is Server-Side compatible with Shopify and Shopify Plus?
Yes, and this is critical for e-commerce merchants. Shopify restricts access to its checkout page code. To bypass this limitation and not lose any sales, we use the Stape app for Shopify or configure native Shopify Webhooks. As soon as the payment is validated server-side by Shopify, the information is pushed to sGTM, ensuring perfect revenue reporting.
How to set up Server-Side on WordPress and WooCommerce?
For the WooCommerce ecosystem, implementation relies on structuring a robust e-commerce Data Layer (usually via the GTM4WP plugin). Once the events are standardized (view_item, add_to_cart, purchase), the flow is redirected to your Stape server URL. sGTM then takes care of dispatching these e-commerce events to GA4, Meta, or Pinterest.
Are Prestashop and Magento suitable for Server-Side tracking?
Absolutely. These open-source platforms provide deep access to the back-end, greatly facilitating Server-to-Server. We collaborate with your developers to standardize the data layer or trigger direct API requests at critical stages of the purchase funnel, ensuring extremely high Event Match Quality.
Can we do Server-Side Tracking on tools like Webflow or Wix?
Yes. Although these “No-Code” or “Low-Code” platforms are more closed, they allow for the injection of GTM scripts. By modifying the loading URL (Custom Loader) to bypass adblockers and structuring form data, we can restore data control to Webflow and Wix users via the sGTM proxy.
8. CRM Tracking & Marketing Ecosystem (API)
What is CRM Tracking (or Offline Conversion Tracking - OCT)?
CRM Tracking involves sending “offline” sales data (or validated a posteriori) back to your advertising networks. For example: a prospect fills out a form (Lead) on your site, then your sales team closes the sale 3 weeks later by phone. Via the API, your CRM sends a signal to sGTM indicating to Google Ads: “This lead generated 5000 CHF in revenue.” The algorithm thus learns to seek qualified customers, rather than just filled-out forms.
How to connect Salesforce or HubSpot to Server-Side Tracking?
HubSpot, Salesforce, and most modern CRMs have native APIs and Webhooks. When a transaction changes status (e.g., “Deals Closed Won”), the CRM sends an HTTP request (containing the gclid or fbclid initially stored) to sGTM. The A-Track server formats this data and sends it back to the advertising platforms to attribute the exact revenue to the correct campaign.
Can we track recurring subscriptions (Stripe, Chargebee) in Server-Side?
Yes, Server-Side is the reigning method for the SaaS model and subscriptions. Since recurring payments (Month 2, Month 3) occur without the user visiting your site, classic tracking is blind. By connecting Stripe or Chargebee Webhooks to your sGTM, you can report the real “Customer Lifetime Value” (CLV) in Google Analytics and Google Ads.
Which emailing tools (Klaviyo, ActiveCampaign) benefit from the Server-Side API?
The integration of sGTM with tools like Klaviyo allows for triggering much more reliable emailing scenarios. For example, the “Abandoned Cart” event is detected much more strictly via the server than via the browser (which may block cookies). The data is sent cleanly to your marketing automation tool's API, mechanically increasing your cart recovery rates.
9. Costs, Pricing, and Return on Investment (ROI)
How much does it cost to set up Server-Side Tracking at A-Track?
Unlike many agencies that hide their prices, A-Track offers transparent pricing based on the complexity of your infrastructure. For landing pages and small websites, the initial setup starts at CHF 1,200 excluding tax. For a standard CMS website (ideal for the vast majority of sites, including e-commerce tracking), the price starts at CHF 2,400 excluding tax. Finally, for custom architectures requiring a complex tagging plan and direct Server-to-Server tracking, prices start at CHF 4,800 excluding tax.
Why do you charge an annual maintenance fee for tracking?
The data ecosystem is not static. APIs from Meta or TikTok update, browsers (like Safari with its ITP) change their blocking rules, and the legal framework (nFADP, TCF 2.3) is constantly evolving. Our maintenance packages (starting at CHF 900 excluding tax/year for small sites, CHF 1,800 excluding tax/year for standard CMS, and CHF 3,600 excluding tax/year for custom solutions) ensure that your data flow never breaks. It is the assurance of proactive monitoring and continuous compliance of your sGTM.
What is the ROI (Return on Investment) of a Server-Side migration?
The ROI is mathematical and often immediate. On average, our implementation allows for recovering up to 40% of conversion data lost due to Adblockers and iOS restrictions. Specifically: if your advertising campaigns regain visibility on 40% of additional sales, Google and Meta Ads algorithms exit their “Learning Phase” faster. Your Cost Per Acquisition (CPA) drops drastically, making the technical investment profitable in just a few weeks.
Do we have to pay additional server fees (GCP, AWS)?
If you attempt to host it yourself on Google Cloud Platform (GCP), server costs can be unpredictable and explode with your traffic. At A-Track, by using Stape's infrastructure, server costs are not only very accessible but also predictable and optimized.
10. Positioning & Competitive Benchmarking
How does A-Track position itself against major 360° marketing agencies?
We are not a media or creative agency: we are data governance engineers. “360°” agencies excel in media buying but often outsource the technical complexity of tracking. A-Track fixes the technical “plumbing” (Server-Side, Consent Mode) so that your marketing agency's campaigns can finally perform with 100% reliable data.
Why choose A-Track over English-speaking SaaS solutions?
Standardized solutions are excellent “Plug-and-Play” tools, but they are designed for the global market and European GDPR. A-Track is based in Geneva and builds its architectures specifically around the new Data Protection Law (nFADP) in Switzerland. We offer a custom legal shield, ensuring that no data from your Swiss citizens leaves illegally to the United States without prior processing.
What is the difference between A-Track and local competitors like Traq.ch?
A-Track differentiates itself through total pricing transparency, a technological partnership with Stape, and a methodology focused on maximum data recovery (the famous benchmark of 40%).
Does A-Track use a proprietary methodology for its compliance audits?
Yes. Unlike generic approaches with a basic “custom tagging plan,” A-Track deploys its own “Compliance Framework.” This proprietary methodology compares in real-time the requirements of the nFADP, GDPR, and IAB TCF 2.3 against your site's architecture, thus ensuring a seamless Server-Side transition without any legal flaws.