Dear Community,
I am struggeling with my Google Remarkting Tags from server-side (using stape.io) to send Outgoing HTTP Requests from the Server. Also the Firing Status is “Failed” whatever I try. This is frustrating as I have tried everything for many days now, all the other Google Ads Conversion tags are firing correctly.
Care to pinpoint what could be the problem?
I am attaching my settings.
Hi @warcious,
I see that you’re using the Data Tag and firing the Google Ads Remarketing tag on sGTM based on this tag.
For it to work, you must enable this setting Support rich command protocol.
Please note that using the GA4 Tag from the web to the server to trigger Google’s tags is the most optimal solution, because they integrate better (they have some settings that are not documented and sometimes are hard to replicate - Google Consent Mode parameters, the rich command protocol etc.).
Can you tell me where I can find this setting “support rich command protocol” as I have been trying to find it everywhere. Is it supposed to be inside the GTM or sGTM container?
I am using your Event Data Client (Stape.io), so I am not 100% sure what you mean with the fact that I am using “Data Tag”.
Hi @warcious,
If you are using the Event Data Client (Stape.io) in your sGTM, that means that in GTM web container you’re using the “Data Tag”.
The “Data Tag” is the one that communicates with the Event Data Client.
The GA4 Tag that you shared (the Google Tag), communicates with the GA4 Client.
That said, you’ll find the Support rich command protocol in the Data Tag in GTM web that sends the event to sGTM.
Let me know if you can find it.
So you are saying that I should use “Data Tag” from Stape.io instead of using GA4 for connecting between GTM and sGTM for consistency? And all my tags should fire correctly?
So you guys have a possibility to make an audit of my current setup, as we are using Stape.io for our server-side tracking?
Currently, we connect GTM to sGTM using Google Tag and our GA4 ID,
Are you suggesting we should use “Data Tag” template when connecting GTM with sGTM?
Hi @warcious,
Please share a screenshot of the 2025-08 Event Data Client (Stape.io) in sGTM.
So you are saying that I should use “Data Tag” from Stape.io instead of using GA4 for connecting between GTM and sGTM for consistency? And all my tags should fire correctly?
Usually, sGTM Google’s tags work better if GA4 tags are used to send data from web GTM to sGTM.
And the Data Tag + Data Client can be used for everything else.
So you guys have a possibility to make an audit of my current setup, as we are using Stape.io for our server-side tracking?
Our Care team can gladly take care of that.
I found your Data Client on github online that I used.
Not sure which screenshot you would like, there is not much in the configuration. But is this helpful?
Btw, do you have a guide on how to setup GTM → sGTM synchronization using Data Tag from Stapie.io?
Also, do I need the multi-domain plan if I use 25 domains (25 Google Ads accounts with 25 GA4 ids, 25 Gads AW-xx tags, etc) through my 1 x Shopify website, or can I do server-side tracking using 1 domain?
Thanks for the screenshot. This means that you are using the Data Client as I suspected, and it also means that you must be using the Data Tag (in web GTM) to send the event that triggers your Google Ads Remarketing tag (in server GTM).
To solve the issue with the Google Ads Remarketing tags failing on the server, go to the web GTM and search for Data Tag.
After that, still in web GTM, open the Data Tag tags that send the events that you use to trigger the Google Ads Remarketing tag in sGTM, and mark the checkbox Support rich command protocol I highlighted here.
And the other option would be to just use GA4 tags (in GTM web) and GA4 Client (in sGTM) for GA4 tags, Google Ads Remarketing and Conversions.
Btw, do you have a guide on how to setup GTM → sGTM synchronization using Data Tag from Stapie.io?
Sure!
Also, do I need the multi-domain plan if I use 25 domains (25 Google Ads accounts with 25 GA4 ids, 25 Gads AW-xx tags, etc) through my 1 x Shopify website, or can I do server-side tracking using 1 domain?
Are these 25 domains all subdomains of a main domain? (e.g. store1.example.com, storeabc.example.com, store2.example.com)
Or, are they totally different domains that are not part of the main domain?
If these domains are all subdomains of a shared main domain, you can do server-side tracking with just 1 domain. Otherwise (multiple different domains that don’t share a main domain), you would need the multi-domain plan so that each domain has its own server-side tracking domain.
Thank you for your earlier reply.
When it comes to the multidomain custom domain configuration option, I am trying to understand the difference between the same origin setup vs subdomain setup. I do have maybe 100.000 request sent per month, even if I use 25 domains. Which option is optimal, so my tracking is as accurate as possible? Is there a lot of tracking loss using the subdomain option instead of the same origin option?
Do you know if domain providers such as netim provide me the option to use custom code to setup same origin option?
Hi @warcious,
The most accurate option for tracking is a same-origin setup + using a CDN (or similar) so that the IP addresses of the website and sGTM are the same.
This will make some cookies have a longer life in Safari and WebKit browsers in iOS.
If that’s not possible, the subdomain setup is fine. But you’ll have some cookies not living that longer on these browsers.
As far as I know, Netim only provides the domain names but doesn’t let you manage the DNS records. The same origin setup has to be configured elsewhere, like Cloudflare or similar.
If all these domains share the same top-level main domain and the websites are the same (just the URL is what changes), then you can go with Pro using either same-origin or a subdomain. Otherwise, Enterprise.
Thank you for your reply.
I am using Shopify, so apparently the same-origin is not working together with Shopify, is that correct, otherwise I could setup the loaders (workers) inside cloudflare and setup my DNS inside Netim, where I just change the nameservers to cloudflares nameservers.
Do you know how to use same-origin with Shopify?
This is the answer I got from chatGPT:
Short version first: because your storefronts are hosted on Shopify, a true same-origin path like https://vortexvr.de/sgtm is not feasible in practice. Same-origin requires a reverse proxy in front of your site that can route /sgtm/* to Stape; with Shopify you generally can’t proxy the apex/WWW through your own Cloudflare zone (Shopify will complain “Your domain has a Cloudflare proxy…” and block verification / SSL). Stape’s own support also notes that same-origin on Shopify isn’t possible unless all traffic is proxied through Cloudflare—which Shopify does not support for normal merchant setups. Use subdomains per ccTLD instead (e.g., gtm.vortexvr.de, gtm.vortexvr.fr, gtm.vortexvr.se). Stape Community+3Cloudflare Community+3Shopify Community+3
Below I’ll still show you (A) how to add each domain to Cloudflare and get the nameservers at NETIM without breaking Shopify, and then (B) the recommended subdomain setup for Stape multi-domain. If you later want to experiment with advanced Orange-to-Orange (O2O) proxying, we can discuss it, but it’s not the standard merchant path. Cloudflare Docs
Hi @warcious,
I’m sorry, I missed when you mentioned you use Shopify. My bad.
Yes, that’s correct. Shopify doesn’t support same origin, so you’ll have to go with the subdomain route. I see that each website has its own domain, therefore you’ll have to use a tracking subdomain for each (e.g., gtm.vortexvr.de , gtm.vortexvr.fr , gtm.vortexvr.se).
Dear @giovaniortolani,
We have tried everything, but for some reason, when we are using the Stape.io Data Tag client inside GTM, it fires our events more then 1 time inside sGTM.
We have tested the datalayer many times, and it is only firing once for each event, also fires correctly inside GTM, but our Stape Data Tag (client) solution is firing more than 1 time, so something is wrong with our synchronization, and we think the problem is with the Data Tag client from Stape.
Can you point is in the right direction, which Stape Data Tag Client version should we use?
Our current version is: 80e00
Are you trying to say that GA4 Data Tag is better to use than Stape Data Tag when connecting GTM with sGTM using Stape.io server-side tracking?
We have tried everything, but for some reason, when we are using the Stape.io Data Tag client inside GTM, it fires our events more then 1 time inside sGTM.
We have tested the datalayer many times, and it is only firing once for each event, also fires correctly inside GTM, but our Stape Data Tag (client) solution is firing more than 1 time, so something is wrong with our synchronization, and we think the problem is with the Data Tag client from Stape.
Can you point is in the right direction, which Stape Data Tag Client version should we use?
Our current version is: 80e00
If you’re seeing duplicate events in the sGTM, most likely it’s due to incorrect tag implementation in the GTM web. Most of the time this is caused by duplicate tags in there.
Please, check that and also check if you see multiple requests to {Your sGTM domain}/data?v=2&event=... in your Network panel on DevTools.
Besides this, are these requests that you shared in the screenshot exactly the same? Are their payloads (request URL, body etc.) equal?
The version you’re using is the most up-to-date version.
I’ve just checked vortexvr.de and vortexvr.fr and didn’t notice any problems with the events from Data Tag.
Are you trying to say that GA4 Data Tag is better to use than Stape Data Tag when connecting GTM with sGTM using Stape.io server-side tracking?
For GA4 tags and Google Ads tags (or Floodlights, we recommend using the GA4 Tag to send the data from web GTM to sGTM, and the GA4 Client to receive the data.
For other platforms (Meta, TikTok, Snapchat, etc.), we recommend using Data Tag to send the data from web GTM to sGTM, and Data Client to receive the data.
1st question:
Can we still use Stape Data Tag for GA4 tags, Google Ads conversion tags, and Google Dynamic Remarketing tags, or do you NOT recommend it at all?
We have encountered strange issues:
Except the strange “double” or “tripple” fires we are seeing inside sGTM we also can not pass the gcs cookie from our GTM → sGTM for Remarketing tags, so the Remarketing tags never fire (Outgoing HTTP request is always “none”) for Server (inside sGTM).
Browser side sends the cookies to sGTM correctly for FB tags, GA4 tags, Google Ads conversion ID tags, but not for Dynamic remarketing tags?
We can see that the cookie gcs ID is not being passed to the server side.
Have you ever encountered this problem, and do you know what to do?
Also, tell me what information you need from my side for debugging?
Please look at my outgoing HTTP requests with payload for each dublette pair of each event in sGTM:
In sGTM - Outgoing HTTP request from browser:
In GTM everything is firing correctly:
Please let me know if I have passed sensitive information that can harm me, than I will quickly remove it or edit it out.
Whatever we do, for some reason our _gcs cookie is NOT being passed using our Stape Data Tag to sGTM (server solution), and we need your help to fix this. Something must be wrong with the Stape Data Tag.
We have 2 problems:
1 - double or tripple fires inside sGTM, even if events fire only once in GTM.
2 - remarketing tags never have output HTTP request sent from sGTM, and here we have discovered the _gcs cookie is not being passed to sGTM.
We need your help, we know GTM is working fine, but inside sGTM we dont get normal results.
Hi @warcious,
1st question:
Can we still use Stape Data Tag for GA4 tags, Google Ads conversion tags, and Google Dynamic Remarketing tags, or do you NOT recommend it at all?
You can, but it won’t work properly. That’s why I recommended using GA4 tags for Google’s tags (GA4, Ads etc.), and the Data Tag for everything else.
There are some parameters (not cookies), like the gcs and gcd that are sent by the GA4 tags and have a specific format that are used by Google’s tags in the server.
When making the switch, everything should work properly.
In theory, you could replicate them in the Data Tag on the browser, but it’s not a durable solution as Google can change their formats anytime.
Whatever we do, for some reason our _gcs cookie is NOT being passed using our Stape Data Tag to sGTM (server solution), and we need your help to fix this. Something must be wrong with the Stape Data Tag.
We have 2 problems:
1 - double or tripple fires inside sGTM, even if events fire only once in GTM.
2 - remarketing tags never have output HTTP request sent from sGTM, and here we have discovered the _gcs cookie is not being passed to sGTM.
We need your help, we know GTM is working fine, but inside sGTM we dont get normal results.
Considering the requests you shared via Pastebin, it seems that the Stape Data Tag is firing twice in the browser. I cannot build any other hypothesis without further investigation.
Please, send a private message to me with the sGTM and web GTM preview mode URLs (the same preview mode URLs where these problems happen).
