HubSpot
Intastellar Consents integrates with HubSpot so marketing and tracking respect consent. Wire HubSpot like any other non-essential stack: CMP before HubSpot scripts, then fire only when the visitor’s choices allow it.
Prerequisites
- Quickstart (or equivalent) so
window.INTA+uc.jsload early in<head>. - Clarity on which HubSpot features you use (tracking code, forms, chat) and which consent purposes they map to.
Recommended: Google Tag Manager
- Deploy the CMP on Consent Initialization — see Google Tag Manager.
- Add HubSpot tags (or Custom HTML) with triggers that match accepted marketing / analytics consent, per your policy.
- Avoid loading the HubSpot embed globally on All Pages before consent unless your legal review says otherwise.
HubSpot Cookie API / CMP behaviour
HubSpot’s own documentation describes how their tags interact with cookies and consent tools. Follow HubSpot + CMP guidance alongside Intastellar’s load order: the CMP supplies consent state; your GTM or site must not treat tracking as granted before choice.
Verify
- Network / Application: HubSpot-related requests and cookies should not appear as fully active before accept (for the purposes you restrict).
- After accept, forms and tracking should work as configured.
Related
Last updated