ConsentPulse
<- All Guides/Server-Side GTM/PRE_CONSENT_MARKETING_LEAK

Server-Side GTM (sGTM) & Stape Custom Loader Consent Mode v2 Governance

Why cookieless gcs=G100 hits to your first-party sGTM proxy must never trigger downstream Meta CAPI or TikTok Events API tags.

1. Observed Wire Symptom

Browser network inspection shows compliant cookieless pings (https://metrics.brand.de/g/collect?...&gcs=G100&gcd=13p3p3p2p5) after Reject All, yet downstream Server-Side GTM tags forward those rejected events with IP/User-Agent/hashed PII to Meta Conversions API and TikTok Events API.

2. Technical Root Cause

In Advanced Consent Mode v2, the web GA4 tag intentionally sends cookieless gcs=G100 pings to your sGTM GA4 Client so Google can perform behavioral modeling. However, third-party server tags inside your sGTM Server Container (Meta CAPI, TikTok, Klaviyo, Pinterest) trigger on every incoming GA4 Client event unless you configure Server-Container Consent Checks or block events where x-ga-gcs == G100.

BROKEN PATTERN
# Broken sGTM Server Container Tag: "Meta CAPI - PageView & Purchase"
Firing Trigger: All GA4 Client Events (Client Name == "GA4")
Consent Settings in sGTM Server Container: Not set
# Danger: Every rejected browser ping (gcs=G100) sent to metrics.brand.de
# is forwarded server-to-server to graph.facebook.com!
REMEDIATED PATTERN
# Fixed sGTM Server Container Configuration:
1. Enable Consent Overview inside your sGTM SERVER container.
2. On Meta CAPI, TikTok Events API, Pinterest & Klaviyo Server Tags:
   Advanced Settings -> Consent Settings ->
   "Require additional consent for tag to fire" -> ad_storage
   (sGTM automatically reads incoming GA4 gcs / gcd consent_state!)
3. Defense-in-depth Blocking Trigger:
   Block when Event Data "x-ga-gcs" matches RegEx ^G10[01]$

3. Post-Publish Verification Checklist

  • ✓Verify browser-to-sGTM /g/collect hits carry gcs=G100 & gcd=13p3p3p2p5 on Cold/Reject and upgrade to gcs=G111 & gcd=13r3r3r2r5 on Accept.
  • ✓Open sGTM Server Preview mode, send a gcs=G100 hit, and confirm zero outbound HTTP requests leave sGTM toward graph.facebook.com or business-api.tiktok.com.
  • ✓Verify sGTM GA4 Server Tag never writes FPID Set-Cookie headers when analytics_storage is denied (G100 / G110).

4. Practitioner Edge-Case FAQ

Are first-party sGTM /g/collect requests on Cold Load a GDPR leak when gcs=G100?
Under Google Advanced Consent Mode v2, browser-to-sGTM /g/collect requests with gcs=G100 and gcd=13p3p3p2p5 are cookieless pings—provided your sGTM server container strips/Withholds FPID cookies when analytics_storage is denied and blocks non-Google CAPI forwarding when ad_storage is denied.
Does Stape's Custom Loader hide GTM tag misconfigurations from external inspection?
Stape's Custom Loader rewrites the bootstrap script URL and query string to bypass adblockers, while still delivering the compiled var data = {"resource": {"version": ...}} container AST to the browser so GTM can execute tags.

Did this GTM remediation playbook help resolve your issue?

1-click practitioner feedback — shapes which CMP & GTM edge cases we document next.

Verify If Your Container Suffers From PRE_CONSENT_MARKETING_LEAK

Paste any storefront URL to inspect live Frankfurt gcs/gcd beacons and exact GTM Tag IDs.

Audit URL Free ->
View 2,328-Site Study ->