Can you let me know why the server’s outgoing requests are not going through? I can see it going through the browser, however, I don’t see it through the server.
This is completely normal for Google ADS tags. They work in a stupid way so far and their request is sent through the browser, even though the tag is running on the server.
I think that once Google completely disables third-party cookies in Chrome - Google ADS will not make any sense to send a requester from the browser either.
2 Likes
Hi @Alex ,
What are your thoughts on this?
Simo Ahava recently published an article about the gclid cookie restriction on Shopify’s checkout extensibility. There I found out that if a gclid is present in the server’s incoming request or as a query parameter in the page_location URL, the Google Ads server-side tag will include it in the “Outgoing HTTP Request from Server” section.
Have you had a chance to read it? I’d love to hear your opinion!
Article link: Cookie Access With Shopify Checkout And SGTM | Simo Ahava's blog
1 Like
Hey @Md_Monirul_Islam ,
Definitely best practice would be to implement it the way Simo describes.
Otherwise it will also work, but definitely worse and only due to the fact that Google ADS sends an additional hit from the browser and due to the fact that Google on its side can link the conversion event by other attributes and by previous secondary conversions that the user has made.
1 Like
Thanks man! I got a little bit confused. Because some of my friends implemented Google ads SST for shopify the usual way without following Simo’s method and their setup is working fine. No complain yet. However I follow simo’s method whenever I setup GAds SST for shopify. Thanks for clearing things up.
Yes, it will work fine, but actually not much better than standard web tracking.
Using the method that Simo described will simply increase the number of conversions that will be tracked.
1 Like