Verify Whether HubSpot Tracking Is Properly InstalledFree Chrome Extension
HubSpot Code Inspector is a free Chrome extension that verifies in seconds whether the HubSpot tracking code is properly installed on any website. Designed for developers, RevOps consultants, and agencies that need to quickly diagnose tracking issues without opening DevTools. Built by Revenue Hub Latam, HubSpot Platinum Partner with over 50 implementations in Chile and Latin America.
Download free from Chrome Web Store →in LATAM
sign-up required
any website
The problem
Why does HubSpot tracking fail more often than you think?
It is not always obvious. Many times the CRM seems to work, but the incoming data is partial or inaccurate. After 50+ implementations in LATAM, these are the scenarios we encounter time and again.
The script exists but loads after the first pageview
The HubSpot code is on the site, but its position in the DOM causes it to execute late. The user has already scrolled, interacted with a form, or even navigated to another page before tracking activates. The first visit is lost and source attribution data remains incomplete.
The portal ID does not match the active portal
In companies with multiple HubSpot portals (sandbox, production, agency portals), it is common for the tracking script to point to the wrong portal. Data arrives at a portal no one checks while the sales team works in another. Without verification, this error can go months undetected.
The consent cookie blocks tracking before the user accepts
Misconfigured cookie banners can block the HubSpot script entirely for visitors who do not click "Accept." On some sites, this means up to 40% of visits are never recorded in the CRM. The marketing team sees less traffic than reality and makes decisions with biased data.
There is a conflict with GTM or another tag manager
When HubSpot tracking loads through Google Tag Manager or another tag manager, the firing conditions may not be correct. The script can load at the wrong time, be duplicated, or conflict with other tracking scripts. HubSpot Code Inspector detects these conflicts in a single view.
How it works
Install · Browse · Verify
No setup. No account. No data leaves your browser.
Install from Chrome Web Store
One click. The extension adds natively to your browser. It works on any site you visit, not just your own.
Open the site you want to check
It can be your client's site, your own, or any domain where HubSpot tracking should be present. The extension analyzes the current page.
Click the extension icon
Within seconds you see the full diagnostic: what is active, what is missing, what is misconfigured. No DevTools or source code inspection needed.
Full diagnostic
What does this extension check?
Everything a developer or RevOps professional needs to confirm that HubSpot is working correctly on a website.
Who is this tool for?
Anyone who needs to verify whether HubSpot is correctly installed on a website, without opening DevTools or requesting access from the development team.
Front-end developers and full-stack engineers who install the HubSpot tracking code on client websites and need to verify everything works before delivering the project.
Revenue Operations professionals who perform HubSpot configuration audits and need to quickly verify tracking status across multiple sites without requesting access to source code.
Agency teams managing multiple portals and clients who need a fast way to confirm tracking is active and pointing to the correct portal before reporting results.
IT leads who need to verify that the HubSpot integration meets the company's technical requirements, including script position, cookie banner interaction, and absence of conflicts.
Is this extension safe? What permissions does it need?
The extension analyzes the visible source code of the pages you visit. Here we explain exactly what it does and does not do with that information.
Page content access: The extension reads the DOM of the current page to detect HubSpot scripts. This is the same source code anyone can see with the browser's "View Source" option.
No data storage: The extension does not save information from the sites you visit. Each analysis is ephemeral — it runs when you click the icon and results disappear when the popup closes.
No external servers: No data is sent to Revenue Hub, Google, HubSpot, or any third party. All processing is local in your browser.
No account required: You do not need a HubSpot account, a Revenue Hub account, or any service account to use the extension.
Read our full privacy policy for more information.
Built by Revenue Hub Latam
Revenue Hub Latam is a Revenue Operations consultancy and HubSpot Platinum Partner based in Santiago, Chile. After more than 50 HubSpot implementations in B2B companies across Chile, Mexico, Colombia, Argentina, and Peru, we built the tools we needed ourselves.
HubSpot Code Inspector was born from hundreds of hours of manual verification on real client projects. Every time we installed or audited HubSpot on a site, we repeated the same steps: open DevTools, search for the script, verify the portal, confirm analytics. We decided to automate it.
Revenue Hub serves B2B companies in technology, SaaS, professional services, and industrial sectors across Latin America.
Frequently asked questions about HubSpot Code Inspector
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.
Other Revenue Hub tools for HubSpot teams
Free Chrome extension that automatically activates the HubSpot tracking panel every time you compose an email in Outlook Web (Microsoft 365). For sales teams losing visibility.
View Outlook auto-tracking extension →Commercial visibility platform with real-time sales, MRR, and attainment dashboards. Connect HubSpot and get the executive view your team needs.
View real-time sales dashboards →Need professional help with your HubSpot implementation?
If your team needs more than an extension — from installing HubSpot correctly to configuring advanced analytics — Revenue Hub Latam can help with a professional implementation.
Want to receive updates about this tool?
No spam. We only notify you if we publish a new version or add features.