Migrate from Universal Analytics (aka "Google Analytics") to Google Analytics 4
还没有人认领这个 Issue。
评估
调研方向
该 issue 未指出任何文件、测试或入口点。首先定位包含 Universal Analytics Tracking IDs 的网站模板或配置，然后清点此次迁移涵盖的 PyTorch 网站。涵盖的网站使用 Linux Foundation 提供的 Google Tag ID 并继续收集指标，即表示完成。
由索引模型根据 Issue 内容生成。
描述
In order to continue to obtain metrics data for our PyTorch websites, we need to migrate to Google Analytics 4.
Historically, we have used Google's Universal Analytics product to collect page view, visitor, and other metrics for the PyTorch collection of websites. On July 01, 2023, Google will stop supporting Universal Analytics. In order to continue to obtain metrics, we'll need to migrate our websites to Google Analytics 4.
Part of the migration requires updating our pages to use a new type of ID tag--specifically, a Google Tag ID instead of the Tracking ID used by Universal Analytics. (Google Tag IDs are recognizable by their "G-" prefix; Universal Analytics Tracking IDs have a "UA-" prefix.)
Because PyTorch "core" is now under the governance of Linux Foundation (LF), they have collaborated with us on the migration: LF obtained a Google Tag ID to use for our websites.
Note that not all PyTorch sites and content are under the governance of LF. For example, Meta Platforms, Inc retains governance of the PyTorch domain libraries, such as TorchAudio, as well as the PyTorch Tutorials. Nevertheless, because, historically, we have taken a unified approach in which we collect metrics across all the PyTorch sites using a single account and a single ID, our plan is to continue along this path. What this means is that LF and Meta will each have access to metrics information for sites that are governed by the other. We don't anticipate that this will create issues. Indeed, if we do identify issues, it should be straightforward to generate one or more additional IDs in order to partition the metrics data appropriately.
- 主要语言
- HTML
- 星标
- 286
- 派生
- 318
- 平均合并
- 5 天 18 小时
- 30 天内合并 PR
- 4
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
pytorch/pytorch.github.io 的其他 Issue
-
难度 1/5 1-3 小时 新手友好度 82/100
pytorch/pytorch.github.io#2135 ·
-
难度 2/5 1-3 小时 新手友好度 84/100
pytorch/pytorch.github.io#2133 ·
-
难度 2/5 1-3 小时 新手友好度 72/100
pytorch/pytorch.github.io#2117 ·
-
难度 2/5 1-3 小时 新手友好度 65/100
pytorch/pytorch.github.io#2065 ·
-
Dead link未关闭
难度 1/5 1 小时以内 新手友好度 65/100
pytorch/pytorch.github.io#1256 ·
查看 pytorch/pytorch.github.io 的全部 Issue
相似的 Issue
-
P4: low
难度 2/5 1-3 小时 新手友好度 82/100
jeffknupp/association#523 ·
-
难度 2/5 1-3 小时 新手友好度 62/100
umami-software/umami#4637 ·
维护者通常 3 天内回复
-
ux
难度 2/5 1-3 小时 新手友好度 64/100
evcc-io/evcc#34969 · 1 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
-
ReferenceArea is drawn from the left edge of the chart when an edge is outside the Brush range可能已有人在做 @maxymlyskov 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 87/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 64/100
mitchelloharawild/ggtime#39 ·