-
Notifications
You must be signed in to change notification settings - Fork 14.2k
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
Ensure that page-feedback events are usable with Google Analytics 4 #37657
Comments
Thanks for filing this @chalin. I also noticed that the data we are currently getting from the feedback form is not reliable. I opened a bug here: #37201. I've done a bit of investigating to try and remove the bot data, but its looking like this is not as straight forward as i was hoping. I dont have a solution yet, but wanted to make sure to note the issue here to remind ourselves about it :) |
/triage accepted |
Progress: I've defined an Event Modification rule through the analytics console interface. It changes the event name of Docsy page-feedback events to So far it is working in realtime in the debugger. It also is appearing in the Realtime overview events panel: Here's an example of the parameters of one of these modified events: I'm not sure how we can conveniently see |
Thanks for working on this @chalin! Just so i understand the numbers, does the Previously, the clicks value was calculated as I'm not sure if GA4 tracks values in the same way or if we are passing the value correctly for GA4. We may need to define a metric/dimension to be able to use this data in a report 🤔 |
Oh, you're right, I'm missing a data (missing a column). I've updated the screenshot, adding an "Event count" column. PTAL. I've found it challenging to create reports in GA4. Maybe it's just a steep learning curve, or maybe the i/f needs improvements (or both) 😄 |
There might be a better way to visualize that data. If there is, I haven' t found it yet. 🤷♂️ ... But I'll keep looking! |
I was just poking around a bit in GA4 just now, and it seems a lot like creating graphs in Google Data Studio. Which is NOT easy either. I used a pre made Data studio template when i put together the analytics dashboard for the Kubernetes site, which is the only reason we have the pretty graphs. So i understand, the |
I'm glad that you found that GDS template then! (Thanks for sharing your experience with GDS and validating that you found that challenging too. My understanding of the data matches yours. |
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:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
Page-feedback events are currently being processed thanks to a workaround so I'll close this issue now. Once Docsy is fixed to address this issue, and it is updated here, things will fall into place. |
FYI, the following is targeted for the next release of Docsy (0.8.0): |
This can be viewed as a subtask of #35299 or a followup task, which is why I'm creating a separate issue. I'd vote for the latter.
While the website's custom layouts/partials/feedback.html is already using the
gtag.js
library, the custom event name (click
) conflicts with GA4's use of the same name to measure outbound clicks.It isn't clear to me yet if we can still (relatively easily) extract the page-feedback data or, for example, write custom GA4 i/f code to rectify this name clash, but IMHO, it would be easier to choose an event name that doesn't clash.
This is also an issue for Docsy, see google/docsy#1302. I'll likely be exploring solutions for Docsy, and can port the required changes here.
/cc @a-mccarthy @nate-double-u
The text was updated successfully, but these errors were encountered: