Migrate from Universal Analytics (aka "Google Analytics") to Google Analytics 4

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.

The issue names no files, tests, or entry points. Start by locating the website templates or configuration that contain Universal Analytics Tracking IDs, then inventory the PyTorch sites covered by the migration. Done means the covered sites use the Linux Foundation-provided Google Tag ID and continue collecting metrics.