A note before you begin: You’ll want to think about how you’d like to trigger the Hum Beacon to fire. If you use Cookie Consent management, you’ll want the beacon to trigger based on the user’s cookie consent decision. To learn more about Hum’s cookie consent best practices, click here. There is also a “Cookieless Beacon” which we recommend installing (instructions below the main beacon instructions in this doc) as it allows for Hum’s content recommendations to run using a browser’s local storage vs. a cookie.

Hum Beacon

  1. Download the template
  2. Navigate to your Tag Manager Account and Workspace at tagmanager.google.com
  3. Click Templates
  4. Click New
  5. Click the 3 dots in the top right
  6. Select Import
  7. Choose the template from step 1
  8. Click Save
  9. Close the template Editor
  10. Select Tags
  11. Select New
  12. Click Choose a Tag Type
  13. Select Hum Beacon (under custom)
  14. Configure the required fields carefully (this is where most user errors occur):

ClientShortName Field:

  • Enter ONLY the subdomain portion of your Hum instance URL
  • Example: If your Hum instance is usa.hum.works, enter usa
  • Example: If your Hum instance is client123.hum.works, enter client123
  • Do NOT include .hum.works or any other parts of the URL

API Key Field:

  • Enter your Public API Key (not your private key)
  • This should be provided by your Hum CSx rep

Content Source Field:

  • This is a unique identifier for the specific site/subdomain being tracked
  • CRITICAL: Each subdomain must have a unique Content Source value
  • Use descriptive names like cms, lms, blog, www, help, etc.
  • Why this matters: Hum combines Content Source + page path to create unique content records
  • Common mistake to avoid: Using the same Content Source for different subdomains will merge their data incorrectly
  • Example scenario:
    • If www.yoursite.com/help uses Content Source main
    • And blog.yoursite.com/help also uses Content Source main
    • Both pages will be tracked as the same content record, mixing their analytics data
  • Correct approach:
    • www.yoursite.com should use Content Source www or main
    • blog.yoursite.com should use Content Source blog
    • help.yoursite.com should use Content Source help

Cookie Domain Field:

  • Enter the broadest domain that covers all your subdomains
  • Use the format with leading dots: .yourdomain.com
  • Example: If you have www.hum.works and blog.hum.works, use .hum.works
  • This allows the cookie to work across all your subdomains

15. 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.

  1. Download the template
  2. Navigate to your Tag Manager Account and Workspace at tagmanager.google.com
  3. Click Templates
  4. Click New
  5. Click the 3 dots in the top right
  6. Select Import
  7. Choose the template from step 1
  8. Click Save
  9. Close the template Editor
  10. Select Tags
  11. Select New
  12. Click Choose a Tag Type
  13. Select Hum Cookieless Beacon (under custom)
  14. Configure the required fields (use the exact same values as your Hum Beacon above):
    • ClientShortName: Same subdomain value used in the main Hum Beacon
    • API Key: Same Public API Key used in the main Hum Beacon
    • Content Source: Same unique identifier used in the main Hum Beacon
  15. 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.