{Old} How to set up server-side Google Ads conversion tracking [Step-by-step guide] 

unfortunately call conversion tracking is not supported on server-side

As of today, the user-provided data check box is also unavailable in our sGTMs. Our test shows that the sst gAds conversion tag automatically parses user data when it is added to the GA4 tag on a web GTM.

Google ads' server-side work is different from Meta. You should have either web or server gAds; thus, there is no need to configure deduplication. If you use the same gAds conversion IDs for server-side tracking as for web, ensure that you pause web tags.

@@Stape we have both set and it seems that when the conversion tracking fires from the web containers, it prevents the sGTM from sending outgoing request to Google servers for similar request. This also happens with the remarketing tag. Do you confirm this theory when both client and server side conversion tracking are running simultaneously?

​@@DavidBoulayFR@DavidBoulayFR Google ads tracking should not run simultaneously on the web and server. You should configure either server or web Google tracking.

​@@Stape Yes but when we disabled the client side and test our server-side GAds Conversion Tracking, it correctly fires on purchase events but there is no outgoing HTTP request sent from server. Instead I get another type of outgoing request that doesn't appear in your test results in this video at 9:20. Here is a screenshot ibb.co/SdHr499

Wow, I have this same prbolem, did you already solve it? I can't find any solution to this just yet.

@@mnl6794 still not, I have not spent much time on it :)

As of today, the user-provided data check box is also unavailable in our sGTMs. Our test shows that the sst gAds conversion tag automatically parses user data when it is added to the GA4 tag on a web GTM.

@@Stape alright! So it is automatically enabled. thanks for your reply!