How to Install Pixels

TL;DR

Pick your provider (Vector, RB2B, Lead Forensics, Clearbit Reveal, HubSpot, etc.), copy their pixel/snippet, and paste it once via Google Tag Manager or your site's global <head>. Publish, verify it is firing, and you are done -usually 5-15 minutes.

The simple, safe way (recommended): Google Tag Manager

Sign in to GTM (tagmanager.google.com) and open your container for the production site.
Add a new Tag -> Custom HTML (or the provider's native template if available).
Paste the pixel/snippet from your identity/analytics provider.
Triggering: set to All Pages (or specific pages if your provider recommends it).
Publish (Submit -> Publish) so it goes live.
Verify with your provider's real-time debugger, GTM Preview mode, or your browser console/network tab.

Why GTM? You avoid code deploys, keep all tracking in one place, and can pause/adjust without bothering engineering.

The direct route: paste into your site's <head>

If you are not using GTM or prefer a direct install:

Next.js / React / SPA

-Put the snippet in your site's global head (e.g., app/(site)/layout.tsx or the framework's HTML template). -For single-page apps, confirm the provider supports SPA route changes; if not, enable their SPA/History settings.

WordPress

-Use Appearance -> Theme File Editor -> header.php (before </head>) or a safe plugin like Header & Footer Scripts. -If using a builder (Elementor/Divi), use their Global Head/Site Settings area.

Webflow / Squarespace / Wix

-Go to Project Settings -> Custom Code and paste the snippet into the Head section.

Shopify

-Online Store -> Themes -> Edit Code -> theme.liquid and paste before </head>.

Do not forget publish/deploy if your CMS/framework requires it.

Provider checklist (works for most tools)

-Copy the exact snippet from your provider's dashboard (Vector, RB2B, Lead Forensics, Clearbit Reveal, HubSpot, etc.). -Paste once (avoid duplicates) in GTM or global head. -All pages trigger unless provider says otherwise. -Consent/region settings: enable Geo/CMP integration if you use cookie consent.

Publish and verify

-Provider's live debugger or "last seen" timestamp -GTM Preview -Browser Network tab -> look for the provider's domain request returning 200.

Quick verification steps

Open your site in an incognito window.
Browse 2-3 pages and wait 60-120 seconds.
Check the provider's dashboard logs (Visitor, Page View, or "Pixel active").

If nothing appears:

-Confirm publish actually happened (GTM or CMS). -Make sure ad blockers are not hiding the request. -Ensure you installed in production, not a staging container. -For SPAs, enable history change/route support in the provider.

Privacy & respect (quick note)

Add or update your Privacy Policy to mention analytics/identity pixels and how data is used. Honor regional consent frameworks (GDPR/CCPA) and your company's data policies. Good tracking is transparent and useful to the visitor.

Success criteria

-Pixel shows active within minutes. -You see company/person-level activity for page views. -No duplicate tags, no console errors. -Intent events (e.g., Pricing viewed, Resources browsed >90s) are visible and can trigger alerts/workflows.

What is next

With the pixel live, you can:

-Alert your team when ICP traffic + high-intent pages are viewed. -Auto-generate a microsite for those visitors (covered later). -Retarget those same accounts back to their microsite.

Installing the pixel is the only technical step. From here, it is all about using the data to craft targeted microsites and book more meetings.