debugging visitor location headers
Can anyone point me in the direction of directions for debugging why the visitor location headers are not being added when the managed transform is turned on? Geolocation is already turned on.
4 Replies
You're looking at the request headers your origin is recieving? They wouldn't appear in dev tools at all for example, either in Request Headers (as added later) and Response Headers (since they'e just going to origin), has to be a proxied record as well
I am looking at the origin server. I need the visitor location headers added on for a GTM server-side implementation and the docs for adding the headers with cloudflare on the front end has not added the headers on. https://developers.google.com/tag-platform/tag-manager/server-side/enable-region-specific-settings#Cloudflare
Google for Developers
Enable region-specific behavior for tags | Google Tag Manager - S...
What headers do you get on the origin? Do you get CF-Connecting-IP at least?
Not a single cf- header. I think i tracked down the issue and am trying to work out how te resolve it correctly. One of the earlier stages of the implementation was to make the subdomains for the tagging server part of the site domain so that it serves first party cookies but we do not control the root website servers so we are using a cloudflare worker to route a path to the subdomain and I am thinking that worker is not passing on the headers or because of the steup it is bypassing adding the headers