If we have the Custom Loader configured to use same origin path, do we need to / is it beneficial to still follow the prompt Google started pushing a couple of months or so back?
Despite having sGTM setup with custom loader I still see plenty of requests to googletagmanager.com. I assume that is referencing Tags that do not push data to our sGTM container?
However, the above are all “initiated” by the “Custom Domain” set within the Custom Loader config. I appreciate this is a n00b question. I’m trying to understand how the chain of requests operates between same origin → custom domain → calls made from the client to third parties || calls made to our sGTM container.
First-Party Mode is a simple server side use case for GA4 and Google ADS. As an alternative to sGTM for those who do not have the resources to make a full server side. It’s kind of like a Meta/Snap/TikTok Gateway.
With the same origin approach with sGTM it is completely normal that some queries are sent directly to Google. These are technical requests that do not affect your tracking. Also as far as I know google collects statistics on GTM usage this way.
As we have GA4 data collection taking place via sGTM but not Google Ads, is setting up the first-party mode a “quick and easy” way to improve the reliability?
Is having them setup together likely to cause any conflict?
Are there advantages to implementing a full sGTM based Google Ads setup vs the first-party mode?
I have not encountered GA4 running in parallel on sGTM and Google ADS via first party mode, but I am almost certain that there will be a conflict. I would recommend using only one of them here.
Since you already have GA4 server side via sGTM, setting up Google ADS conversions on sGTM is not difficult at all:
Just trigger Google ADS tag on needed GA4 request and thats it
