Version 3.2 of the Standard Mason GTM container has been released. You can find the new version on the Mason GTM Container page.
The new version includes tracking of user interaction with expandable content areas and adds additional folders to improve organization.
Changes in this Version
Expandable Content Areas
Many websites use expandable content areas to hide sections of content until it is clicked-on by the user. This version of the GTM container includes tracking of when expandable content area triggers are clicked.
Triggering HTML elements are identified by using a CSS selector. When an element matching this selector is clicked, tracking information is sent in the following format:
GA Hit Type: event
Category: expandable content
Action(s): open, close, indeterminate
Label: [Actual text of element which is clicked to trigger the expandable content area]
This trigger is pre-configured by default to work for Mason standard Drupal websites. If your website is on a different platform, and uses expandable content areas, set this trigger criteria to a CSS selector which will identify the elements used to activate expandable content areas on your website.
Beyond simply providing more information about user interaction with these expandable content areas, this change should also make bounce rates more accurate. For example, consider a session in which a user visits a single page, interacts with an expandable content area, and then leaves the site. If expandable content interactions were not tracked, this visit would appear as a bounce. However, now that the GTM container is tracking interactions with the expandable content area, this visit would generate a second “expandable content’ event hit after the initial page view hit, and therefore would not be counted as a bounce.
I have added a few new folders to improve organization and make implementation easier:
- All critical implementation setting are now found in the folder “00 standard configuration settings”. These are the critical settings that need to be set (or confirmed) when the GTM container is implemented on a new website. Having them all in one place makes it easier to implement this container on a new website.
- Elements (tags, triggers, variables, etc.) which are not part of the standard tracking implementation, but are unique to the website in questions, should be included in the folder called “01 material unique to this website”. This will provide for extensibility of tracking to meet the needs of individual websites, while keeping this content separate from the standard tracking elements.
- Many units are now working with third-party marketing vendors, who, in many cases, are granted direct access to the website’s GTM container. To help keep their additions separate from our standard tracking elements, all elements added by third-party vendors should be added to the folder “02 third-party additions”.