App Engine Headers – It seems that App + Web currently does

It seems that App + Web currently does not allow you to overwrite a user’s IP address in an outgoing request to Google servers, which means that App + Web processes all requests as if they came from your server container. However, the geolocation data of App Engine must match the identification parameters used by Google Analytics, which is a bit annoying without the search table variable. When the Server Container is created in Google Tag Manager, GTM creates for you an implementation of App Engine on Google Cloud platform. In any case, I have no doubt that the correct IP solution will soon be introduced in the App + Web tags, but you can still send this information in the form of metadata, as it may be useful to see if the geolocation results differ between App Engine and App + Web. To get them, you need to create new custom variables in the server container, each variable is of Request Header type and the value of one of these headers is determined. In this article I will show you how to obtain these header values and pass them to the labels that are activated in the server container. You can also add geolocation information to universal analysis labels using the Measurement Protocol &geoId parameter. This article was inspired and influenced by discussions with Google engineers and programmers involved in tagging on the server side, especially Adam Halbardyer. One potentially useful thing the application engine does is to decorate all incoming HTTP requests with HTTP headers that can be used in an application. These headers contain geolocation headers based on the IP address of the machine that sent the results. NOTE: I do not know how the Application Engine solves the geolocation or how Application + Web does it. In this way, you can geolocalize a user without having to follow the Google IP address. The initiative to write this article arose while working with the ip_override and user_agent commands in another article. This document only states that the WHOIS database is not used for geolocation.