Stape.io Setup for Server-Side GTM

Stape.io is a hosting service for server-side Google Tag Manager. It runs the server for you, handles scaling, and adds features built for tracking. This outline covers a standard setup.

What you need first

• A working web GTM container on your site
• Access to your domain’s DNS settings to add a subdomain
• Admin access to GA4, and to Meta Business Manager if you plan to use the Conversions API

1. Create the server container in GTM

In Google Tag Manager, create a new container and choose Server. Select the option to provision manually and copy the container config string.

2. Create the container on Stape

In your Stape account, create a new container, paste the config string and choose a server location close to your visitors. Stape creates the server and gives you a default URL.

3. Add a custom domain

Use a subdomain of your site, for example sst.yoursite.com. Stape shows the DNS records to add. Once verified, set this domain as the server container URL in GTM so requests go to your own domain.

4. Send GA4 data to the server

In the web container, update your Google tag so it sends data to the server container URL (the server_container_url setting). In the server container, the built-in GA4 client receives these requests. Add a GA4 tag in the server container to forward events to Google Analytics.

5. Add the Meta Conversions API

In the server container, add a Meta Conversions API tag (Stape provides a template in the GTM gallery). You will need your Pixel ID and a Conversions API access token from Events Manager. Map events such as generate_lead to Meta’s Lead.

Make sure the browser Pixel and the server tag send the same event_id so Meta can deduplicate. See how Meta CAPI deduplication works.

6. Consider the custom loader

Stape offers a custom loader that serves the GTM script from your own subdomain. It is optional; check it fits your consent setup and site policies before enabling it.

7. Test before publishing

• Use Preview in the server container to watch requests arrive and tags fire
• Use GA4 DebugView to confirm events
• Use Test Events in Meta Events Manager to confirm server events and deduplication

Keep it maintained

Watch Stape’s usage limits against your traffic, keep tag templates updated, and re-test after any website change that touches forms or checkout.

This is a standard part of server-side tracking setup.