It would be great to have a README

[fr0der1c]

I found this repo when browsing Docker Hub before I make my own GA proxy. It would be great to have a README here.

[fr0der1c]

I've figured out how to use this container to proxy gtag.js for Google Analytics. However, gtm.js seems not working. Is there any special reason not to use sub_filter in location /t/? I assume using sub_filter in location /t/ and replace https://www.googletagmanager.com/gtm.js with https://my-domai.com/t/gtm.js will make gtm.js work.

[fr0der1c]

I also wonder if this proxy will correctly transport the client's IP (Instead of seeing only proxy's IP address in GA)

[MartijnHols]

Simply start the container, there's nothing to configure.

Subfiltering in /t/ seems like a good idea if any of the files it serves need it. My use case didn't seem to require it.

[fr0der1c]

Hi Martijin, The user's geolocation is all replaced by the proxy server's after applying the proxy in my case. Did you face the same situation?

[MartijnHols]

What info are you missing? I do not use GA that extensively so I haven't missed anything. I do get country info which is good enough;

[fr0der1c]

I can only see one country and one city which is where my proxy server located in my case. I guess that's because I have another reverse proxy before this proxy.

[MartijnHols]

My setup is CloudFlare -> nginx proxy -> this container. The only extra thing I do is use realip in the first proxy to convert the CF IP.

https://support.cloudflare.com/hc/en-us/articles/200170706-How-do-I-restore-original-visitor-IP-with-Nginx-

[fr0der1c]

I see. That makes the difference. I solved the problem by add X-Real-IP header in the front reverse proxy.

[iammattmartin]

I see. That makes the difference. I solved the problem by add X-Real-IP header in the front reverse proxy.

I'd love to know if the fork you made addresses this as i've tried that but still only see the location of the nginx proxy; both with this version and your fork.