Integrations

Server-Side GTM

Server-side GTM can reintroduce data flows after a browser-side decision unless HONORED outcomes are deliberately carried into the server container.

Customer Wiring Checklist

  • Forward the endpoint decision state from the browser or application layer to your server-side container.
  • Map HONORED decisions to event filters for sale, sharing, targeted advertising, and vendor-specific destinations.
  • Ensure server-side events do not re-create suppressed identifiers after the browser path honored GPC.
  • Log enough synthetic test evidence to show the server-side handoff path was exercised.
  • Define retry and fail-closed behavior for missing or stale decision state.
  • Review vendor templates and custom tags for routes that bypass shared suppression variables.

Testing Checklist

  • Send a Sec-GPC request and confirm the endpoint decision record exists.
  • Confirm the server-side container receives the corresponding HONORED state.
  • Confirm mapped vendor calls are blocked or stripped as designed.
  • Capture synthetic test evidence without exposing personal data or secrets.

Limitations

GPCGuard does not host or configure your server-side GTM container. It provides decision records and response fields that your implementation can use to drive suppression logic.

Browser GTM checklist →