Works with your stack
Cookie consent for HubSpot
one loader, many tools
The HubSpot plugin adds HubSpot’s loader to every page once an account is connected. That loader brings HubSpot tracking and more. The plugin has no consent setting in WordPress.
By HubSpot, Inc. · hubspot.com · WordPress.org
Is this your product? Tell us if anything here is out of date. Write to us
HubSpot
WordPress plugin
- Tested version
- 11.3.75
- How
- Tested automatically around each Cookie Rocks version
- Last test
- 7 November 2026
- Latest version
- 11.3.75 tested
- Active installs
- 200,000+
What HubSpot adds to your visitors’ browser
Not testable without an account: the HubSpot tracking code needs a connected HubSpot portal.
What matters for consent with HubSpot
Consent lives in HubSpot
The plugin has no consent setting and no WP Consent API code. The only consent option is HubSpot’s own banner, set up in your HubSpot account.
Forms and meetings apart
HubSpot forms and meeting pages load from HubSpot’s servers on their own, separately from the loader.
The optional proxy
The plugin can relay HubSpot requests through your site. Then HubSpot’s cookies come from your own domain. It is off by default.
Cookie Rocks with HubSpot
- Holds the scripts it adds to your pages, such as tags, pixels or a chat, until the visitor consents. In advanced Consent Mode, Google’s tags load with consent denied instead.
What our tests found on HubSpot
Set before the choice · HubSpotThe HubSpot plugin loads HubSpot on every page with no consent setting
Once an account is connected, the loader is added to every front page. Consent exists only through HubSpot's own banner, set in the HubSpot portal. Forms and meetings load separately.
Read in its code, 16 October 2026, HubSpot 11.3.75.
Full detail
Once a HubSpot account is connected, the HubSpot plugin adds the loader js.hs-scripts.com/<portalId>.js (or js-eu1..., id hs-script-loader, async defer) in the footer of every front page, plus an inline _hsq.push(['setContentType']) in the head. It has no consent setting in WordPress and no WP Consent API code; consent handling exists only through HubSpot's own banner configured in the portal. Forms load from <hublet>.hsforms.net and meetings from static.hsappstatic.net, separately.
Depends on a setting · HubSpotHubSpot's optional proxy makes HubSpot cookies come from the site's domain
setting “proxy mappings” · by default: off
Off by default. When on, WordPress relays HubSpot addresses, with HubSpot's cookies, so its requests and cookies come from the site itself.
Read in its code, 16 October 2026, HubSpot 11.3.75.
Full detail
The HubSpot plugin has an optional reverse proxy, off by default: /_hcms/, /hs/, /hubfs/, /hs-fs/, /cs/c/, /e3t/ and /events/public/v1/ are relayed to HubSpot by WordPress, with HubSpot's headers and Set-Cookie included, so HubSpot requests and cookies then come from the site's own domain.
How we test it
Around each version, with its latest release
Around each Cookie Rocks version, a fresh WordPress installs its latest version from WordPress.org next to Cookie Rocks and runs the same checks. A new version joins the next run on its own.
- HubSpot 11.3.75, tested on 7 November 2026.
- The banner shows, the trackers of the test page wait for consent and load after it, and Cookie Rocks raises no PHP error.
- Settings of the test: Default settings after activation.
- Last run: HubSpot 11.3.75 on 7 November 2026, with WordPress 7.1.3.
Analytics and ad pixels
Other plugins of the same kind.
Questions
What should the visitor’s choice cover?
The HubSpot loader, and with it HubSpot’s tracking. Cookie Rocks holds known trackers until consent.
What happens after the 30-day trial?
The banner, your visitors’ choices and your proofs of consent keep working. Without a key, most settings lock, updates and support stop. Take a key at any time and everything opens again.
For HubSpot users
One banner for HubSpot and the rest.
tracking after a yes
Every feature of the complete plugin for 30 days, no card.
- During the trial: everything, including the full settings and the scans
- After 30 days without a key: the banner, your visitors’ choices and your proofs of consent keep working
- What waits for a key: most settings, updates and support
Get your trial key
Your e-mail and your site. Your key arrives as soon as you confirm your e-mail.