Where exactly the code goes in HubSpot
To cover every page type at once, add the snippet under Settings → Content → Pages → "Site header HTML"; with several connected domains, pick the domain at the top, because HubSpot keeps header HTML per domain. If only one landing page needs sign-off, use that page's settings → Advanced options → "Head HTML" instead. For approvals the second route is often better: the snippet disappears with the page after launch instead of running permanently across all domains.
Preview links, test mode and what stakeholders actually see
HubSpot preview URLs (`preview.hs-sites.com` or the "share preview" link) render the page without a published version, and header HTML from the domain settings is not always served there. That is why the page-level head HTML is the more reliable route for pre-publish sign-off. Alternatively publish to a non-indexed staging domain and share that link.
Approval loops with many stakeholders
Landing pages rarely have a single approver: marketing, sales, legal and management comment in parallel, usually in a spreadsheet or by email. With notes on the element and a status per item you see what is open, in progress and done – instead of merging three versions of a feedback sheet and still missing one change.
Forms, CTAs and smart content
HubSpot forms render inside an iframe, and CTAs or smart content vary by list membership or device. So place notes on the surrounding module – the form block, the heading above it, the CTA container – and describe the change you want to a field label or copy. With smart content, record in the comment which audience the variant was for, otherwise the context cannot be reconstructed later.
Domains, subdomains and the cookie banner
HubSpot pages usually live on a subdomain such as info.example.com or go.example.com, and each one has to be registered in your nootiz project or the snippet will not load. If the HubSpot cookie banner with script blocking is active, it can hold back third-party scripts until consent; for review environments either disable the banner or accept once in your test browser.
A/B tests and multiple variants
During an A/B test HubSpot serves one variant per visitor. Notes stay tied to the variant that was opened, but the mapping is only traceable when the comment names the variant (A or B). For clean sign-off, approve variants individually before the test goes live.
From feedback into the marketing backlog
Every note carries the URL, the element, a screenshot crop and the comment, and can be handed to Trello, Asana, Jira or GitHub as a task. Delivery stays where your team plans – nootiz is the collection point for feedback, not a second project tool.
