How to configure Stape Gateway
Updated Nov 13, 2026
Before you begin
You’ll need to configure GA4 or Google Ads tracking for your website. Ensure that web Google Analytics 4 and/or Google Ads tracking is configured for your website. Stape Gateway works only based on data that web GA4 and/or gAds requests send.
Step 1 | Create Stape Gateway
- 1.Log in to your Stape account and click Gateways in the dashboard.

2. Click Create gateway → Create Stape Gateway.

3. Fill in:
- Gateway name – a descriptive label.
- Web GTM ID – your web container ID. For the instructions on how to find it, read How to find Web Google Tag Manager (GTM) ID?
- Server location – pick the region closest to the majority of your traffic.
4. Click Create gateway.

5. Select a subscription plan and click Continue.

6. Wait for the gateway status to change to Running.

Step 2 | Configure custom subdomain (highly recommended)
Setting up a custom domain is highly recommended to unlock the full potential of server-side tracking. When your tagging server runs on your own subdomain, tracking cookies are treated as first-party data. While Safari's ITP restricts client-side cookies to just 7 days, server-side cookies issued from your domain maintain their longevity, allowing you to accurately recognize returning visitors and preserve long-term attribution. Additionally, routing data through a custom subdomain keeps tracking requests integrated with your first-party traffic, preventing ad blockers and browser privacy controls from dropping critical conversion signals.
- 1.In your gateway, click Add custom domain.

2. Fill in:
- Domain name – enter the subdomain name. A subdomain is a separate section of your domain that sits in front of the root domain. For example,
stape.iois the root domain, sosgtm.stape.ioandvideo.stape.ioare subdomains of it. For a custom domain, this means your tagging server URL would be something likedata.example.com, whereexample.comis your root domain. Try to avoid using phrases specific to advertising or tracking:ad, gtm, stgm, tracking, analytics, metrics, stape, gtag, and so on. Some ad blockers are smart enough to recognize these. - Web GTM ID – web container ID that you’ve already provided while creating the gateway.
Toggle Own CDN if you want to route your domain through the same IP address as your main website. By matching the IP addresses between your gateway domain and your site domain, browsers like Safari and Firefox treat cookies as true first-party cookies, preventing their shortened lifespans under Intelligent Tracking Prevention (ITP). With Own CDN you are responsible for SSL certificate issuance and we can validate your custom domain only once the SSL certificate is in place. For the setup instructions when Own CDN is enabled, go to the Configuring a custom domain with own CDN enabled chapter.
Select how you want to connect the custom domain:
- Automatically (via Entri) – the easiest way to connect domains. Log in with your DNS provider details via Entri, and give us one-time permission to connect your domain. Check if your DNS provider is supported by Entri in this list.
- Manually – after you add a custom domain to your Stape container, you will see DNS records that should be added to your DNS provider to verify the custom domain. The DNS records depend on the server location and which CDN options you choose.

What to do if custom subdomain isn’t verified
Domain verification can take up to 72 hours, but it usually happens within 30-60 minutes if your DNS records are correct. If it takes more time for you, there may be a problem with your configurations.
There are the main reasons why a subdomain may not verified:
- Typo in the Name/Host field – some DNS managers automatically append your root domain. If you enter
data.yourdomain.cominstead of justdata, the record might resolve todata.yourdomain.com.yourdomain.com. In some DNS providers, only the prefix (for example,data) should be entered in the Host/Name field. - Proxy status enabled – if you use Cloudflare, ensure the proxy status for the CNAME record is set to DNS only, not Proxied.
- Target mismatch – ensure the CNAME points to the exact gateway target provided by Stape, with no spaces or typos.
- Conflicting DNS records – ensure there are no existing A, AAAA, or conflicting CNAME records for the exact same subdomain name in your DNS settings.
- Missing SSL – if you configured the custom domain using an Own CDN setup, Stape can't verify the domain until an active SSL certificate is in place on your side.
You can check your DNS records with the Google Admin Toolbox Dig tool.
- 1.Enter your custom subdomain (for example,
data.yourdomain.com, withouthttps://or trailing slashes). - 2.Select the CNAME tab.
- 3.Verify that the returned target matches the exact value provided in your Snapchat Conversions API Gateway dashboard.

Step 3 | Configure Custom Loader
Important:
Without enabling the Custom Loader, Stape Gateway won’t work.
- 1.In your gateway scroll down to the Custom loader section. Select your CMS platform where your website is built. If your website is custom-built, then select Other.
- 2.Click Generate.
- 3.Follow the instructions in the Configuration and App installation sections to finish setting up Custom Loader.

Testing
Check the following:
- Open a URL of your Stape Gateway and add
/healthyat the end (for example,https://data.stapeusa.com/healthy). If everything works correctly, you should see the ok response.

- Go to Google Tag Manager and open your web container → Preview. Enter your website URL and do some actions inside Google Tag Assistant to trigger the events. Select the GA4 client and click the Hits Sent tab. Open any event.

Confirm that the URL is the custom subdomain one.

Was this article helpful?
🍽 Table of content:
Comments