HubSpot

What it does. Tells HubSpot's tracking code whether it may set cookies and track the visitor.

Consent category. analytics.

How it works

HubSpot's tracking queue takes a do-not-track instruction rather than a consent one, so the bridge pushes the appropriate form on each consent update:

_hsq.push(['doNotTrack', { track: true }]);

When analytics is denied it pushes the bare form, which is HubSpot's way of saying tracking is off:

_hsq.push(['doNotTrack']);

If _hsq doesn't exist the bridge creates it as an array, so the call survives arriving before HubSpot's script.

Setup

On by default. Toggle it under Vendor Consent Signals on the banner's App Integrations page, then publish.

Testing

Accept analytics and look for the hubspotutk cookie. Reject it, clear cookies, reload, and confirm it doesn't come back. You can also inspect the queue:

window._hsq

The pushed doNotTrack entries are visible there before HubSpot processes them.