Refactor Google Tag Manager integration

[stephenyeargin]

This pull request significantly refactors the analytics integration logic to improve privacy consent handling and script loading behavior. The main focus is to ensure that tracking scripts (HubSpot, Google Tag Manager, and Reo) are only loaded after the appropriate user consent is granted, and to make the consent logic more robust and maintainable.

Key improvements and changes:

Consent Management & Script Loading Logic:

• Replaces the static HubSpot embed code with a dynamic loader that only injects the HubSpot script after verifying user consent, preventing tracking scripts from loading before consent is granted. [1] [2]
• Adds helper functions (isLocalHost, isGrantedValue, firstDefined, etc.) to determine consent state from both the HubSpot consent listener and cookies, and to prevent script loading on localhost.
• Introduces a centralized handleConsentState function that ensures tracking scripts are loaded only if consent is granted, and blocks tracking on local environments.

Google Tag Manager (GTM) Consent Enforcement:

• Implements a default-deny consent policy for GTM by calling gtag('consent', 'default', ...) before any scripts load, and updates consent dynamically based on user actions. [1] [2]
• Ensures GTM is initialized with proper consent events and does not load until consent is explicitly granted.

Robust Consent State Handling:

• Adds logic to parse consent state from both the HubSpot listener and the __hs_cookie_cat_pref cookie, ensuring returning users’ preferences are respected. [1] [2]
• Ensures all consent categories (analytics, ads, personalization) are handled and updated atomically to avoid inconsistent states.

These changes make the analytics integration more privacy-compliant, robust, and maintainable.

[github-actions]

🚀 Deployed on https://ae7daf936da7f1929b1c5f0e6a51c5488e1defe5--floxdocs.netlify.app