Events are triggered, when publish a web container

Google Tag Manager Server Container
1

Hello. Colleagues, please help.
I have configured web and server containers with Data-tag (for web) and Data-client (for server side). Sending Data From the Google Tag Manager Web Container to the Server Container

When I publish a web container, events are triggered, why is this happening ?
video

and in facebook pixel:

Events Manager - Incogniton Browser
Events Manager - Incogniton Browser1071×567 94 KB

Can this be fixed ?

UPD: I found out that this only happens when “Request type” = POST. In this case one event is triggered three times after publishing the web container.

Google Tag Manager - Google Chrome
Google Tag Manager - Google Chrome1237×702 110 KB

2

Hello. Dear support.
Dear Support.
Can you fix the problem with the data-tag ?
When I publish a container there are three requests,
page_location =gtm-msr

image
image1215×561 86.3 KB

Or tell me how I can get around it.
I have brought two clients to you, they have switched to a paid plan. I would like to get help from you.
This problem is distorting the data in facebook pixel.
Thank you.

3

Im also still waiting for a reply, I think it’s weird that it is being ignored. Don’t know if you are using shopify but they have updated their CAPI and added the other events, so it’s not just Purchase that gets the browser and server side tracking so i’m not sure if it’s still worth using this platform for the server side tracking.

4

Hello @Beetje.
I haven’t worked with shopify yet, my clients use “tilda” . I also find it strange that they started ignoring messages. I’ve emailed them on github, emailed the developer and in the comments of the post.
They do unsubscribe to this thread.

5

@Beetje You can add an additional condition to the triggers like I did.
For example:

  1. Add in the server container a variable like “Request Header”, name “Origin”, like this.
  2. Add this variable to an additional condition in trigger. For example for generate_lead event,
    like this
  3. Publish the server container and test it.

We told our tag to trigger only if it matches an event and it is a request from our site. The requests will still come, but the tag will only be triggered by our condition:
event name = generate_lead and Origin = our site
like this

6

Dear, @111 @Beetje

We have been trying to respond as soon as possible, but we are also experiencing a high volume of inquiries from our paid clients these days.

If you have issues with the container subscribed to a Pro plan, please feel free to contact us via email at support@stape.io. For the Business plan container, we provide support either via email or chat. We will reply asap and always within 24 hours during the working hours.

Our support working hours:
Monday-Friday: 7AM-5PM (UTC)
Saturday: 7AM-10AM (UTC)
Sunday: closed

As an option, if you have trouble setting up GTM Web or GTM SS, we provide a Setup All for You service: Server-Side Tracking Agency offers different quotes - Stape and also we provide paid consultations.

Regarding the issue described here answer is provided in this similar topic Server side sending false ''add to cart'' events - #9 by Denis

7

@Denis Hello.

If you have issues with the container subscribed to a Pro plan, please feel free to contact us via email at support@stape.io. For the Business plan container, we provide support either via email or chat. We will reply asap and always within 24 hours during the working hours.

I understand, but in most cases such problems are detected at the stage when the client uses the “Free” plan and I perform the integration. Thank you very much for your help and feedback