Add Website Visitor Identification to Webflow

Q: Does adding Leadpipe slow down my Webflow site?

No meaningfully. The snippet loads async, so it doesn't block rendering or delay your page. It's a few hundred bytes of script plus a lightweight background request — invisible in real-world load times and Lighthouse scores.

Q: Does it capture form submissions too?

Leadpipe identifies visitors who don't fill out forms — that's the point. Your existing Webflow form submissions still flow wherever you send them; Leadpipe adds the ~97% who never submit anything. The two are complementary.

Webflow is where a lot of B2B marketing sites actually live — fast, designer-friendly, and easy to ship. The problem is what happens after someone lands on it. Roughly 97% of B2B website traffic leaves without filling out a form, which means most of the demand your beautiful Webflow site generates walks out the door anonymous.

Leadpipe fixes that by identifying anonymous visitors at the person level — a named contact with verified work email, company, title, and the pages they viewed — using deterministic matching against its own identity graph. And because Leadpipe is just a lightweight JavaScript snippet, adding it to Webflow takes about five minutes with no developer required.

This guide walks through every way to install Leadpipe on Webflow, how to verify it’s firing, and how to route the visitors it identifies to your team.

What you need before you start

Three things:

A Leadpipe account. You can start free with 500 identified leads — no credit card — and grab your install snippet from the dashboard.
A Webflow Site plan. Custom code in Webflow requires a paid Site plan (Basic or higher). The free Webflow subdomain won’t let you add site-wide head code.
Publish rights on the Webflow project. Custom code changes only go live after you publish the site.

Your Leadpipe snippet is a single <script> tag that looks roughly like this (your data-id will be unique):

<script async src="https://cdn.leadpipe.com/px.js" data-id="YOUR_SITE_ID"></script>

That one tag is the whole install. Everything below is just where you paste it.

Method 1: Site-wide custom code (recommended)

This is the cleanest option — the tag loads on every page automatically, including new pages you build later.

In the Webflow Designer, open Project Settings (or Site Settings in newer workspaces).
Go to the Custom Code tab.
Paste your Leadpipe snippet into the Head Code field (the <head> section).
Click Save Changes.
Publish your site (top-right Publish button → publish to your live domain).

That’s it. Because the script is async, it loads without blocking your page render, so it won’t touch your Core Web Vitals or Lighthouse scores.

In one sentence: Paste the Leadpipe tag once into Webflow’s site-wide Head Code, publish, and every page on your site starts identifying visitors.

Note on the character limit. Webflow caps site-wide custom code at 10,000 characters. Leadpipe’s snippet is a few hundred characters, so you’ll never hit it — but if your head is already crowded with other tags, use Google Tag Manager instead (Method 3).

Method 2: Per-page custom code

Sometimes you only want identification on specific pages — say, high-intent pages like pricing, demo, and product tours — rather than your blog or careers pages. Webflow lets you scope custom code to a single page.

In the Designer, open the page you want to track.
Open Page Settings (the gear icon next to the page name).
Scroll to Custom Code → Inside <head> tag.
Paste the Leadpipe snippet and save.
Publish.

Repeat for each page you want covered. Per-page code overrides nothing — it’s additive to your site-wide code — so don’t paste the same tag both site-wide and per-page or it will load twice.

In practice, most teams want identification everywhere. A visitor reading three blog posts before they ever touch your pricing page is exactly the kind of research pattern you want to catch. See what to do when someone visits your pricing page for why the low-intent pages still matter.

Method 3: Install through Google Tag Manager

If you already run GTM on your Webflow site, deploy Leadpipe as a tag there instead of hard-coding it. This keeps all your marketing tags in one place and lets non-technical teammates manage them.

In GTM, create a new Custom HTML tag.
Paste the Leadpipe snippet.
Set the trigger to All Pages (or a subset if you’re scoping it).
Submit and publish the GTM container.

Because your GTM container snippet is already in Webflow’s head, nothing new needs to go into Webflow itself. For the full walkthrough — including consent-mode considerations — see our Google Tag Manager setup guide. If you run consent banners in the EEA, also read Google Consent Mode and visitor identification.

How to verify it’s actually firing

Don’t assume it worked because the page saved. Confirm it:

Network check: Open your published site, open your browser’s DevTools → Network tab, reload, and filter for leadpipe or px.js. You should see the script load with a 200 status.
Dashboard check: Visit your own site from a normal browser (not incognito, not a VPN), then open the Leadpipe dashboard. Within a few minutes you should see session activity. In the US, some of your own team’s visits will resolve to identified people.
Publish reminder: If you see nothing, the single most common cause is that the site was saved but never published. Webflow staging (.webflow.io) and your live domain are separate — make sure you’re testing the domain where the code is published.

In one sentence: If px.js returns a 200 in the Network tab and sessions appear in your Leadpipe dashboard, the install is done.

A quick reality check on coverage: Leadpipe identifies roughly 30–40% of US B2B visitors at the person level. It’s deterministic, so it returns a verified match or nothing — it never guesses. Outside the US, coverage is lower and often resolves at the company level, which is normal and honest. If most of your Webflow traffic is US B2B, you’ll see the strongest results.

Try Leadpipe free with 500 leads →

Route the visitors you identify

Installing the pixel is step one. The value comes from what you do with each identified visitor. A few common routes for Webflow-based teams:

Slack alerts. Get a real-time ping when someone from a target account visits. Setup in Leadpipe Slack visitor alerts.
CRM sync. Push named visitors straight into HubSpot or Salesforce as contacts with the pages they viewed. See the Salesforce integration.
Automation. Fan visitors out to sheets, email tools, or enrichment steps with Zapier recipes.

The through-line: an identified visitor is only useful if it reaches a human or a workflow while intent is still warm.

Webflow-specific gotchas

A few things that trip Webflow users up specifically:

Issue	Cause	Fix
No sessions appearing	Site saved but not published	Publish to your live domain
Code field greyed out	Free/Starter Webflow plan	Upgrade to a paid Site plan
Tag loads twice	Same snippet site-wide and per-page	Keep it in one location only
Firing on staging only	Testing the `.webflow.io` URL	Test your live custom domain
Blocked by consent banner	EEA consent gating	Configure consent mode correctly

None of these are Leadpipe quirks — they’re just how Webflow’s custom code and publish flow behave.

Why deterministic matching matters on a marketing site

Your Webflow site is a top-of-funnel asset. Whatever gets identified there flows downstream into outreach, CRM records, and increasingly into AI-driven follow-up. That’s exactly the wrong place to introduce guesses.

Probabilistic tools return a “best guess” even when their confidence is a coin flip, which means a chunk of the “identified” contacts you’d email never actually visited. Deterministic matching returns a verified person or nothing at all — so what leaves your Webflow site is data you can act on. We break down the tradeoff in full in deterministic vs probabilistic matching.

If you want the broader primer on how identification works before you commit, read how to easily identify anonymous website visitors and the product overview.

FAQ

Does adding Leadpipe slow down my Webflow site?

No meaningfully. The snippet loads async, so it doesn’t block rendering or delay your page. It’s a few hundred bytes of script plus a lightweight background request — invisible in real-world load times and Lighthouse scores.

Do I need a developer to install Leadpipe on Webflow?

No. Pasting one script tag into Webflow’s Custom Code field and publishing is something any marketer with publish access can do in a few minutes. If you’d rather keep tags centralized, deploy it through Google Tag Manager instead.

Can I identify visitors on a free Webflow plan?

No. Webflow requires a paid Site plan to add custom code, and Leadpipe needs that snippet to run. Free .webflow.io sites can’t add site-wide head code. Upgrade to a Basic (or higher) Site plan first.

Will Leadpipe work with Webflow Ecommerce?

Yes. The snippet fires on all pages regardless of whether they’re CMS, static, or Ecommerce templates. If you sell B2B or wholesale through Webflow Ecommerce, identification is especially valuable on product and cart pages where anonymous browsers abandon.

Does it capture form submissions too?

Leadpipe identifies visitors who don’t fill out forms — that’s the point. Your existing Webflow form submissions still flow wherever you send them; Leadpipe adds the ~97% who never submit anything. The two are complementary.

Start identifying your Webflow visitors

Your Webflow site is already doing the hard part — attracting the right people. Leadpipe just makes sure you know who they were. Paste one tag, publish, and start turning anonymous sessions into named, verified B2B contacts you can actually follow up with.

Try Leadpipe free — 500 identified leads, no credit card required.