Hello.
I’m using the Google Tag Gateway and I don’t seem to be receiving any geo data other than country. Unlike the sGTM, there are no power-ups to configure. I’m just not sure if Stape is autonomizing the geo data before pushing it to GA4 dashboard. I think my tag is set-up correctly as are all my config options in analytics (except the confusingly worded consent signals).
Geo data is not sent as part of the request. This is determined on the GA4 side based on the IP address you send with the event + GA4 signals functions if you have this active.
Also please note what Denis wrote above - City detection is not supported when using First Party Mode (this is how Gateway works). This is a limitation of GA4, they will probably change this in future updates.
If Stape does, do you know of any settings that might allow GA4 to determine the country and region from the IP address without revealing or knowing the full IP?
In Stape’s sGTM offering, there is a power-up of Geo-headers. Is there such a thing with GTG? If not, will there be? Is there any “pass-through” setting?
Could you clairify “…based on the IP address you send with the event…”?
I have confirmed in GA4 debug view, that there isn’t any IP address (or partial) in the hit details. As I understand it, if Stape is passing those data points through to GA4, it should show in the debug view.
No, only the last octet is trimmed just like with GA client tracking or via sGTM.
In Stape’s sGTM offering, there is a power-up of Geo-headers. Is there such a thing with GTG? If not, will there be? Is there any “pass-through” setting?
No, these power-ups only work for sGTM so you can use them in your tracking. For any Gateway solutions, they are meant to be a simple server side transition and do not involve any additional flexibility. Just your client tracking easily becomes server side.
I have confirmed in GA4 debug view, that there isn’t any IP address (or partial) in the hit details.
As I understand it, if Stape is passing those data points through to GA4, it should show in the debug view.
The IP address is not available on the client, so you can’t see it in the outgoing hit from web. This applies to any platform or tracking variation.
When you send a hit, the GA server retrieves it from your browser and thus can determine your IP address. If you do not have any additional GA settings active anonymise_ip is written to the GA just without the last octet.