Google Tag Manager templates for Hum Beacons
Hum Beacon
- Download the template
- Navigate to your Tag Manager Account and Workspace at tagmanager.google.com
- Click Templates
- Click New
- Click the 3 dots in the top right
- Select Import
- Choose the template from step 1
- Click Save
- Close the template Editor
- Select Tags
- Select New
- Click Choose a Tag Type
- Select Hum Beacon (under custom)
- Add your fields
- ClientShortName: This will be the client part of client.hum.works/api. So if your Hum instance is usa.hum.works, then you would use usa.
- API Key is your Public Api Key
- Content Source is the identifier for the site that is being tracked (e.g. “cms” or “lms”).
- It is important that the content source be unique for each subdomain being tracked. Hum uses the content source in combination with a content id (usually derived from the page’s path) to create a unique content record in Hum. So if you were to have www.hum.works/help and blog.hum.works/help but both had the same content source of “hum”, all data for both help pages (such as pageviews or score) would be gathered under 1 content record in Hum: hum_help. In this instance www.hum.works should have a source like humwww and blog.hum.works should have a source like humblog.
- Cookie Domain will be the domain of the site. Ideally this will be the least specific domain possible. e.g. If you own www.hum.works and blog.hum.works, the cookie domain for both should be *.hum.works.
- Configure Your Trigger
- If you are not running a cookie consent manager, this will be pageview. If you are, please refer to your Cookie Consent Manager’s documentation of how to configure the trigger for the category in which you’ve placed Hum.
Hum Cookieless Beacon
If you are running a cookie consent manager, you will also want to install Hum’s Cookieless Beacon. This enables Hum to serve Content Recommendations to people who do not accept cookies using only local information.
- Download the template
- Navigate to your Tag Manager Account and Workspace at tagmanager.google.com
- Click Templates
- Click New
- Click the 3 dots in the top right
- Select Import
- Choose the template from step 1
- Click Save
- Close the template Editor
- Select Tags
- Select New
- Click Choose a Tag Type
- Select Hum Cookieless Beacon (under custom)
- Add your fields (Note: These fields will be the same values as for the Hum Beacon above)
- ClientShortName: This will be the client part of client.hum.works/api
- API Key is your Public Api Key
- Content Source is the identifier for the site that is being tracked (e.g. “cms” or “lms”)
- Configure Your Trigger
- This trigger should be fired when the category that Hum is in has not been accepted. Please refer to your Cookie Consent Manager’s documentation of how to configure this trigger.