谷歌分析 4 使用 nginx 进行反向代理

Tal*_*sin 2 google-analytics nginx nginx-reverse-proxy google-analytics-4

我有一个主要工作的 nginx 反向代理来处理与 ga4 的接口。我遇到的问题是,我网站的访问者的地理位置数据全部来自弗吉尼亚州阿什本(我的白种人居住的地方)。

这是我的 nginx 配置,其中编辑了特定于站点的数据:

events {
    worker_connections 4096;
}

http {
    set_real_ip_from 10.1.20.0/24;
    set_real_ip_from 10.1.30.0/24;
    real_ip_header X-Forwarded-For;

    log_format main '$remote_addr - $remote_user [$time_local] "$request" '
                    '$status $body_bytes_sent "$http_referrer" '
                    '"$http_user_agent" "$http_x_forwarded_for" ';

    access_log /var/log/nginx/access.log main;
    error_log /var/log/nginx/error.log notice;
    rewrite_log on;

    server {
        listen 80;
        server_name _;
        client_max_body_size 500M;
        location / {
            include uwsgi_params;
            uwsgi_pass 0.0.0.0:8000;
        }

        location /workaround-ga4/ {
            resolver 8.8.8.8;
            proxy_set_header X-real-ip $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            rewrite /workaround-ga4/([^/]+) /g/collect?$args&uip=$remote_addr break;
            proxy_pass https://www.google-analytics.com;
        }
    }
}
Run Code Online (Sandbox Code Playgroud)

我可以在捕获并调试 nginx 重写的 error_log 中看到以下两个条目:

2022/06/21 22:03:36 [notice] 528#528: *1165 "/workaround-ga4/([^/]+)" matches "/workaround-ga4/g/collect", client: 555.555.555.555, server: _, request: "POST /workaround-ga4/g/collect?v=2&tid=G-MYGOOGLEANALYTICSCODE&gtm=555555&_p=555555555&_z=55555&cid=555555555.5555555555&ul=en-us&sr=5555x555&sid=5555555555&sct=55&seg=5&dl=https%3A%2F%2Fmy.site.com%2F&dt=my%20site%20which%20%7C%20is%20having%20trouble%20with%20googleanalytics&_s=1 HTTP/1.1", host: "my-site.com", referrer: "https://my-site.com/"
Run Code Online (Sandbox Code Playgroud)

2022/06/21 22:03:36 [notice] 528#528: *1165 rewritten data: "/g/collect", args: "v=2&tid=G-MYGOOGLEANALYTICSCODE&gtm=555555&_p=555555555&_z=5555555&cid=555555555.5555555555&ul=en-us&sr=5555x555&sid=5555555555&sct=55&seg=5&dl=https%3A%2F%2Fmy-site.com%2F&dt=my%20site%20is%20%7C%20having%20problems%20with%20google%20analytics&_s=1&uip=my.real.ip/&v=2&tid=G-MYGOOGLEANALYTICSCODE&gtm=555555&_p=5555555555&_z=555555&cid=5555555555.5555555555&ul=en-us&sr=5555x555&sid=5555555555&sct=55&seg=5&dl=https%3A%2F%2Fmy-site.com%2F&dt=my%20site%20is%20%7C%20having%20trouble%20with%20google%20analytics&_s=1", client: my.actual.ip, server: _, request: "POST /workaround-ga4/g/collect?v=2&tid=G-MYGOOGLECODE&gtm=555555&_p=5555555555&_z=555555&cid=5555555555.5555555555&ul=en-us&sr=5555x555&sid=5555555555&sct=55&seg=5&dl=https%3A%2F%2Fmy-site.com%2F&dt=my%20site%20is%20%7C%20having%20trouble%20with%20google%20analytics&_s=1 HTTP/1.1", host: "my-site.com", referrer: "https://my-site.com/"
Run Code Online (Sandbox Code Playgroud)

对我来说,这表明重写正在按预期工作 -uip参数被设置为访问者的真实 IP 地址,而不是我的 albs 的 10.1.x IP。

我的 ga4 活动和页面浏览量按预期触发 - 但地理位置显示每个人都来自阿什本。

我错过了什么/不明白什么?

我应该注意,出于性能考虑,我的 google Analytics js 库是通过我的 webapp 在本地加载的,并且不包含在此代理业务中(尽管已进行编辑以将所有 google Analytics api 调用指向 mydomain.com/workaround-ga4/)。

任何帮助是极大的赞赏 :)

Tal*_*sin 5

好的。事实证明,GA4 尚未正式支持uipURL 中的参数。

但是,Google 在 alpha/beta URL 参数前加上_. 改变&uip=$remote_addr我的proxy_passto&_uip=$remote_addr就成功了。

**请注意,这是一个临时解决方案,如果/一旦 Google 决定正式支持该uip参数,或者决定更改 API,它将中断。