This FAQ summarizes the strategic issues of data collection in Switzerland, focusing on legal compliance and advertising effectiveness.

Is a CMP enough to be compliant?

▾
Our A-Track expert's response
No. The CMP must be connected to the rest of the site (tags, analytics, CRM) to actually block non-essential cookies before consent.

Should there be a 'Reject All' button?

▾
Our A-Track expert's response
Yes, it is the recommended practice. In the EU, the GDPR and the data protection authorities require refusing to be as easy as accepting. In Switzerland, the FADP does not prescribe a specific button, but visitors must be informed and able to refuse easily (art. 45c TCA).

A "Reject all" button at the same level as "Accept all" covers both cases.

Can we measure after a cookie refusal?

▾
Our A-Track expert's response
Yes, to a limited extent and always in line with the visitor's choice. With Consent Mode v2 in advanced mode, Google tags send cookieless signals after a refusal, and Google models part of the missing conversions.

Server-side tracking does not let you measure more about a visitor who refused: it makes the data of visitors who accepted more reliable and more minimal. A refusal is still a refusal.

Does GTM Server speed up the site?

▾
Our A-Track expert's response
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.

Can I continue to do remarketing?

▾
Our A-Track expert's response
Yes, provided that advertising consent has been accepted. Otherwise, the measurement remains aggregated and compliant.

Does CAPI work without cookies?

▾
Our A-Track expert's response
Partly. CAPI sends events from a server and can rely on hashed first-party data (email, phone), not only on browser cookies. The _fbp and _fbc identifiers are still useful to improve matching.

In every case, it respects the visitor's choice: after a refusal, no marketing event is sent to Meta.

What is the difference between audit and consulting?

▾
Our A-Track expert's response
The audit identifies problems. Consulting assists in their resolution and structures your data governance.

Do you offer certified training courses?

▾
Our A-Track expert's response
Yes, with a final assessment and official A-Track certificate.

What is the Meta Pixel and what is it used for?

▾
Our A-Track expert's response
The Meta Pixel is a code that you install on your website to track the actions of your visitors (purchases, forms, clicks). This data allows Meta to optimize your ads, measure your conversions, and create more effective audiences on Facebook and Instagram.

Is the Meta Pixel compliant with the FADP in Switzerland?

▾
Our A-Track expert's response
It can be, provided it is configured properly. In Switzerland, Art. 45c of the Telecommunications Act requires informing visitors about cookies and letting them refuse; the FADP requires transparency about the purposes and recipients of the data, Meta included. For EU visitors, the GDPR and the ePrivacy Directive require prior consent.

In practice, the simplest approach is to fire the Pixel only after consent, through your CMP. Server-side tracking lets you control and limit the data sent to Meta, but it does not replace consent: a refusal is still a refusal.

How to install LinkedIn Ads tracking on my site?

▾
Our A-Track expert's response
It is sufficient to install the Insight Tag via Google Tag Manager with your LinkedIn Partner ID, then add a conversion tag with the Conversion ID for each important action (form, purchase, key page). For reliable tracking, combine client-side and server-side API.

Why use server-side tracking for LinkedIn Ads?

▾
Our A-Track expert's response
Because it makes measurement more robust. Events go through your own subdomain (first-party), then are sent to LinkedIn through its Conversions API. Measurement is less exposed to browser restrictions and ad blockers, and LinkedIn receives more complete conversions to optimise your campaigns.

The server also lets you filter data before it is sent. It always respects the visitor's choice: a refusal is still a refusal.

Is the cookie banner mandatory for a 100% Swiss site?

▾
Our A-Track expert's response
Not strictly under the FADP, but in practice almost always. In Switzerland, Art. 45c of the Telecommunications Act requires informing visitors about cookies and letting them refuse, and the FADP requires transparent information (privacy policy). Swiss law therefore does not impose a prior-consent banner for a purely Swiss audience.

However, Google has applied its EU user consent policy to Switzerland since 31 July 2024: to use Google Ads fully (remarketing, audiences, conversion measurement), you must collect consent and pass it on through Consent Mode v2. As soon as you also target EU visitors, prior consent is required. For a commercial website, a CMP remains the safest option.

Who is responsible in case of a fine: the agency or the client?

▾
Our A-Track expert's response
In Switzerland, FADP fines (up to CHF 250,000) target the natural person responsible for an intentional violation, usually within the client company, and are imposed by cantonal criminal authorities. Where identifying that person would require disproportionate investigation, the company itself can be fined up to CHF 50,000 (Art. 64 FADP).

The agency, for its part, may face contractual liability if it failed in its duty to advise or performed its mandate poorly. In the EU, the GDPR penalises the company (controller or processor).

What is Google Consent Mode v2?

▾
Our A-Track expert's response
It is a mechanism that lets your Google tags (Analytics, Ads) adjust their behaviour based on the visitor's choice in the cookie banner. Version 2 adds the ad_user_data and ad_personalization parameters.

Google has required it for EEA data since March 2024 and has also applied it to Switzerland since 31 July 2024: without consent signals, advertising features (remarketing, audiences, conversion measurement) are limited.

Can I use a free plugin for compliance?

▾
Our A-Track expert's response
It is not recommended for a commercial website. Free plugins often keep up less well with legal and technical changes (Consent Mode v2, IAB TCF 2.3, new cookies to categorise). A professional CMP such as Cookie-Script automates cookie scanning, preventive tag blocking and the passing of signals to Consent Mode.

Whatever the tool, test it: no non-essential tag should fire after a refusal.

Is it mandatory if I only target Switzerland?

▾
Our A-Track expert's response
Yes, if you use Google Ads. It is not Swiss law that requires it but Google's policy: since 31 July 2024, Google has applied its EU user consent policy to Switzerland. Even for a small Vaud business selling only locally, without Consent Mode v2, remarketing, audiences and conversion measurement are limited.

On the legal side, Switzerland requires information and a right to refuse (Art. 45c of the Telecommunications Act); prior consent is required for EU visitors.

Will I lose data by enabling it?

▾
Our A-Track expert's response
Quite the opposite. Without Consent Mode v2, your Google Ads audiences empty out and measurement degrades. By enabling it, especially in advanced mode (the one A-Track recommends), tags send cookieless signals after a refusal, and Google can model part of the missing conversions.

For EU visitors, have this setting validated by your DPO.

Does this replace Server-Side Tracking?

▾
Our A-Track expert's response
No, the two are complementary. Consent Mode passes the visitor's choice on to Google tags. Server-side handles how data travels: first-party measurement on your own subdomain, more resilient to browser restrictions and ad blockers, and data filtering before sending.

Combined, they give reliable measurement that always respects the visitor's choice: a refusal is still a refusal.

What is the major difference between the FADP (Switzerland) and the GDPR (EU) for a website?

▾
Our A-Track expert's response
Although very similar, the FADP (Federal Act on Data Protection) favors a risk-based and transparency approach, while the GDPR imposes a stricter framework on prior consent. However, if you are targeting European customers, you must comply with the GDPR, which is the highest standard.

My company is 100% Swiss, do I need to install a cookie banner?

▾
Our A-Track expert's response
In most cases, yes. In Switzerland, Art. 45c of the Telecommunications Act requires informing visitors about cookies and letting them refuse, and the FADP requires transparent information about processing.

In addition, Google has applied its EU user consent policy to Switzerland since 31 July 2024: without a banner (CMP) connected to Consent Mode v2, Google Ads advertising features are limited, even for a Swiss audience. If you also target the EU, prior consent is mandatory.

What is the "Privacy by Design" imposed by the FADP?

▾
Our A-Track expert's response
This means that data protection must be integrated from the design stage of your website or marketing campaigns, and not added at the end. Tracking must be configured to collect the minimum amount of necessary data.

What are the financial risks in case of non-compliance with the FADP?

▾
Our A-Track expert's response
The GDPR provides for fines against companies of up to EUR 20 million or 4% of worldwide annual turnover (Art. 83 GDPR). The FADP works differently: it provides for criminal fines of up to CHF 250,000 against the responsible individuals, for intentional breaches of certain duties (information, cooperation, due diligence, professional secrecy, Art. 60 to 63 FADP).

These fines are imposed by cantonal criminal authorities; the FDPIC investigates and orders measures but does not impose fines. Indirect costs come on top: rushed remediation, reputational damage, limited advertising features.

Is it illegal to use Google Analytics in Switzerland or Europe?

▾
Our A-Track expert's response
No, it is not illegal per se, but the default configuration is problematic. You need to collect consent where it is required, shorten data retention, limit the data sent and, ideally, route collection through server-side tracking on your own subdomain: the visitor's IP address is then no longer passed directly to Google's servers in the United States.

What is a CMP (Consent Management Platform)?

▾
Our A-Track expert's response
It is the software that manages the cookie banner (e.g., Cookie-Script, Cookiebot). It blocks tracking scripts until the user has given their consent and stores proof of consent.

Is data compliance a hindrance to marketing performance?

▾
Our A-Track expert's response
No, it's the opposite. "Clean" and compliant tracking (especially via Server-Side) improves the quality of the collected data as it is filtered and structured, increasing the trust of advertising algorithms.

Should I update my privacy policy?

▾
Our A-Track expert's response
Absolutely. It must list all the tracking tools used, the purpose of the data collection, the location of data storage, and the rights of users. It is a requirement under the FADP and GDPR.

What is the "Right to be Forgotten"?

▾
Our A-Track expert's response
It is the right for a user to request the deletion of all their personal data from your databases (CRM, Analytics, marketing tools). Your tracking infrastructure must allow for this action.

What is "Client-Side" (classic) tracking?

▾
Our A-Track expert's response
This is the traditional method where the user's browser (Chrome, Safari) directly sends data to platforms (Facebook, Google). It has become fragile due to ad blockers and browser restrictions (ITP).

What is "Server-Side" tracking?

▾
Our A-Track expert's response
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?

▾
Our A-Track expert's response
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.

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

▾
Our A-Track expert's response
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.

Why do my cookies expire after 24 hours or 7 days on Safari?

▾
Our A-Track expert's response
Because of Apple's ITP (Intelligent Tracking Prevention). Safari blocks third-party cookies and caps first-party cookies created in JavaScript at 7 days, or even 24 hours when the visitor arrives through a link carrying tracking parameters (for example gclid or fbclid).

A cookie set by your server in the HTTP response, on your own subdomain, can last longer. Be careful: since Safari 16.4, if the server setting the cookie has an IP address too different from your website's, Safari caps it at 7 days as well. The tagging server architecture must be planned accordingly.

What is GTM (Google Tag Manager) Server-Side?

▾
Our A-Track expert's response
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 "Stape.io"?

▾
Our A-Track expert's response
Stape is a hosting provider specialised in server-side Google Tag Manager. It is often chosen over Google Cloud (GCP) because it is simpler to configure, with clear pricing, and because it offers ready-to-use modules (power-ups): loading GTM from your own domain (Custom Loader), anonymisation, keeping first-party identifiers (Cookie Keeper).

These tools make measurement more robust but change nothing about consent: a refusal is still a refusal.

What is the difference between Stape and Google Cloud for tracking?

▾
Our A-Track expert's response
Google Cloud is a raw infrastructure billed by usage (complex). Stape is a "turnkey" solution optimized for GTM, with servers in Europe, facilitating GDPR/FADP compliance.

Does Server-Side tracking improve SEO?

▾
Our A-Track expert's response
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).

Is it complicated to migrate to Server-Side?

▾
Our A-Track expert's response
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.

Why use Cookie-Script as a CMP?

▾
Our A-Track expert's response
It is a robust, cost-effective solution that is easy to integrate with GTM. It offers "Geo-Targeting" features (displaying the GDPR banner to Europeans but a lighter version to the Swiss if desired) and integrates well with Google Consent Mode V2.

What is the Facebook/Meta Conversion API (CAPI)?

▾
Our A-Track expert's response
It is the interface for sending events (purchase, lead) directly from your server to Meta, alongside the browser pixel. Both streams are deduplicated using a shared event ID (event_id).

CAPI makes measurement more resilient to browser restrictions, ad blockers and the effects of iOS 14.5 (App Tracking Transparency). It still respects the visitor's choice: a refusal of consent remains a refusal.

What are Google's "Enhanced Conversions"?

▾
Our A-Track expert's response
When a conversion occurs, the tag sends Google hashed first-party data (SHA-256), such as the email or phone number entered in the form. Google matches it with signed-in Google accounts to link the conversion to the right ad click, even when the cookie is no longer available.

This personal data should only be sent with the visitor's consent (the ad_user_data parameter of Consent Mode v2) and clear information in your privacy policy.

Should I use a custom subdomain (e.g., data.mysite.com)?

▾
Our A-Track expert's response
Yes, it is strongly recommended for server-side. Hosted on your own subdomain, the tracking server can set first-party cookies through HTTP headers. They generally last longer than cookies set in JavaScript, which Safari (ITP) caps at 7 days.

They are not immune to restrictions, though: Safari and Firefox keep evolving their protections (Safari can also cap these cookies, for example when the server's IP address is not close to your website's), some blockers filter these subdomains, and a refusal of consent remains a refusal.

What is the "Data Layer"?

▾
Our A-Track expert's response
It is an invisible JavaScript object on your site that contains all the key information (product price, ID, category, user email). GTM reads this Data Layer to send the right information to marketing tools.

Does Server-Side work with Shopify / WordPress?

▾
Our A-Track expert's response
Yes. Plugins (like GTM4WP or Shopify Data Layer apps) facilitate sending data to the GTM Server-Side container.

Does "Cookieless Tracking" mean the end of tracking?

▾
Our A-Track expert's response
No. "Cookieless" mainly means ending the dependence on third-party cookies. Safari and Firefox already block them; Google, however, gave up in April 2025 on removing them from Chrome, where they remain available.

The underlying trend is unchanged: measurement relies more and more on first-party data, cookies set by your own domain and server-side sends (conversion APIs). We measure differently, while respecting consent.

What is a Stape "Power-Up"?

▾
Our A-Track expert's response
They are add-on modules offered by Stape to simplify technical tasks: for example Cookie Keeper (keeps and restores first-party identifiers when the browser deletes them), Custom Loader (loads GTM from your own domain) or anonymising data before it is sent.

They are always used in line with the visitor's choice.

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

▾
Our A-Track expert's response
Yes. You can send data to Facebook, TikTok, Pinterest, LinkedIn, Klaviyo, or even your own SQL/BigQuery database from the same server.

What is the monthly cost of a Server-Side infrastructure?

▾
Our A-Track expert's response
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.

I have a showcase site, is advanced tracking necessary?

▾
Our A-Track expert's response
For a simple showcase without advertising, basic Analytics is sufficient. However, if you are doing SEO or local campaigns, understanding user behavior (time spent, clicks on "contact") through GTM remains valuable.

B2B Lead Gen: How to track lead quality?

▾
Our A-Track expert's response
You should not only track the form submission. You need to use Server-Side to send an "Offline Event" to Google/Facebook when the lead becomes a "qualified" or "signed" client in your CRM.

E-commerce: Why do my Analytics sales not match my Back-office?

▾
Our A-Track expert's response
It is often caused by ad blockers, cookie refusals, browser restrictions or visitors leaving the "Thank you" page before the tags load.

Server-side tracking makes purchase reporting more reliable and significantly narrows this gap. A residual gap is normal: a refusal of consent remains a refusal, and Analytics does not replace your accounting.

What is POAS (Profit On Ad Spend)?

▾
Our A-Track expert's response
Instead of measuring ROAS (Revenue / Ad Spend), advanced tracking allows you to send the actual margin to advertising tools. You optimize your ads for profit, not just for sales volume.

How to track a clicked phone number?

▾
Our A-Track expert's response
Through GTM, we configure a trigger on tel: links. To go further, we use dynamic "Call Tracking" to know which keyword generated the call.

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

▾
Our A-Track expert's response
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.

How to manage tracking if I have multiple domains?

▾
Our A-Track expert's response
Two cases must be distinguished.

Between subdomains of the same domain (www.your-site.ch and shop.your-site.ch), Google cookies are shared automatically: no cross-domain configuration is needed.

Between separate domains (your-site.ch and your-site.fr, or a payment or booking provider's domain), cross-domain measurement must be configured carefully in GTM and GA4 so the visitor's session is not lost, and redirects and consent must be checked on each domain.

Can we track AJAX forms without a thank you page?

▾
Our A-Track expert's response
Yes, this is a specialty of the implementation via GTM. We listen for the form's "success" in the code or the Data Layer to trigger the conversion, without needing a specific URL.

Is marketing attribution 100% reliable?

▾
Our A-Track expert's response
Never. It's a mathematical model. However, Server-Side tracking provides the most raw and complete data possible, making GA4 or Facebook attribution models much more accurate.

What is the "User ID"?

▾
Our A-Track expert's response
It is a feature that allows recognizing that a mobile user is the same person as on a computer, provided they have logged into their customer account. This is essential for the cross-device customer journey.

Why is tracking maintenance necessary?

▾
Our A-Track expert's response
The web changes all the time: browser updates, legal developments, changes to Meta and Google APIs, new releases of the website or the CMP. Without monitoring, a setup that works today can stop working overnight, often without anyone noticing.

What does a tracking audit consist of?

▾
Our A-Track expert's response
An expert analyzes your GTM account, GA4, and your pixels. They check for duplicates, compliance of cookie banners, data loss (Data Discrepancy), and the security of collected data.

What to do if my web agency has "badly" installed the tracking?

▾
Our A-Track expert's response
It is common, and it is not a criticism: advanced tracking is a profession in its own right, distinct from web development. It is best to bring in a specialist (such as A-Track) to audit the existing setup, clean up the tags, implement a clean Data Layer and, where relevant, migrate to server-side GTM, without touching the site's design.

How long does Server-Side compliance and installation take?

▾
Our A-Track expert's response
For a standard site, it takes between 3 to 7 business days for the audit, configuration, testing phase, and going live.

Does maintenance include the management of the CMP (Cookie banner)?

▾
Our A-Track expert's response
Yes. Maintenance services often include a monthly scan of cookies to ensure that new plugins installed on the site do not drop illegal cookies without being blocked by the banner.

What is the added value of a Swiss expert for the FADP?

▾
Our A-Track expert's response
Knowledge of local subtleties. For example, knowing how to configure geolocation to apply the strict rules of the GDPR to EU visitors while maintaining more flexibility for Swiss visitors (if the strategy allows it).

Is Server-Side tracking reserved for large companies?

▾
Our A-Track expert's response
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.

What deliverables do we receive after a tracking mission?

▾
Our A-Track expert's response
Generally: a tagging plan, access to the clean GTM container, documentation of the architecture implemented, and a technical compliance report.

Can I manage my tracking alone with YouTube tutorials?

▾
Our A-Track expert's response
For a basic setup, yes. For Server-Side, strict FADP compliance, and conversion APIs, the risk of error (double counting, data loss, illegality) is very high without a technical background.

What is the first step to working with experts like a-track.ch?

▾
Our A-Track expert's response
The first step is always the Audit. It is impossible to build a solid house without checking the condition of the ground. The audit allows you to list security flaws and opportunities for data improvement.

Can we host Google Tag Manager Server-Side at Infomaniak?

▾
Our A-Track expert's response
Yes. Google provides an official Docker image of server-side GTM, which can be installed on Infomaniak's cloud infrastructure in Switzerland (Jelastic Cloud or a virtual server).

This option greatly reduces exposure to foreign law such as the US CLOUD Act, which can appeal to organisations with strict confidentiality requirements (banking, healthcare, public sector). It does, however, mean heavier technical operations (image updates, availability, monitoring). The choice should be made with the company's compliance team.

Is Google Cloud Platform (Zurich) compliant with the FADP for tracking?

▾
Our A-Track expert's response
Google Cloud's Zurich region (europe-west6) hosts data in Switzerland with a strong level of technical security, but Google remains a US company subject to US law (CLOUD Act). For most Swiss commercial companies, it is a defensible option, especially as Google is certified under the Swiss-U.S. Data Privacy Framework, in force since 15 September 2024.

For data subject to professional secrecy (banking, healthcare), a host operated by a Swiss company, such as Infomaniak, greatly reduces the risk of extraterritorial access. The decision lies with the compliance team or the DPO.

Can a Swiss bank use Google Ads and Facebook Ads?

▾
Our A-Track expert's response
Yes, for its public website and under strict rules. A-Track never tracks inside e-banking or back-offices: measurement stops at the public website.

On that website, marketing tags fire only after the visitor agrees in the CMP; a refusal is still a refusal. On the server side, A-Track processes data only for statistical purposes and with consent, and filters every request before anything is sent (sensitive parameters and identifiers removed or minimised). The setup should be validated by the bank's compliance team.

How to reconcile digital marketing and banking secrecy in Switzerland?

▾
Our A-Track expert's response
Through a strict scope and data minimisation. No measurement inside e-banking or back-offices: only the public website is concerned, and only with the visitor's consent.

On the server side, requests are cleaned before anything is sent: a descriptive URL (for example bank.ch/mortgage-geneva) is replaced by a generic code (for example prod_id_123), and sensitive parameters are removed. Recipients therefore receive as little information as possible.

This greatly reduces the risk of profiling without eliminating it: it must be validated by the bank's compliance team with regard to banking secrecy (Art. 47 Banking Act).

How to track Chinese (WeChat) and Western clients in the same tool?

▾
Our A-Track expert's response
To unify data from WeChat (China) and from Google or Meta (the West), luxury houses can rely on a centralised server-side "hub". This server acts as a switchboard: it receives data from the different regions, handles local specifics (such as Google services being blocked in China) and consolidates everything in a data warehouse (for example BigQuery) for a global view of ROI.

Each region keeps its own rules: consent, data transfers and China's Personal Information Protection Law (PIPL) must be addressed from the design stage.

What is the impact of ITP (Safari) on luxury watch sales?

▾
Our A-Track expert's response
Apple's ITP caps first-party cookies created in JavaScript at 7 days in Safari (24 hours in some cases when arriving through a tracking link). Yet the decision to buy a luxury watch often takes several weeks, even months: the link between the ad and the purchase is lost, and the performance of digital campaigns is underestimated.

First-party measurement on your own subdomain (server-side), with cookies set by the server, makes attribution more robust, provided the server is properly aligned with your domain, and always in line with the visitor's choice.

What documents does the FDPIC request during an FADP audit?

▾
Our A-Track expert's response
The FDPIC has no fixed list, but during an investigation (Art. 49 and 50 FADP), five documents often come up:

1) The record of processing activities (Art. 12 FADP), from which companies with fewer than 250 employees are partly exempt.
2) Proof of consent choices, where you rely on consent (EU visitors, Google's policy).
3) The safeguards for data transfers outside Switzerland (Art. 16 FADP, for example the Swiss-U.S. DPF or standard clauses) and, if the processing is high-risk, an impact assessment (Art. 22 FADP).
4) Technical proof that non-essential trackers respect the visitor's choice (data protection by design and by default, Art. 7 FADP).
5) The processing agreements with your service providers (Art. 9 FADP).

Who pays the FADP fine in case of non-compliance: the company or the director?

▾
Our A-Track expert's response
The FADP targets the natural person responsible for an intentional violation (for example the person who took the decision within the company), not automatically the director. The fine can reach CHF 250,000 and is imposed by cantonal criminal authorities; the FDPIC itself does not impose fines.

Where identifying the responsible person would require disproportionate investigation, the company can be fined up to CHF 50,000 (Art. 64 FADP). The European GDPR, by contrast, penalises the company.

Why do my Performance Max (PMax) campaigns lack stability?

▾
Our A-Track expert's response
PMax instability often comes from a lack of clean data. If your tracking loses too many conversions (browser restrictions, ad blockers, misconfigured conversions), the algorithm lacks signals to learn from.

To stabilise PMax, feed it reliable and regular conversions: first-party server-side tracking, enhanced conversions (hashed first-party data, with consent) and Consent Mode v2 in advanced mode, which lets Google model part of the conversions of visitors who refuse.

What is POAS and how does it complement ROAS?

▾
Our A-Track expert's response
ROAS (Return on Ad Spend) relates revenue to advertising spend; POAS (Profit on Ad Spend) relates margin to it. By sending a margin-based conversion value (for example via server-side, which can enrich each purchase with product costs), you can ask Google Ads bidding to optimise for profit rather than sales volume alone.

ROAS remains useful to track revenue; POAS adds the profitability view.

How to improve the quality score of my audiences (Match Rate)?

▾
Our A-Track expert's response
By sending hashed first-party data (email, phone), with the visitor's consent, through conversion APIs (for example Meta CAPI) and Google's enhanced conversions. The higher the match rate, the better the platforms link your conversions to their users, which helps their algorithms optimise.

Check the quality of the data you send (format, normalisation before hashing) in the platforms' diagnostic tools, for example Event Match Quality at Meta.

Does Apple's ITP (Safari) impact luxury sales?

▾
Our A-Track expert's response
Yes, especially when the purchase cycle is long. Safari (ITP) caps cookies set in JavaScript at 7 days. Yet buying a luxury watch is often decided over several weeks or even months: the visit that sparked the interest is no longer linked to the sale.

Server-side tracking on your own subdomain lets you set longer-lasting cookies and better preserve attribution, while respecting the visitor's consent.

Does Server-Side Tracking expose my server to security vulnerabilities?

▾
Our A-Track expert's response
No, if it is properly configured. The GTM Server-Side container operates in an isolated environment (Docker/Sandboxed). It does not have direct access to your client database or back-office; it only receives filtered HTTP requests.

What is the ROI of a tracking compliance project?

▾
Our A-Track expert's response
There is no universal figure: it depends on your advertising budget, the share of conversions currently lost or misattributed, and your margin.

To estimate it, compare your back-office sales or leads over one month with those reported in Google Ads, Meta or GA4, quantify the gap, then weigh it against the project cost (setup and maintenance). As a benchmark, based on our measurements across more than 100 installations (Stape Analytics), server-side tracking recovers 30 to 80% more data depending on the site, around 40% on average: an order of magnitude, not a guarantee. On top of that come gains that are harder to quantify but real: lower legal risk and decisions based on reliable data.

How are your services billed to my clients?

▾
Our A-Track expert's response
Two models are available:

Reseller: You include our service (Audit or Setup) in your overall quote, with your margin. We invoice you as a subcontractor.

Business referrer: You put us in direct contact with the client for the Data part. We handle the contract and invoicing, and ensure perfect coordination with your media/web teams.

Do you help with sales during the pre-sales phase?

▾
Our A-Track expert's response
Absolutely. We can support your sales team during client pitches to answer advanced technical questions (CIO, DPO) and reassure the prospect about the security and compliance of the project.

If the tracking breaks, who is responsible towards the client?

▾
Our A-Track expert's response
If the client has subscribed to our Annual Maintenance offer, A-Track takes technical responsibility for the proper functioning of the tags and commits to response times (SLA). This relieves the agency of the pressure of technical "after-sales service".

My business only targets Switzerland (under the FADP). Am I really required to switch to the IAB TCF 2.3?

▾
Our A-Track expert's response
No, in most cases. Neither the FADP nor the GDPR requires the IAB TCF. Google requires it from publishers who monetise their site or app with its ad networks (AdSense, Ad Manager, AdMob): they must use a certified CMP integrated with the TCF, including for Swiss traffic since 31 July 2024. Since 1 March 2026, only version 2.3 is valid.

For an advertiser using Google Ads and GA4 on its own website, what matters is Consent Mode v2: your CMP must pass the visitor's choice on to Google, whether or not it uses the TCF. If you display third-party advertising, have your case checked.

What is the "disclosedVendors" signal and does it affect my SEO?

▾
Our A-Track expert's response
The disclosedVendors segment, mandatory in TCF 2.3, records in the consent string (TC String) which partners (vendors) were shown to the user in the banner.

It has no direct effect on search rankings. Indirectly, a CMP loading hundreds of unnecessary partners makes the banner heavier and can weigh on page loading; Core Web Vitals, however, are only one signal among many for Google. Good practice: keep only the partners you actually use in your list.

How can I check whether my cookie banner (CMP) is ready for TCF 2.3?

▾
Our A-Track expert's response
This check mainly concerns websites that use the TCF, for example to display third-party advertising. Since 1 March 2026, only version 2.3 is valid.

In your CMP interface (Cookiebot, Didomi, Usercentrics, etc.), open the IAB framework settings and check:
1) that the active version is 2.3;
2) that the disclosedVendors segment is generated.

Take the opportunity to clean up your vendor list and disable the partners you do not use. Finally, use Tag Assistant to confirm that your Google tags receive the consent signals.

What is Event Match Quality (EMQ) on Meta?

▾
Our A-Track expert's response
It is a score out of 10 assigned by Meta to assess the quality of customer data (Email, IP, First Name, etc.) sent with each conversion event via the API. The higher the score, the better Meta is able to identify the Facebook or Instagram user who made the purchase, thereby optimizing the delivery of your ads.

Should I remove the Facebook Pixel from my site if we are using the Conversions API?

▾
Our A-Track expert's response
No, definitely not. Meta and A-Track's best practices involve using a "Hybrid" approach (Pixel + API). The Pixel handles browser data (like scroll depth), while the API secures crucial data (purchases). The key is to set up perfect deduplication via the Event ID to avoid skewing the numbers.

How much does Stape server hosting for Meta CAPI cost?

▾
Our A-Track expert's response
Server-side hosting is now affordable. Stape offers a free plan up to 10,000 requests per month, then a Pro plan at about USD 17 per month billed annually, for up to 500,000 requests (Stape's published pricing, September 2026). The right plan depends on your traffic.

At A-Track, hosting is billed separately: it is included neither in the setup nor in the annual maintenance.

Is Meta CAPI compatible with the Swiss FADP?

▾
Our A-Track expert's response
Yes, if it is configured properly. CAPI through an intermediary server lets you control precisely which data is sent to Meta (minimisation, hashing, removal of sensitive parameters).

It does not replace consent: if the visitor refuses, no marketing event is sent to Meta, neither through the Pixel nor through the server. Also name Meta as a recipient in your privacy policy (FADP); for EU visitors, prior consent is required.

How long does it take to implement Meta CAPI via sGTM?

▾
Our A-Track expert's response
The complexity varies depending on your CMS and the state of your Data Layer. A clean setup (server creation, sGTM configuration, deduplication, testing, and validation) by our experts typically takes between a few days and two weeks.

Does GA4 Server-Side replace the classic version?

▾
Our A-Track expert's response
No, it is an evolution of the collection method. You still use the same Google Analytics 4 interface to read your reports. What changes is the "pipe" feeding those reports: more robust, cleaner, and easier to control from a compliance standpoint thanks to data filtering before sending. It does not remove the need for consent.

If we use GA4 Server-Side, do we still need a cookie banner?

▾
Our A-Track expert's response
Yes. Server-side does not replace the banner: you must still inform visitors and respect their choice (right to refuse in Switzerland under Art. 45c of the Telecommunications Act, prior consent for EU visitors, Google's consent policy applied to Switzerland since 31 July 2024).

The server does, however, let you enforce that choice more strictly and filter data before it is sent. With Consent Mode v2 in advanced mode, Google tags send cookieless signals after a refusal, from which Google models part of the conversions.

Why use Stape instead of Google Cloud Platform (GCP) for sGTM?

▾
Our A-Track expert's response
Because hosting on GCP requires cloud administration skills (instances, scaling, domains, monitoring) and costs more for moderate volumes: Google estimates about USD 45 per month per server and recommends at least two servers in production.

Stape offers a turnkey infrastructure, clear pricing and ready-to-use modules (Custom Loader, Cookie Keeper, anonymisation). GCP remains relevant for very high volumes or teams that already run their own cloud.

Does GA4 Server-Side fix "Direct Traffic" issues?

▾
Our A-Track expert's response
Only partly. An abnormal rise in "Direct" traffic in GA4 has several possible causes: cookies shortened by Safari's ITP, journeys that pass through another domain (payment, booking), redirects that lose the referrer, links without UTM parameters (emails, apps).

Cookies set by the server on your own subdomain can reduce the first cause, provided the server is properly aligned with your domain. The others are fixed through configuration (cross-domain measurement, UTMs, redirects).

How long does it take to migrate my GA4 to Server-Side?

▾
Our A-Track expert's response
If your Data Layer (Client-Side) is already clean and standardized, configuring the Stape server, sGTM tags, and "Data Redaction" filters usually takes between one and two weeks, including testing (QA) phases.

Do I need the Events API if I only use TikTok for awareness?

▾
Our A-Track expert's response
Not necessarily, but it is still useful. For traffic or awareness campaigns, the Events API makes reporting of events such as page views more robust against browser restrictions and ad blockers, which better feeds your retargeting audiences.

It always respects the visitor's choice: without consent, no event and no audience. If you do no retargeting at all, the Pixel alone may be enough.

Is the TikTok Pixel removed with this method?

▾
Our A-Track expert's response
No. We use a hybrid setup: the Pixel collects events in the browser and the Events API also sends them from the server, which makes measurement more robust. A shared identifier (event_id) lets TikTok deduplicate events and avoid double counting. Both channels follow the same consent choice.

Does Server-Side slow down my e-commerce site?

▾
Our A-Track expert's response
No, and it can even make it lighter, under one condition. The server-side container runs on a separate server, with no load on your website. The speed gain only appears if scripts are removed from the browser, for example advertising pixels replaced by server-side sends.

A lighter site benefits user experience and, indirectly, SEO.

Is the data sent via the TikTok API secure?

▾
Our A-Track expert's response
Yes, if the architecture is well designed. Personal data such as email or phone number is normalised then hashed with SHA-256 on your server before being sent to TikTok, and you choose exactly which fields are transmitted.

Be careful: hashing is not encryption. Hashed data remains pseudonymised personal data under the FADP and the GDPR, since the platform can match it with its own users. It should therefore only be sent with the visitor's consent.

How to keep this infrastructure up to date?

▾
Our A-Track expert's response
TikTok's APIs, GTM templates and Stape's recommendations change regularly. You therefore need to monitor the data flow (alerts on event volumes, conversion checks) and apply updates.

That is the purpose of A-Track's annual maintenance: monitoring, updates and quick fixes when something breaks, to keep data loss to a minimum.

Why do my campaigns generate many leads but few clients?

▾
Our A-Track expert's response
Because the algorithm optimizes the objective you gave it, not your business outcome. If your conversion is "form submitted", the platform will look for people likely to fill in forms, not buyers.

The solution: send back signals closer to real value (qualified leads, sales, customer value via your CRM), so the algorithm learns to target the profiles that actually become clients.

What is a "signal" for an advertising algorithm?

▾
Our A-Track expert's response
A signal is conversion information you send to the advertising platform (Google Ads, Meta, LinkedIn) to tell it what a good outcome looks like: a real conversion, a qualified lead, a sale, customer value, CRM data.

Good signals are close to real business value. "Noise" (spam forms, low-intent clicks, misconfigured conversions) degrades the algorithm's learning instead.

How long does an advertising algorithm need to learn?

▾
Our A-Track expert's response
Platforms need volume and repetition to detect patterns. The learning phase therefore depends on the number of conversions reported: the more frequent and reliable the signal, the faster the learning.

Two mistakes to avoid: over-segmenting your campaigns (each segment fragments the data volume) and changing your campaigns too often (each major change restarts the learning phase).

Should you still finely segment your Google Ads and Meta campaigns?

▾
Our A-Track expert's response
No, not like before. In the era of smart bidding, excessive segmentation dilutes the data available for learning and hurts performance.

The right approach: fewer campaigns, but each with a clear role in the customer journey (awareness, engagement, traffic, conversion, retargeting) and an objective consistent with its place in the funnel. The algorithm then tests the audience × message × visual combinations.

Why does server-side tracking improve algorithm performance?

▾
Our A-Track expert's response
Because it makes the raw material of learning reliable: the data. By routing collection through your own subdomain, server-side tracking makes measurement more resilient to browser restrictions (such as Safari's ITP) and technical losses. It also lets you control the data sent to each platform, in line with the FADP and GDPR when properly configured. The visitor's choice is still respected: a refusal remains a refusal.

The result: more usable conversions reach the platforms. Based on our measurements across more than 100 installations (Stape Analytics), server-side tracking recovers 30 to 80% more data depending on the site, around 40% on average. The algorithm learns from a more accurate view of reality and optimizes your advertising budget (ROAS) better.

What is marketing in the age of algorithms?

▾
Our A-Track expert's response
Marketing in the age of algorithms refers to a model where advertising platforms (Google Ads, Meta, LinkedIn) make bidding, audience and delivery decisions themselves through machine learning. The advertiser's role is no longer to configure every parameter manually, but to provide the algorithm with the right environment and reliable data so it can learn correctly.

Why is reliable data essential for advertising algorithms?

▾
Our A-Track expert's response
An advertising algorithm has no business common sense: it only optimises the objective and signals you provide. If tracking is faulty or incomplete, the algorithm learns from a distorted view of reality and reproduces the wrong results. Reliable data, captured through compliant server-side tracking, is therefore the basic condition of effective learning.

Is tracking alone enough to make advertising campaigns perform?

▾
Our A-Track expert's response
No. Reliable tracking is the essential foundation, but it is not a sufficient condition. To generate growth, you must build on top of it: quality content and creative, a clear campaign structure, expert media management and a rigorous A/B testing methodology. The data foundation and the media layer are complementary.

What does A/B testing bring to online advertising?

▾
Our A-Track expert's response
A/B testing consists of methodically comparing variants of audiences, creatives and messages to identify what actually generates value. Because the algorithm reinforces what works, A/B testing supplies it with quality material to optimise and turns reliable data into profitable advertising decisions.

Does server-side tracking fully replace the Pixel?

▾
Our A-Track expert's response
No. The ideal setup is hybrid: keep the Pixel in the browser for simplicity and add the server-side API (CAPI) to fill the gaps. The platforms then deduplicate the events to avoid any double counting.

Is server-side tracking compatible with every CMS?

▾
Our A-Track expert's response
Yes, in the vast majority of cases. Because we rely on the dataLayer and Google Tag Manager, server-side tracking can be implemented on Shopify, WordPress/WooCommerce and PrestaShop as well as on a fully custom site.

Some platforms need adjustments: on Shopify, for example, checkout tracking runs through Customer Events, executed in an isolated environment.

Does server-side tracking make the site faster?

▾
Our A-Track expert's response
Not automatically. The speed gain only appears if scripts are removed from the browser, for example advertising pixels replaced by server-side sends. If every pixel stays in place, the page is no lighter.

When scripts are removed, load times improve, which benefits user experience and, indirectly, SEO.

Does my sGTM host monitor the quality of my data?

▾
Our A-Track expert's response
No. A provider such as Stape monitors its infrastructure: server availability, scaling, certificates and response times.

It does not check that your website actually sends events, that your conversions arrive or that consent is respected. If your site stops sending purchases, the server stays healthy and reports nothing. That monitoring must be assigned to a named person, internal or external.

How often should server-side tracking be checked?

▾
Our A-Track expert's response
We recommend three layers:

1. Continuous automated alerts on a minimum number of events per hour and on your main conversions.
2. A weekly review of server logs (5 to 10 minutes), because logs are only kept for a few days depending on the hosting plan.
3. A full audit every six to eight weeks, replaying key journeys in preview mode.

Add a quick conversion test after every website release.

Why do conversions vanish while traffic stays stable?

▾
Our A-Track expert's response
This is the typical symptom of a partial outage. The GTM snippet still loads, so page views arrive, but something tied to the conversion has changed: a rewritten confirmation page, a purchase event missing from the dataLayer, a renamed button, or a CMP that no longer passes on the consent update.

Compare your conversions every day with the same weekday a week earlier, and reconcile them weekly with actual orders in your shop or CRM.

Does monitoring tracking help with FADP compliance?

▾
Our A-Track expert's response
Yes. Art. 7 FADP requires technical and organisational measures from the design stage of the processing, and default settings that limit processing to the minimum necessary.

After a website or CMP update, tags can fire before consent, contrary to what your privacy notice states. Regular monitoring, documented in a log of checks, lets you detect these gaps and show that your website does what it says. For visitors located in the EU, the GDPR sets comparable requirements.

Why are my conversions credited to direct traffic?

▾
Our A-Track expert's response
This is the classic symptom of a funnel that crosses several domains.

When the visitor leaves your site for a payment page, a booking engine or a ticketing platform hosted elsewhere, the measurement cookie does not travel with them. The destination domain finds no identifier, creates a new one, and GA4 opens a second session. Because the referrer is your own site, or is lost in a redirect, that session is classified as direct traffic.

The result: one person counts as two users, the paid channel's conversion rate collapses and direct traffic's conversion rate soars. Start by checking whether your funnel changes domain before the confirmation page.

Do subdomains need a cross-domain configuration?

▾
Our A-Track expert's response
No, in the vast majority of cases.

www.your-site.ch and shop.your-site.ch share the same root domain. The Google tag and the Conversion Linker set their cookies on the highest possible level domain, that is your-site.ch, and both subdomains read them with no extra configuration.

Adding a cross-domain configuration for subdomains anyway can create problems that did not exist before, notably cookie overwriting. Cross-domain configuration is justified between separate domains, for example your-site.ch and your-site.fr, or towards an external provider's domain.

Does server-side share a cookie across two domains?

▾
Our A-Track expert's response
No. No architecture lets a cookie cross a domain boundary: that is a browser rule, not a tooling limit.

A tagging server hosted at data.your-site.ch can set a cookie for your-site.ch, never for a provider's domain.

What server-side genuinely brings to a multi-domain funnel lies elsewhere. First, lifetime: a cookie set by the server in the HTTP response, with the HttpOnly attribute, can escape the seven-day cap Safari applies to cookies created in JavaScript, provided the server's IP address is aligned with your website's (otherwise Safari caps it too). Second, reconciliation: the conversion can be rebuilt server-side from the order reference and sent to the platforms through their APIs, in line with consent.

Google offers a linker token, the FPLC cookie, but it lives for roughly twenty hours.

Does one consent cover my provider's domain?

▾
Our A-Track expert's response
No, not automatically.

A banner served on your-site.ch does not legally cover the domain of a payment or booking provider, absent an explicit contractual arrangement between the two entities. In practice the visitor often sees two consecutive banners and may answer them differently.

Your implementation has to handle that case rather than pretend it away: if analytics is refused on the second domain, no identifier should be recreated there.

Two things to check under the FADP and the GDPR: the identifier shared across domains must appear in the privacy policy of each domain, naming the controller, and Consent Mode default values must be consistent everywhere.

Must every data leak be reported to the FDPIC?

▾
Our A-Track expert's response
No. Art. 24 para. 1 FADP requires a report to the FDPIC only where the breach is likely to result in a high risk to the personality or fundamental rights of the people affected.

Risk is presumed high in particular where the leak involves sensitive data, copies of identity documents or credit cards. There is generally no high risk where the data was already publicly accessible before the breach.

Note that the rule differs if you are a processor: art. 24 para. 3 FADP requires you to report every breach to the controller, with no severity filter.

What is the deadline to report a data breach in Switzerland?

▾
Our A-Track expert's response
The FADP requires a report as soon as possible, without setting any figure. This is a significant difference from art. 33 GDPR, which requires notification without undue delay and where feasible within 72 hours of becoming aware of the breach.

The absence of a fixed deadline does not mean you can wait: it gives you time to establish the facts before qualifying the risk. Art. 15 para. 2 of the Data Protection Ordinance also allows a report in stages where all the information cannot be gathered at once.

If you also serve customers in the European Union, plan against the stricter of the two regimes.

Must my agency report a data leak to me?

▾
Our A-Track expert's response
Yes, with no severity exception. If your agency runs your tag manager, your server-side container, your consent platform or your CRM, it is acting as a processor.

Art. 24 para. 3 FADP requires it to report every data security breach to you as soon as possible, including when it caused the breach itself.

It is then up to you, as controller, to decide on the report to the FDPIC and on informing your own customers. Your processing agreement should name a recipient, a channel reachable outside office hours and an information format that lets you qualify the risk.

Is an email address in a URL a data breach?

▾
Our A-Track expert's response
Potentially yes. The FADP defines a breach by its effect rather than its origin: it is enough that personal data has been made accessible to unauthorised persons. No intrusion is required, a misconfiguration suffices.

An email address placed in a URL parameter travels in the referrer, in the server logs, into your analytics tool and on to every ad platform called from that page. It has therefore been disclosed to third parties.

What remains is to qualify the risk in order to decide on reporting. But the right reflex is to treat the incident as a breach, document it, and only then assess it.

Is there a fine for not reporting a data leak?

▾
Our A-Track expert's response
Failure to report is not in itself a criminal offence: art. 24 FADP does not appear in the list of provisions covered by art. 60 to 62 FADP.

The exposure sits elsewhere. If the leak results from a failure to meet the minimum security requirements issued by the Federal Council, art. 61 let. c FADP provides for a fine of up to CHF 250,000 upon complaint, imposed on the responsible natural person rather than the company.

The FDPIC can also open an investigation and, under art. 51 FADP, order the modification, suspension or cessation of the processing. For a measurement setup, that can mean stopping a collection your campaigns depend on.

How much does a GDPR or FADP audit cost?

▾
Our A-Track expert's response
The price depends on the scope: number of websites and languages, mobile apps, server-side flows and target countries. The 48-hour flash audit is free.

For a full audit, our technical questionnaire (https://www.a-track.ch/en/form) lets us send you a precise quote.

What is the difference between a client-side and a server-side tracking audit?

▾
Our A-Track expert's response
A client-side audit analyses what happens in the visitor's browser: tags, pixels and the dataLayer. A server-side audit analyses your tracking server: what it receives, what it filters and what it sends to the ad platforms.

The two complement each other, because most data losses and leaks appear where they meet.

Does a Swiss website have to comply with the GDPR?

▾
Our A-Track expert's response
Yes, as soon as it offers goods or services to people in the European Union or monitors their behaviour, for example with analytics tools or advertising pixels.

Most Swiss websites that also target France or Germany are therefore subject to both the FADP and the GDPR.

How long does an audit take?

▾
Our A-Track expert's response
The flash audit is delivered within 48 hours. A full audit takes from a few days for one website to a few weeks for a multi-site, multi-country group.

The timeline is set during scoping.

What is GA4's AI Assistant channel?

▾
Our A-Track expert's response
It is a default channel group in Google Analytics 4, available since 13 May 2026. It gathers visits coming from conversational assistants such as ChatGPT, Gemini, Copilot, Grok or Deepseek.

No configuration is needed: when GA4 recognises the referrer, it automatically writes the medium ai-assistant and the campaign name (ai-assistant) to the session.

Be aware that it does not cover all AI-driven traffic: Google Search AI Overviews and AI Mode are excluded and remain counted as organic search.

Does the AI Assistant channel measure Google's AI Overviews?

▾
Our A-Track expert's response
No. Google's documentation explicitly excludes AI Overviews and AI Mode from the AI Assistant channel: those clicks are counted in organic search, mixed in with clicks from classic results.

To follow that visibility you need Search Console's generative AI performance report, rolled out to all websites as of 31 August 2026. It works in impressions and does not separate AI Overviews from AI Mode.

Practical consequence: a small AI Assistant channel does not mean AI brings you nobody.

Why does my ChatGPT traffic land in direct traffic?

▾
Our A-Track expert's response
Because the AI Assistant channel relies entirely on the HTTP referrer. In mobile apps, desktop apps and some integrations, that referrer is absent or stripped.

GA4's documentation is explicit: a session is processed as direct traffic when no information about the referral source is available.

No setting and no move to server-side restores information the browser never sent. The only usable clue is the trend of your direct traffic and your unusual landing pages.

Do you need a custom channel group for AI traffic?

▾
Our A-Track expert's response
Not at the start. The default AI Assistant channel is enough to get a first figure, with no configuration.

A custom channel group becomes useful as soon as you see assistant sessions landing outside the channel, for example when a link arrives already carrying a source parameter but no medium parameter.

In that case, keep the default channel as a comparison baseline and document the date of every change. Without a log, a break in the curve becomes impossible to interpret six months later.