Priority: Should have
Affects Version/s: None
Fix Version/s: 2.31.1
Sprint:Sprint #131, Sprint #132, Sprint #133
P4 site:All sites
P4 Test Environment:atlas
Last year we started tracking a few click events on selected Planet 4 sites via Google Tag Manager, often based on the element's IDs or classes. This usually demands an extensive custom setup in Tag Manager and is often less accurate.
As suggested by Pieter Vincent and Sagar Deshmukh, we can work with data-* attributes instead of dataLayer events. This should facilitate the implementation while also allowing some more flexibility when setting up the events tags in Google Tag Manager.
The idea is to implement a set of new data attributes with standard values. These will be used later to trigger events and define its category, action and label.
- Example: See image attached for using GTM's dataLayer variable to extract data attributes (gtm.element.dataset.target)
- Implement data-attributes on elements:
- Implement data-attributes with the following standard values:
data-ga-category data-ga-action data-ga-label Search Page Issue Filter
[filter name] Search Page Load More Button [n. results displayed] Search Page Sort By Filter Most Relevant
Search Page Search Button n/a Search Results Title
Call to Action
Here's a screenshot linking the design elements with the data-ga-action standard value:
- [filter name] = name of the issue / tag / category / content checkbox that was clicked by the user
- [n of search results] = number of search results when the user clicked on the Load More button
To view all events standards and data-attributes structure proposed: "P4 Events Standards - 2020 Review"
- Julia should create the Google Tag Manager setup in all P4-NRO's containers.
- Investigate and communicate with NROs using child themes to apply the same data attributes