Install a visitor ID tag: pick your platform
The tag usually goes in one place that every page shares, and pasting it takes minutes. What differs by platform is how the install fails without any error: a plan that does not allow scripts, a speed plugin that holds them back, a cookie banner default, a sandbox, or a single-page app that loads the tag once and never sees the pricing page. Find your platform below; each page gives the exact location, the failure modes that apply there, and a check you can run.
Which page covers your site?
| Your site runs on | Page | What usually breaks there |
|---|---|---|
| A Google Tag Manager container already on the site | Install through GTM | Custom HTML minification, consent settings, the History Change trigger for single-page apps |
| WordPress.com or self-hosted WordPress | WordPress | Plan gate on WordPress.com; speed plugins that delay scripts until the visitor interacts |
| Webflow or HubSpot CMS | Webflow and HubSpot checklist | Paid Site plan or Workspace on Webflow; site-wide vs per-page header HTML on HubSpot |
| Squarespace, Wix, Framer, Ghost, Carrd, Duda, Bubble, BigCommerce or Google Sites | Website builders | Plan gates, cookie-banner defaults, embeds that only run where you place them |
| Shopify | Shopify | Custom pixels run in a sandbox and accept JavaScript only |
| Next.js, React, Vue, Angular, SvelteKit, Nuxt, React Router, Gatsby or Astro | JavaScript apps | Client-side navigation: the tag loads once and misses later pages |
| Rails, Django, Laravel, ASP.NET Core, Drupal, Magento, Eleventy or plain HTML | Server-rendered and static sites | CSP settings, Turbo and Blazor page swaps, Magento checkout blocking |
What should you decide before you paste the tag?
- One install path. Put the tag either in the site’s code or in your tag manager, not both. Two copies count every visit twice, and the duplicate is hard to see later.
- Whether it waits for consent. Some builders run custom code before the cookie banner is answered unless you set a category. That choice belongs to your privacy owner; the consent decision tree sets it out.
- Who owns it. Write down where the tag lives and who can remove it. The implementation checklist covers the rest of the rollout plan.
What comes after the install?
A tag that fires is not yet data you can use. Run the post-launch QA test script before any alert reaches sales, filter out employee, customer and bad-fit traffic, and measure what share of visits the vendor actually matches with the match-rate calculator. No vendor identifies every visitor. If the tag loads but records nothing, test the site’s policy with the CSP checker for tracking tags.
These pages are written from each platform’s own documentation, with the date we read it next to every source.