Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
carljparker opened this issue Jun 15, 2023 · 1 comment

Comments

@carljparker
Copy link

carljparker commented Jun 15, 2023

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.

svekars pushed a commit to pytorch/pytorch_sphinx_theme that referenced this issue Jun 15, 2023
Re: pytorch/pytorch.github.io#1397

Adding the new GTAG to populate on all sites that use pytorch_sphinx_theme.
pytorchmergebot pushed a commit to pytorch/pytorch that referenced this issue Jun 16, 2023
Re: pytorch/pytorch.github.io#1397
Following the migration to latest google analytics
FYI @malfet
Pull Request resolved: #103766
Approved by: https://github.com/svekars
@cjyabraham
Copy link
Collaborator

Is this issue still waiting for something or can it be closed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants