No correct geolocation data in GA4. - same origin setup

1

I have the same-origin config with Stape but it seems no correct geolocation data in GA4. In GA4 much of the traffic and purchases is show to be from Germany …but all my clients are from Hungary.
I also have Cloudflare site-proxy .

I ve found at Exclude internal traffic - #3 by adessoOM that

“We are aware of the basic functionality, but due to an increased level of privacy we do not send client IP addresses to GA4 and need to do the filtering / flagging on the server where the client-side request is collected.”

In the logs of Stape server I can see client data ( bcs GEO Headers

powerup ) but clientIp is a Cloudflare IP ( “172.68.224.220” )

"request_X-Gclb-Country": "HU",
"request_X-Gclb-Region": "BU",
"request_X-Geo-City": "Budapest",
"request_X-Geo-Country": "HU",
"request_X-Geo-Ipaddress": "89.202.178.111",
"request_X-Geo-Postalcode": "1011",
"request_X-Geo-Region": "BU",
"ClientIP": "172.68.224.220"

}

I ve seen some people doing a GTM Transformation for an Augment Event transformation, that overrides the ip_override event data value with a generic country IP for the user IP . Do I really need to do this kind of things for correct geolocation data in GA4 when using same-origin Stape config?

Thanks,

2

Can you please confirm that you use configuration like described here https://help.stape.io/hc/en-us/articles/21396416759837-How-to-configure-the-same-origin-custom-domain-in-sGTM-Cloudflare-nginx#h_01J73V90VMDD030GQCGQEP2K5W

?

look like you do not passing static, header name ‘X-From-Cdn’ with value ‘cf-stape’

3

You are right . I didnt had the passing static, header name ‘X-From-Cdn’ with value ‘cf-stape’ .

This step I guess was later added to the tutorial because I am pretty sure many months ago when I had followed the tutorial for ‘same origin’ it was not there…

Thanks,