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

Remove GA from website #925

Closed
antross opened this issue Jul 30, 2020 · 4 comments · Fixed by #927
Closed

Remove GA from website #925

antross opened this issue Jul 30, 2020 · 4 comments · Fixed by #927

Comments

@antross
Copy link
Member

antross commented Jul 30, 2020

Triggered by questions in #913 and discussed at our sync last week, we want to remove Google Analytics from the website because:

  1. Nobody is currently looking at the GA data
  2. The data we do look at is gathered through webhint-specific code and stored in Application Insights
  3. We want to only gather data we know we're going to use and can explicitly make anonymous to maximize user privacy
@molant
Copy link
Member

molant commented Jul 30, 2020

Is there a plan to track click through from the tools to the documentation pages?

sarvaje pushed a commit to sarvaje/webhint.io that referenced this issue Jul 30, 2020
@sarvaje sarvaje mentioned this issue Jul 30, 2020
2 tasks
@antross
Copy link
Member Author

antross commented Jul 31, 2020

Is there a plan to track click through from the tools to the documentation pages?

Yes for browser integrations we're working on. We don't currently have work tracking this from the other entry points (e.g. the browser extension) but I suspect that would be useful as well. We'd just need to update the extension to append a source param and we could follow that through. Or did I misunderstand your question?

@molant
Copy link
Member

molant commented Jul 31, 2020

We'd just need to update the extension to append a source param and we could follow that through.

My question was more about what is going to record how many visits come with that param. If the plan is to report it via AppInsights that's fine.
Another problem is the data retention, especially if at one moment there are OKRs about any of these values (although we already have that problem).

@antross
Copy link
Member Author

antross commented Aug 3, 2020

My question was more about what is going to record how many visits come with that param. If the plan is to report it via AppInsights that's fine.

@molant, yes the plan is to report it via App Insights (and was implemented here #913)

@hxlnt hxlnt added this to the 2008-2 milestone Aug 7, 2020
antross pushed a commit that referenced this issue Aug 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants