Check explainer
Server-side tracking
Server-side tagging bypasses ad blockers, stabilises attribution, and decouples tracking from the frontend.
- note
- ok
What we check
Looks for server-side tagging indicators: stape.io, sGTM endpoints, first-party subdomains.
Why it matters
Server-side tagging bypasses ad blockers, stabilises attribution, and decouples tracking from the frontend.
Common causes
- There simply is no server-side setup, all tags send straight from the browser to the vendor domains.
- The server container exists, but the web container still sends to the standard endpoints instead of the first-party subdomain.
- The setup runs on a subdomain the scan does not recognise as a tagging endpoint, then check your own request targets.
- An sGTM project was started and never finished, the container idles along.
How to fix it
Set up a stape.io container or self-host sGTM, then migrate client-side tags step by step.
What does a failing Server-side tracking finding mean?
Server-side tagging bypasses ad blockers, stabilises attribution, and decouples tracking from the frontend. Set up a stape.io container or self-host sGTM, then migrate client-side tags step by step.
How do you fix Server-side tracking?
Set up a stape.io container or self-host sGTM, then migrate client-side tags step by step.