Server-side GTM (sGTM)

CookieBeam can provision one hosted sGTM container per banner. Browser events are sent to the container's measurement endpoint, and the container routes them to the server-side tags you configure.

Endpoint and consent behavior

The default endpoint is a CookieBeam-managed subdomain of syncingbeam.com. It is not first-party to a publisher site on another registrable domain.

To use an endpoint under your site, add and verify a custom subdomain such as track.example.com. CookieBeam uses the custom domain only after verification. Until then, the container continues to use its managed endpoint.

Generated transport events include consent state. This does not make every server-side tag consent-aware automatically. Configure each server-side tag to read and respect the incoming consent values.

Provision and verify a container

1. Open Server-Side GTM and choose Enable sGTM for the banner.
2. Open the container and supply its Container Configuration. Use Save & Provision.
3. Check the container status and server URL.
4. To use your own subdomain, add it under Custom Domain, create the displayed DNS record, and use Check Verification until it is active.
5. Run Test Connection. Then send a test event and confirm the intended server-side tag receives the consent fields.

Container provisioning and domain verification use the sGTM controls directly. They are not completed by publishing a banner version.

Usage tiers and billing

sGTM has request-volume tiers. A team's first container has a 14-day grace period before billing starts; each additional container is billed from activation, prorated onto the subscription. Current tier prices and limits are shown before enablement.

With Auto tier upgrades enabled, usage above the current limit moves the container to the required higher tier. For a team with a Stripe subscription, the service then synchronizes that tier to Stripe. A failed Stripe synchronization attempts to restore the previous database tier and reports an error. With automatic upgrades disabled, the current check returns without upgrading, suspending, billing an overage, or sending a warning.

At a successful subscription-cycle invoice, CookieBeam resets the database request counter and database tier to pro. That reset does not synchronize a lower price to Stripe. A quieter cycle therefore does not automatically reduce the billed subscription item. The Stripe item can remain at the previous higher tier until another billing synchronization occurs, such as a later upward tier change, container removal, or explicit reconciliation.

The dashboard tier can therefore differ from the tier currently billed by Stripe after a cycle reset. Do not use the displayed reset tier as proof of a billing downgrade.