Tracking & Compliance · sGTM

Your tracking measures less than you think - and your “compliance” might be just a banner.

Real measurement, within the law - without the 40% myth or the fine scare.

Painel de tracking server-side com eventos, consentimento e fluxo sGTM para CAPI
[ The problem ]

Two problems nobody connects.

What you lose

On one side, you measure less than you think: Safari, Firefox and adblockers cut a slice of client-side tracking, and your Meta Ads optimizes on incomplete data.

The legal risk

On the other, “being compliant” has become displaying a cosmetic banner that doesn't address what LGPD (Brazilian data protection law) actually requires.

The good news: both can be fixed - with engineering, not fear.

[ Typical vs. Inodus ]

The same site, two different foundations.

Collection
Comumclient-side (Safari/adblockers cut it)
Inodusserver-side (sGTM), more resilient
Meta Pixel
Comumbrowser → Meta (blockable)
Inodusserver → CAPI + deduplication
Consent
Comumcosmetic banner (fires before consent)
Inodusreal consent, granular opt-in
Legal basis
Comumundefined
Inodusdocumented (consent or legitimate interest)
International transfer
Comumignored (GA4/Meta in the US)
Inoduscontractual mechanism (standard clauses)
[ The numbers ]

Complete data becomes conversion.

Verified data from public studies and the law itself. Server-side recovers part of what client-side loses - a real benefit, without a guaranteed magic number.

29.5%use an adblocker

The “death of cookies” never happened in Chrome (Google reversed it). The real measurement loss comes from Safari, Firefox and adblockers.

Fonte: GWI, 2025
~11–24%gain with server-side

Server-side (sGTM) recovers part of the events. Vendor case studies show these gains - a real benefit, but not a fixed guaranteed number. Be suspicious of anyone promising “recover 40%”.

Fonte: Stape (vendor case studies)
BR ≠ EUcompliance without myths

LGPD has no ePrivacy law: necessary cookies don't require consent, and legitimate interest can cover part of your analytics (with documentation). Google's Consent Mode v2 is a requirement only for EEA traffic - not for Brazil.

Fonte: LGPD / Google
R$50Mfine cap per violation

The most concrete risk isn't the banner: it's the international transfer of data (GA4/Meta in the US), which requires standard contractual clauses since ANPD Resolution 19/2024. Fines of up to 2% of revenue exist, but as of this material's verification the ANPD had not fined anyone over a cookie banner.

Fonte: LGPD Art. 52 / ANPD Resolution 19/2024
[ Frequently asked questions ]
Why do Meta Ads and GA4 show different numbers?+

Client-side loses events differently in each browser; a 20–50% discrepancy between platforms is common.

Is my cookie banner OK?+

If GA or Meta fire before the consent click, it isn't. You can check in DevTools → Network.

Is sGTM worth it?+

It captures more conversions and gives your tracking a legal basis. It solves the revenue problem and the compliance problem at once.

Is your tracking losing conversions - or exposing you to the ANPD?

Run the free audit and find out, in under a minute, how many events your site loses and whether your tags fire before consent.