I can’t seem to set up the HS tracking code for some reason.
I’ve inserted the code just fine (using Webflow here), but I am getting Failed status in Hubspot.
Reason:
HubSpot tracking snippet found (or indicated by domain), but it is not loading successfully
The seem to fire just fine with a Status code of 304 - https://prnt.sc/hXoN-_C0DnhV
(this is on our homepage but it fires on every page - https://www.cloudcapital.co/)
In Termly I’ve set all these domains of cookies to be put into Essential:
I found a few Knowledge Base articles that should help you troubleshoot this further:
I’m also tagging a few community experts for more ideas. Hey there @CarolinaDeMares@trevordjones@GIlievski, I hope you’re having a great week! Any additional insights here?
Hey @sbi85 ! I would say the easiest way to get your HS tracking code installed propertly into your CMS would be to use a direct integration. I see in the HubSpot’s market place there is in fact an integration with Webflow that covers tracking code installation:
So you just have to simply remove everything you have already added, and try doing the integration with the HubSpot marketplace
If you really want to do it your way and need further assistance in reviewing your code, in ZUID we can for sure assist.
Hope this helps!
Thanks @CarolinaDeMares . I may give it a go. However the 2.8 rating on the marketplace app and the almost total unusability that people report in these reviews are a bit concerning.
I’ve installed the Webflow app, connected the two systems and I see it in Webflow working properly.
BUT now the Hubspot tracking code is not even get found on the page, when I try to validate.
- HubSpot tracking code not found on page" Screenshot by Lightshot
Previously at least it was there. So the app integration seem worthless currently.
Which does mean that I am totally unsure what the next step would be here.
The issue is almost certainly in how Termly categorizes and fires the HubSpot scripts. Even though you added those domains to Essential in Termly, the HubSpot tracking code itself (hs-scripts.com) loads additional scripts dynamically after the initial snippet runs, and Termly might be blocking those secondary scripts because they set cookies that Termly classifies as Analytics or Marketing rather than Essential. The 304 status you’re seeing just means the file is cached, it doesnt confirm the script is actually executing fully.
What I’d try: in Termly, go to your cookie scan results and look for any HubSpot related cookies (like __hstc, __hssc, hubspotutk) that might still be categorized under Analytics or Marketing. Those need to be reclassified to Essential too, otherwise Termly blocks the scripts that set them even if you allowlist the domains. Alternatively you could configure Termly to let HubSpot load through its tag manager integration so Termly controls when the script fires based on consent rather than blocking it outright.
For the Webflow app making things worse, that tracks with what others have said about it. I’d go back to the manual snippet approach since you confirmed it was at least detected before. Remove the Webflow app connection, paste the HubSpot tracking code back into Webflow’s custom code section in the <head>, and then focus on getting the Termly categorization right. One thing at a time basically (Install the HubSpot tracking code ) Note This response was written based on my own experience and lightly reformatted with AI for clarity.
