Feedback form on pages includes clicks from bots in Google Analytics

[a-mccarthy]

This is a Bug Report

Looking at the data from out feedback form, it appears that a lot of data is from bots. Google Analytics has a way to filter bot activity, https://support.google.com/analytics/thread/16422940?hl=en. But we do not have that enabled

It looks like bot activity is turned off by default in the next version of Google Analytics, https://support.google.com/analytics/answer/9888366?hl=en. We are in the process of migrating to this version in https://github.com/kubernetes/website/issues/35299.

Problem:

It looks like bot activity is throwing off users feedback in out feedback forms. For example, in the screen shot, this page has 41 response on the feedback form, but they are all from the same day.

Proposed Solution:

Exclude bot data from the charts, https://support.google.com/analytics/answer/9888366?hl=en.

Page to Update: This would be a change in Google Analytics.

[a-mccarthy]

/assign

I can take care of turning on the filter. but wanted to log the bug so we had a record of this being an issue. And make sure to check that the bot filtering is happening correctly in the new Google Analytics set up.

[a-mccarthy]

also, feedback for is located on the bottom of doc pages: https://kubernetes.io/docs/tutorials/. and tracks "Was this page helpful".

Until we get the filtering figured out, we aren't able to accurately see if pages are helpful/unhelpful.

im also not an expert on bots. so if this behavior is indicative of an different issue, please let me know :)

[sftim]

/triage accepted

[a-mccarthy]

i tried adding the filter, but still saw the same results. Going to keep researching this to see if there is a better answer

[chalin]

I've promoted this issue upstream:

• https://github.com/google/docsy/issues/1303

I think that we'll need a programatic solution, filtering probably won't be effective -- glad to be proven wrong though.

[a-mccarthy]

Thanks @chalin!

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[chalin]

This is still relevant. /cc @a-mccarthy

[vaibhav2107]

/remove-lifecycle stale

[k8s-triage-robot]

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.