-
Notifications
You must be signed in to change notification settings - Fork 286
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
GA4 Widgets: Update "Engaged Sessions" metric name title to read "Engagement rate". #6693
Comments
All of the existing metrics, as well as metrics in the GA4 Figma mock, use Title Case for their names: I'm guessing "Engagement rate" here was an oversight and not something deliberate; if it wasn't and we want to change the case of these metrics it might be better to do that all at once—it will be confusing having them be inconsistent. I've adjusted the case in the ACs and IB, and pinged @techanvil just to make sure it wasn't intentional. IB ✅ |
Thanks @tofumatt - good spot, it should indeed be "Engagement Rate". |
Note that while reviewing the PR for this issue I noticed the |
QA Update ✅
Note -
|
Feature Description
As discussed on Slack, having switched from the
engagedSessions
metric toengagementRate
, we should also update the relevant titles on the GA4 widgets that use it, from "Engaged Sessions" to "Engagement rate".Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance criteria
engagementRate
metric should use "Engagement Rate" for the corresponding metric name/column title.Implementation Brief
ModulePopularPagesWidgetGA4
,extract-dashboard-data.js
,overall-page-metrics.js
,SearchFunnelWidgetGA4
:'Engaged Sessions'
and change it to'Engagement Rate'
ModulePopularPagesWidgetGA4
andSearchFunnelWidgetGA4
, also change the ID fromengaged-sessions
toengagement-rate
. This isn't part of the ACs but helps with consistency.Test Coverage
QA Brief
ga4Reporting
and check the Widgets mentioned in the AC for the change from'Engaged Sessions'
to'Engagement Rate'
.Changelog entry
The text was updated successfully, but these errors were encountered: