How do you install a visitor ID tag on a website builder?
Most builders here have a site-wide header code field, and that is where the tag goes; Carrd uses a hidden embed placed in the head, and Google Sites has no site-wide option at all. Do not use an on-page embed element. The questions that decide the install are whether your plan allows scripts, whether the builder's cookie banner holds the tag until consent, and whether the builder offers a site-wide slot at all. A tag in an on-page embed runs only where you placed it, and inside a sandboxed iframe it records the iframe, not the page.
The table gives the answer for each builder; the sections below give the path and the check. Webflow and HubSpot have their own install checklist.
Plan gate, consent handling and sandboxing, compared
| Builder | Site-wide field | Plan needed for scripts | Built-in banner holds the tag? | Works? |
|---|---|---|---|---|
| Squarespace | Code Injection, Header | Core, Plus, Advanced or some legacy plans | No; wire consent yourself | Yes |
| Wix | Settings > Custom Code | No stated plan; site must be published with a connected domain | Only if you set a non-essential category | Yes |
| Framer | Project Settings > Custom Code | Not stated in Framer's help article | Only via Framer's cookie banner and Consent Mode | Yes |
| Ghost | Settings > Advanced > Code Injection | Not stated in Ghost's help article | Not described in Ghost's help | Yes |
| Carrd | Embed element set to Hidden, Head | Pro Standard or higher | Not described in Carrd's docs | Yes |
| Duda | Site-wide Header HTML | Not confirmed; check your account | Not confirmed; check your account | Yes |
| Bubble | Settings > SEO/metatags > Script/meta tags in header | Not stated in Bubble's manual | Not described in Bubble's manual | Yes |
| BigCommerce | Script Manager | Stencil-theme stores | Yes, by script category | Yes |
| Google Sites | None (only a Google Analytics ID field) | n/a | n/a | No site-wide install |
Why doesn't an embed element work?
Many builders offer two ways to add code: a site-wide header field, and an element you drop onto a page. An element runs only on the pages where you place it, and on some builders it runs in a sandboxed iframe. Wix says HTML element code "is displayed within a sandboxed iFrame" and has no access to the rest of the page. A visitor identification tag inside that frame reports the frame's address, not the page the visitor is reading, and it runs only on the pages where you placed it. Always use the site-wide field.
Will the builder's cookie banner block the tag?
Usually not unless you tell it to, and the defaults differ. Wix loads custom code as "essential" unless you choose another category, which means it runs before consent. BigCommerce lets you give each script a consent category. Squarespace's banner does not manage injected code; its help page tells you to make sure your banner "can interact with the code". Whether this tag should wait for consent is a decision for your privacy owner, not the builder's default. The consent decision tree sets out that decision.
How do you add the tag on Squarespace?
Where it goes: Code Injection, in the Header field. Squarespace inserts Header code into <head> on every page. Individual pages also have their own code injection, but a visitor ID tag belongs in the site-wide field.
Plan: Core, Plus, Advanced or some legacy plans. Code Blocks exist on every plan, but JavaScript inside them needs a paid tier.
What breaks it on Squarespace
- Code Injection runs inside the editor preview too. If it gets in the way while you edit, use the "Disable Scripts in Preview" setting, and test in a private window.
- The Squarespace cookie banner does not hold injected scripts on its own.
- Squarespace support does not help with code-based changes, so keep the vendor's install note with the snippet.
How to check it on Squarespace
Open the live site in a private window, view source, and search for the vendor's host inside <head>. Then click to a second page and confirm it is recorded.
Sources: Squarespace Help: Code injection (read 2026-09-25); Squarespace Help: Code blocks (read 2026-09-25); Squarespace Help: Cookie banner (read 2026-09-25).
How do you add the tag on Wix?
Where it goes: In the site dashboard, go to Settings, then Custom Code in the Development & integrations section, and click + Add Custom Code. Choose Head, load it on all pages, and pick a cookie category.
Plan: Wix states no plan tier, but the site must be published and have a connected domain before you can add custom code.
What breaks it on Wix
- Custom code defaults to the Essential category, so it loads "prior to visitor consent and cannot be disabled". If your privacy owner wants the tag to wait for consent, set it to Analytic or Marketing.
- Do not use the separate header code / meta tag field. It rejects
<script>tags and holds 2,000 characters. - Do not use the Embed HTML element; it runs in a sandboxed iframe.
- Preview runs your code as a site admin, which is not how a real visitor sees it. Test on the published site.
How to check it on Wix
On the published site, open a private window, accept or decline the banner the way a visitor would, and check whether the vendor's request fires in each case.
Sources: Wix Help: Embedding custom code (read 2026-09-25); Wix Help: Categorizing your custom code (read 2026-09-25); Wix Help: Header code guidelines (read 2026-09-25).
How do you add the tag on Framer?
Where it goes: Open Project Settings, choose the Custom Code tab and click Add Script. Place it in the head, apply it to all pages, and choose how often it runs (below).
What breaks it on Framer
- Framer asks whether a script runs "Once", which it suggests for things like adding event listeners, or on every page visit, "each time someone visits the page". A tag that records a visit when it loads needs every page visit. If your vendor's tag tracks page changes by itself, ask the vendor which setting it expects, then test by clicking between pages.
- Framer's cookie banner component only controls tags if you connect it to Google Tag Manager with Consent Mode. A plain custom-code script is not held back on its own.
How to check it on Framer
Publish, open the live site in a private window, click between two pages and check that the vendor records both.
Sources: Framer Help: How to add custom code (read 2026-09-25); Framer Academy: Cookie banner component (read 2026-09-25).
How do you add the tag on Ghost?
Where it goes: Settings > Advanced > Code Injection, in the Site Header field. Ghost outputs it inside <head> on every page. Posts and pages also have their own code injection in the post settings; do not use that for this tag.
What breaks it on Ghost
- The field takes raw HTML, so a missing closing tag breaks what follows it. Paste the snippet exactly as the vendor issued it.
- Ghost's help article describes no consent control for injected code. If the tag must wait for consent, your consent tool has to hold it, and that tool usually goes into the same field, above the tag.
How to check it on Ghost
Open a post and the home page in a private window and search each page's source for the vendor's host.
Source: Ghost Help: Code injection (read 2026-09-25).
How do you add the tag on Carrd?
Where it goes: Add Element > Embed. Set Type to Code and Style to Hidden, then choose Head. Carrd has no separate site-wide settings field; a hidden embed placed in the head covers the whole site.
Plan: Pro Standard or higher. Pro Lite has no Embed element.
What breaks it on Carrd
- An Inline embed puts the code where the element sits on the page, not in the head. Use Hidden.
How to check it on Carrd
Publish, view source on the live site and confirm the tag is inside <head>.
Source: Carrd Docs: Embedding custom code (read 2026-09-25).
How do you add the tag on Duda?
Where it goes: The site-wide Header HTML field in the site's settings. Duda describes it as the place for scripts, meta tags and other code that belongs in <head>. It accepts <script>, <link> and <meta>, but not <img> or <iframe>.
What breaks it on Duda
- Duda's editor runs on jQuery 3.0. If the vendor snippet loads its own jQuery, it can break the editor, so ask the vendor for a version without it.
How to check it on Duda
Publish, then view source on two pages and search for the vendor's host.
Sources: Duda Support: Headers (read 2026-09-25); Duda Developers: Custom editor JavaScript (read 2026-09-25).
How do you add the tag on Bubble?
Where it goes: Settings > SEO/metatags, in the advanced field "Script/meta tags in header". Bubble accepts <script>, <meta> and <link> there. Anything else is pushed into the body.
What breaks it on Bubble
- A script inside an HTML element on a page runs only in run mode, not in the editor, and only on that page. Use the header field.
- If your app changes views by showing and hiding groups on one page, no new page loads, and a tag that records on page load will miss those views. Ask the vendor how to send a page view, and call it from a workflow when the view changes.
How to check it on Bubble
Open the live app, move through the views a buyer would use, and check that each one you care about is recorded.
Sources: Bubble Manual: SEO / metatags (read 2026-09-25); Bubble Manual: Visual elements (HTML element) (read 2026-09-25).
How do you add the tag on BigCommerce?
Where it goes: Script Manager, in the storefront channel's settings. Add a script, set its location to Head and its pages to All pages, and choose a consent category. Script Manager is available on stores that use Stencil themes.
What breaks it on BigCommerce
- Each script has a consent category (Essential, Functional, Analytics or Targeting). If you use BigCommerce's cookie consent, a script in a non-essential category waits for the shopper's choice. Choose the category with your privacy owner, not by guessing.
- Scripts added through the Scripts API show up in Script Manager, but only the API account that created them can change them. Record which app or account owns the tag.
How to check it on BigCommerce
Load the storefront in a private window, decline and then accept cookies, and check when the vendor's request fires each time.
Sources: BigCommerce Dev Center: Scripts (read 2026-09-25); BigCommerce: ScriptConsentCategory (read 2026-09-25).
Can you add a visitor ID tag to Google Sites?
Where it goes: Not properly. Google Sites has no field for head code. Its only tracking setting is Settings > Analytics, which takes a Google Analytics measurement ID and nothing else. Insert > Embed > Embed code adds code to one spot on one page, in the body.
What breaks it on Google Sites
- Embed code runs only on the page where you place it, so you cannot get site-wide page views from it, and Google's help describes no way to reach the page's head. Do not rely on it for visitor identification.
- If the site matters for pipeline, move it to a platform with a site-wide header field.
How to check it on Google Sites
Not applicable. There is no supported install to verify.
Sources: Google Sites Help: Analytics (read 2026-09-25); Google Sites Help: Add Google files, videos, website content, & more (read 2026-09-25).
Where to go next
- Webflow and HubSpot install checklist: the two builders with their own guide
- WordPress: WordPress.com plans and self-hosted WordPress
- Shopify: custom pixels run in a sandbox and need a different approach
- Post-launch QA test script: what to check after the tag fires