01
Contacts lack a reliable source
Conversions arrive as direct traffic or without campaign context.
ToolsHubSpot Code Inspector
Free Chrome extension
Confirm HubSpot is tracking before losing attribution
Check in seconds whether HubSpot tracking is installed correctly, which portal it uses, and whether basic analytics and form signals are available.
$0
free extension
<10 s
to check a page
0
portal permissions required
Revenue Hub Labs
Site inspected
HubSpot Code Inspector
HubSpot codeDetected
Portal ID12345678
Forms trackingEnabled
ConsentReview
Visible diagnosis without opening DevTools or requesting HubSpot access.
Attribution
A page can look fine while HubSpot records nothing
When the code is missing or loads incorrectly, forms, campaigns, and web behavior lose traceability.
02
Landing pages launch without verification
The team assumes tracking works because the page loads.
03
Audits depend on development
Marketing needs technical help to check every page.
What it solves
A fast check before launching or diagnosing
The extension turns a frequent technical task into a clear signal for marketing and RevOps.
Validation in seconds
Check tracking without opening developer tools.
Correct portal
Confirm the page sends data to the expected account.
Better campaign QA
Add a repeatable check before activating paid traffic.
Daily use
Install, visit, and review
No login or HubSpot connection required.
1
Install the extension
Add HubSpot Code Inspector from the Chrome Web Store.
2
Open the page
Visit the site or landing page you want to validate.
3
Read the diagnosis
Review code, portal, and tracking signals in the browser.
Visible signals
The information needed for an initial diagnosis
Designed for fast validation, not as a full analytics or consent audit.
Tracking code
Detect whether the main HubSpot script is present.
Portal ID
Show which account the installation targets.
Load location
Flag atypical or incomplete implementations.
Forms tracking
Check signals needed for form tracking.
Analytics
Indicate whether basic measurement appears active.
Consent
Flag signals requiring review before launch.
Who uses it
For teams that need page checks without DevTools
Useful for QA, audits, migrations, and campaign launches.
The extension analyzes the page visible in your browser. It does not request portal access or modify the site.
Marketing
Validate landing pages before launching campaigns.
Revenue Operations
Check attribution during portal audits.
Agencies
Review client sites without source-code access.
Development
Get a first signal before deeper debugging.
FAQ
HubSpot Code Inspector frequently asked questions
How do I know if HubSpot tracking is working on my website?
Install HubSpot Code Inspector in Chrome, navigate to your website, and click on the extension icon. Within seconds you will see a full diagnostic: whether the HubSpot script is present, whether it is active, which portal ID is connected, whether analytics is recording visits, and whether forms are sending data to the CRM. No need to open DevTools or manually inspect source code.
What does it mean if the HubSpot script is in <body> instead of <head>?
When the HubSpot tracking script loads in the <body> instead of the <head>, there is a risk it will not execute before the user interacts with the page. This can cause the first visit (pageview) to go unrecorded, or a form submission to occur before tracking is active. The ideal placement is in the <head> of the document, before any visible content.
How can I verify which HubSpot portal is connected to a website?
HubSpot Code Inspector shows the Portal ID connected to the website you are visiting. This is useful for confirming that tracking is sending data to the correct portal, especially for agencies managing multiple HubSpot accounts or companies with both sandbox and production portals.
Why is HubSpot not recording visits from my website?
The most common causes are: the tracking script is not installed, it is installed but blocked by a cookie banner before the user accepts, it loads after the first pageview because it is at the end of the DOM, the portal ID does not match your active account, or there is a conflict with another tag manager such as Google Tag Manager. HubSpot Code Inspector diagnoses all of these situations in a single view.
Why are my website forms not showing up in HubSpot?
If Forms tracking shows as disabled in HubSpot Code Inspector, your website form submissions are not being connected to HubSpot. This can happen if you use native HTML forms instead of HubSpot embed forms, if the Forms module is not included in your tracking script, or if there is a portal configuration error.
Can the cookie banner block HubSpot tracking?
Yes. If your cookie banner is configured to block third-party scripts before user consent, HubSpot tracking will not activate until the visitor accepts cookies. HubSpot Code Inspector detects the cookie banner state and alerts you if consent settings may be affecting tracking.
Do I need a HubSpot account to use HubSpot Code Inspector?
No. The extension does not require any account or login. It works independently by analyzing the source code of any website you visit. It is useful for verifying your own site as well as auditing client, competitor, or prospect websites.
Does the extension work in Edge or other Chromium browsers?
Yes. HubSpot Code Inspector works in any Chromium-based browser, including Google Chrome, Microsoft Edge, Brave, and Opera. It installs from the Chrome Web Store and functions the same way across all of these browsers.
Does the extension access my browsing data?
The extension only analyzes the DOM of the page you are currently visiting to detect HubSpot scripts. It does not access your browsing history, does not store data from the sites you visit, and does not send information to external servers. All processing happens locally in your browser.
What happens if I have two portal IDs on the same site?
HubSpot Code Inspector detects all HubSpot scripts present on the page. If there are multiple portal IDs, the extension will display them. Having two portal IDs on the same site generally indicates a configuration error — for example, a production script and a sandbox script loading simultaneously — and can cause duplicate or inconsistent data in your CRM.
Do not launch a page without confirming attribution
Add the extension to Chrome and make tracking verification part of QA.
Free · No login · Available in the Chrome Web Store