As the final body of work relating to the Analytics Conversion Tracking (ACR) epic, internal measurement/tracking should be implemented so that Site Kit can better understand the uptake, usage and success/failure of this feature. This tracking should leverage existing tracking means used throughout the codebase.
This tracking involves updates to existing KMW tracking infrastructure/implementations, as well as the introduction of new tracking against ACR elements introduced within this epic. Tracking will cover the following areas:
Any inline CTA’s and/or banners introduced as part of this epic should also be tracked as follows:
Banner/CTA seen
Banner/CTA clicked (on CTA)
Banner/CTA closed
Banner/CTA dismissed
It should be noted that none of the existing events track identifiable metric slugs. This will make it challenging to ascertain the success of this feature, as it will not be possible to determine if the added widgets are News KMW vs ACR KMW. For this reason, it is proposed that the following updates be made to internal tracking relating to KMW:
Widget slugs be tracked for events directly applicable to the metric selection or tile itself
Data loading errors and retry attempts within widgets
Specific event for when ACR metrics are present within the saved metric selection panel/sidebar
Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance criteria
Internal tracking is to be implemented on all new banner introduced as part of the ACR work
The existing trackEvent function should be leveraged, as it is throughout the Site Kit application
The following events should be tracked as a result of interactions with the new ACR banners:
dismiss_notification - Tracked when an ACR KMW banner is dismissed
confirm_{applicable CTA action slug} when a CTA button within an ACR banner is clicked
Said banners included should be those surfaced within the main dashboard area, as well as within admin settings for Key Metrics
Additionally, the following (existing) KMW tracking actions are to be supplemented to support a more informatory tracking overview to gauge ACR success:
The existing metrics_sidebar_save tracked event within assets/js/components/KeyMetrics/MetricsSelectionPanel/Footer.js is updated to an event name that explicitly tracks that the saved metrics include ACR metrics. The existing event will remain as is, regardless of metrics saved, with this additional event being tracked, allowing a differential of ACR vs total metric sidebar saves.
Feature Description
As the final body of work relating to the Analytics Conversion Tracking (ACR) epic, internal measurement/tracking should be implemented so that Site Kit can better understand the uptake, usage and success/failure of this feature. This tracking should leverage existing tracking means used throughout the codebase.
This tracking involves updates to existing KMW tracking infrastructure/implementations, as well as the introduction of new tracking against ACR elements introduced within this epic. Tracking will cover the following areas:
Any inline CTA’s and/or banners introduced as part of this epic should also be tracked as follows:
It should be noted that none of the existing events track identifiable metric slugs. This will make it challenging to ascertain the success of this feature, as it will not be possible to determine if the added widgets are News KMW vs ACR KMW. For this reason, it is proposed that the following updates be made to internal tracking relating to KMW:
Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance criteria
trackEventfunction should be leveraged, as it is throughout the Site Kit applicationdismiss_notification- Tracked when an ACR KMW banner is dismissedconfirm_{applicable CTA action slug}when a CTA button within an ACR banner is clickedmetrics_sidebar_savetracked event withinassets/js/components/KeyMetrics/MetricsSelectionPanel/Footer.jsis updated to an event name that explicitly tracks that the saved metrics include ACR metrics. The existing event will remain as is, regardless of metrics saved, with this additional event being tracked, allowing a differential of ACR vs total metric sidebar saves.Implementation Brief
Test Coverage
QA Brief
Changelog entry