print

Integrating HubSpot with TRUENDO CMP in Google Tag Manager

Objective: Use TRUENDO as the central consent management solution while integrating HubSpot in a compliant manner. HubSpot’s native cookie banner will be disabled, and TRUENDO will handle all consent decisions and set the HubSpot consent state accordingly.

Key Steps Overview#

  1. Disable HubSpot’s Cookie Banner:
    Add window.disableHubSpotCookieBanner = true; before HubSpot scripts load, ensuring HubSpot doesn’t show its own banner and leaves consent decisions to TRUENDO.
  2. Control HubSpot Consent via TRUENDO:
    Use TRUENDO’s cookie callback (TruendoCookieControlCallback) to map TRUENDO consent categories (e.g., preferences, marketing, statistics) to HubSpot’s consent fields (analytics, advertisement, functionality).
  3. Remove async from HubSpot Script:
    Ensure that HubSpot’s script loads after TRUENDO sets consent states, so that HubSpot tracking respects these decisions.
  4. Add a Standard Trigger in GTM:
    For example, use an “All Pages” trigger for your HubSpot tag. The script will load, but actual analytics/advertisement tracking only runs if TRUENDO grants consent.

Prerequisites#

  • TRUENDO Account & Integration: Ensure TRUENDO CMP is already integrated into your website.
  • GTM Access: You can edit your Google Tag Manager setup.
  • HubSpot Script: You have HubSpot’s tracking code ready to be inserted, without async.
  • Consent Mode (If Using Advanced Setup): If using Google Consent Mode, ensure you’ve followed TRUENDO’s advanced consent mode instructions.

  1. Disable HubSpot Cookie Banner & Prepare Consent Callback:

    Insert the following code into your TRUENDO GTM tag, replacing any previous snippets. This code:

    • Disables HubSpot’s banner with window.disableHubSpotCookieBanner = true;
    • Uses TruendoCookieControlCallback to set HubSpot consent via setHubSpotConsent.
    <script>
  // Disable HubSpot's native cookie banner
  window.disableHubSpotCookieBanner = true;

  window._hsp = window._hsp || [];

  function TruendoCookieControlCallback(cookieObj) {
    // Map TRUENDO categories to HubSpot consent fields
    // HubSpot consent fields: analytics, advertisement, functionality
    // Example mapping:
    // statistics -> analytics
    // marketing -> advertisement
    // preferences -> functionality (optional, depending on your needs)

    const analyticsConsent = cookieObj.statistics ? true : false;
    const advertisementConsent = cookieObj.marketing ? true : false;
    const functionalityConsent = cookieObj.preferences ? true : false;

    // Update HubSpot’s consent state
    window._hsp.push([
      'setHubSpotConsent',
      {
        analytics: analyticsConsent,
        advertisement: advertisementConsent,
        functionality: functionalityConsent
      }
    ]);

    // Optionally push dataLayer events for other GTM triggers if needed
    if (cookieObj.preferences) {
      dataLayer.push({ event: "truendo_cc_preferences" });
    }
    if (cookieObj.marketing) {
      dataLayer.push({ event: "truendo_cc_marketing" });
    }
    if (cookieObj.statistics) {
      dataLayer.push({ event: "truendo_cc_statistics" });
    }
    if (cookieObj.social_content) {
      dataLayer.push({ event: "truendo_cc_social_content" });
    }
  }
</script>
<!-- TRUENDO Privacy Center -->
<script id="truendoPrivacyPanel" type="text/javascript" src="https://cdn.priv.center/pc/app.pid.js" data-siteid="YOUR_SITE_ID"></script>
<!-- End TRUENDO Privacy Center -->

    Note: Replace YOUR_SITE_ID with your actual Site ID from the TRUENDO console.

  2. Remove async from HubSpot Script:
    Ensure the HubSpot tracking code does not have async. It should load in a controlled fashion so that TRUENDO’s consent decisions apply before HubSpot initiates tracking.

  3. Add a Trigger to HubSpot Tag: In GTM, add a standard trigger (e.g., All Pages) to your HubSpot tag. This ensures HubSpot script loads on all pages, but actual data collection (like analytics) only starts if TRUENDO grants consent.

If you’re using Google Consent Mode along with TRUENDO, incorporate the relevant gtag consent updates as per TRUENDO’s advanced consent mode instructions. In the callback, instead of _hsq.push(['doNotTrack', ...]), we use setHubSpotConsent as shown above.

The logic remains the same: TRUENDO sets consent categories, which then trigger setHubSpotConsent calls to HubSpot. HubSpot acts accordingly, respecting analytics, advertisement, and functionality consent states.

Verification and Testing#

  • Clear Cookies & Cache: Test in a fresh browser session to simulate a new user.
  • Visit Your Website: Check if the HubSpot cookie banner is absent (it should be, since window.disableHubSpotCookieBanner = true; is set).

  • Consent Decisions:

    • If user denies analytics (statistics), HubSpot’s analytics field is false, meaning no analytics tracking.
    • If user later grants marketing, HubSpot’s advertisement field switches to true, enabling ad-related cookies.

  • Check Developer Tools:

    • Open browser dev tools to see which requests HubSpot makes.
    • Confirm that analytics or advertisement requests do not run if user denies those categories.

Summary#

By integrating TRUENDO CMP and HubSpot via GTM with these updated instructions, you:

  • Centralize all consent decisions in TRUENDO.
  • Disable HubSpot’s native cookie banner and rely on TRUENDO for privacy compliance.
  • Dynamically set HubSpot’s consent states based on TRUENDO user choices.
  • Maintain compliance and build trust by respecting user preferences at all times.

If you need further guidance, review TRUENDO and HubSpot documentation or contact TRUENDO support for assistance.

×