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

[Urgent] Opt-out of "Automatically set up a basic Google Analytics 4 property" #248

Closed
chalin opened this issue Feb 25, 2023 · 11 comments
Closed

Comments

@chalin
Copy link

chalin commented Feb 25, 2023

In March (next week), Google will start creating new GA4 site tags if there's no existing GA4 ID connected to an existing UA ID. But Cilium.io already has a GA4 property.

  1. So, Cilium.io needs to opt out of Google's forced & automatic GA4 migration. To do so:

    Unfortunately, I have access to the panel but I don't have the permissions to opt out. Can you either grant me the permissions or make the change?

  2. Note that according to the Google Tag Assistant, the Cilium docs are also being tracked via another UA property with ID UA-17997319-1. I don't have access to that account. You'll need to opt out of there too.

  3. If you have access to the ReadTheDocs account for the Cilium docs, it might be a good idea to remove the UA IDs from the config there.

For context regarding the GA4 opt-out issue, see:

/cc @nate-double-u @lizrice @qmonnet

@qmonnet
Copy link
Member

qmonnet commented Feb 27, 2023

I don't have access to these.

@xmulligan Hi, do you have access and required permissions in the Google Analytics panel to help? Otherwise, do you know who does?

Cc @aanm regarding item 3 and access to ReadTheDocs

@lizrice
Copy link
Member

lizrice commented Feb 27, 2023

I've turned off "Automatically set up a basic GA4 property" for UA-96283704-1

I can't see any properties with the ID UA-17997319-1 in the admin panel. I wonder if this ID is some kind of default value in a Sphinx config file that has been propagated inadvertently? Searching for it I found quite a few references for example https://nbsphinx.readthedocs.io/en/0.2.5/conf.py, https://github.com/pyNLO/PyNLO/blob/master/config.py, https://docs.epics-controls.org/projects/pva2pva/en/latest/doxygen/conf_8py_source.html etc

@chalin
Copy link
Author

chalin commented Feb 28, 2023

Thanks @lizrice.

I can't see any properties with the ID UA-17997319-1 in the admin panel. I wonder if this ID is some kind of default value in a Sphinx config file that has been propagated inadvertently?

In that case, would it be possible to remove that ID from the Sphinx config?

@qmonnet
Copy link
Member

qmonnet commented Feb 28, 2023

@chalin Do you mean the googleanalytics_id variable in Documentation/conf.py should be gone altogether? I suppose this means the ID we use is defined somewhere in that case?

I can take care of the removal from conf.py if that's what we need

@chalin
Copy link
Author

chalin commented Feb 28, 2023

@chalin Do you mean the googleanalytics_id variable in Documentation/conf.py should be gone altogether?

No, that stays.

What needs to be removed is the UA ID set for global_analytics_code in the RTD config, e.g.:

context = {
    ...
    'user_analytics_code': '',
    'global_analytics_code': 'UA-17997319-1',
   ...
}

Change the setting to 'global_analytics_code': '' (or drop the both analytics parameters if that works).

@chalin
Copy link
Author

chalin commented Feb 28, 2023

Since we're talking about require changes, there is this that needs to be done:

@aanm
Copy link
Member

aanm commented Mar 1, 2023

I've removed UA-96283704-1 from the readthedocs admin panel

@chalin
Copy link
Author

chalin commented Mar 1, 2023

@aanm or @lizrice can you remove UA-17997319-1 from the config too?

@aanm
Copy link
Member

aanm commented Mar 3, 2023

@chalin I don't see the UA-17997319-1 anywhere in the readthedocs admin panel nor we do have that set in our Documentation config

@chalin
Copy link
Author

chalin commented Mar 3, 2023

@aanm - thanks for confirming. Investigating this a bit more, it seems to be a RTD ID, so we're good! Thanks all!

@chalin chalin closed this as completed Mar 3, 2023
@xmulligan
Copy link
Member

Thanks for your help @chalin !

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

5 participants