Debug HubSpot in Chrome DevTools

What HubSpot traffic looks like

HubSpot spans three traffic families (analytics beacons, form capture, and CTAs), all keyed to the Hub ID in the loader URL.

Endpoint pattern

Loader js.hs-scripts.com/<hubId>.js pulls the analytics module from js.hs-analytics.net (or js-eu1.hs-analytics.net for EU data residency) and, where ads features are enabled, the ads pixel from js.hsadspixel.net; beacons go to track.hubspot.com or track-eu1.hubspot.com; forms through js.hsforms.net / forms.hubspot.com; CTAs from per-account cta-*.hubspot.com hosts

Transport

GIF requests with everything in the query string: __ptq.gif for page views, __ptbe.gif for behavioral events; form submissions are their own family, including the "collected forms" feature that POSTs submissions of the site's own non-HubSpot forms to a forms.hubspot.com collection endpoint, worth finding if you did not know it was on

Key parameters

a Hub ID · vi visitor ID · u the hubspotutk user token HubSpot uses to stitch anonymous visits to a contact record once a form identifies the person · nc new-contact flag · page URL and title

Cookies

hubspotutk plus the __hstc / __hssc / __hssrc session cookies carry the visit history

Debugging HubSpot with Event Watcher

• A dedicated HubSpot parser decodes __ptq.gif/__ptbe.gif beacons into readable groups: Identity (Hub ID, visitor ID, hubspotutk, browser fingerprint), Page Context, Device, and Timing.
• The overview surfaces the Hub ID, page title, and new-contact flag directly.
• The cookies section shows the hubspotutk/__hstc traffic per event, and every hit gets the consent verdict.

HubSpot and consent

The extension checks HubSpot against the marketing consent category, a stricter bar than analytics, because the hubspotutk token exists precisely to join browsing history to an identified contact, which is why most CMPs classify HubSpot tracking as marketing.

HubSpot's own consent integration can hold the tracker in a cookieless "do not track" mode until the banner grants.

A correct setup shows no pre-consent beacons, or beacons without identity cookies; a __ptq.gif carrying hubspotutk before the CMP decision is marked pre-consent and counted.

Common debugging scenarios

• Contact timeline missing page views. Filter to HubSpot and check that __ptq.gif fires per page with a stable hubspotutk. A token that changes between pages means the cookie is being blocked or reset.
• Form fills not creating contacts. Look for the form submission call (HubSpot-hosted or collected-forms) and verify it fires alongside the tracking beacon carrying the same visitor token.
• Collected forms enabled unknowingly. Audit the stream for forms.hubspot.com traffic on pages with only non-HubSpot forms. That reveals the feature capturing submissions.
• EU data residency verification. Confirm beacons target track-eu1.hubspot.com rather than the US host, using the Endpoint pivot in Grouped view.
• Pre-consent identification. Walk the page before accepting the banner and check the consent badges on any HubSpot beacon. Compare with other marketing-automation traffic such as Klaviyo on the same site, or run the broader pixel audit workflow.