Only set up server container - Events already send

Google Tag Manager Server Container
1

Hi,

What are those events that are sent as soon as you setup the GTM server container in GTM itself but without updating transport urls, website scripts etc.?

I set up stape for one of my clients but just made the first step of connecting stape with a subdomain and a server GTM container and events are already recorded in stape (about 1% per day of the 10.000 free events).

2

If you used the custom loader, then those events are:

  • initial container download
  • donwload of analytics.js
  • donwload of gtag.js
  • etc
1 Like
3

I just had a look, I didn’t set the custom loader - just connected subdomain with stape and connected the server GTM (“manual”) hash to stape.

  • There is a web GTM container running on the same tag manager account - but it’s not connected with the server container.
  • Only the default UA and GA4 clients are installed in the server container (they are preinstalled nowadays).
  • The transport URL isn’t connected in the server container settings.
  • The gtm script on the website isn’t changed for the SST transport url.
4

Hi Olaf, please send me the website URL and I will check.

1 Like
5

I have the same issue now. Created my Stape account, a custom tagging server url, and a server GTM 7 days ago. That’s it. But when I opened the account today, already hundreds of requests have been made. How is this possible?

  • The web GTM is not connected to the server GTM yet. Both are running under the same GTM account.
  • The default GA4 client is installed, but not yet connected to GA4 tags in the web container.
  • The GTM script on the website is not changed for the custom tagging server url

With 1 difference compared to Olafs old post: my custom tagging server url was connected to the serverside GTM 3 days ago.

6

@Sabrina_AR did you perhaps ever run a preview of your server container?

7

Hi @Dan , I have! But that gives the error “no tags were evaluated in this container”, so there’s nothing fired (yet).

8

When you run a preview session of a server container, it periodically (roughly each 10 sec) queries the server to see if there were any requests received to be rendered in your preview session. Which means just running preview, even w/o any tags does generate some requests.

9

Ah, that explains a lot. Thanks Dan!