60-Second Summary
Webflow is great for building fast, polished B2B sites, but it won’t tell you which companies visit out of the box. This guide shows how to add company-level visitor identification on Webflow, what data you get, and how to keep implementations compliant.
Key takeaways: Add the Leadfeeder Tracker to Webflow (via Google Tag Manager or Webflow custom code) to identify visiting companies; you then get company name, firmographics, pages viewed, source/medium, and visit time.
Standout strategies & tactics: Use GTM (recommended) to inject the tracker for easiest setup, configure Leadfeeder traffic filters, and connect integrations (CRM, Slack) to act on intent while it’s fresh.
Real-world lessons & frameworks: Visitor identification matches IPs to companies via reverse-IP lookup and business databases, keeping insights at the company level (not individual), which is more actionable for B2B sales and marketing.
Compliance & practical note: Company-level data is treated differently from personal data, but GDPR and local rules still apply—review implementation, choose transparent vendors, and honour objections; start experimenting with Leadfeeder’s free plan.
*This summary was created with AI assistance, using our original content.
Webflow is great for building a fast, polished B2B site, but out of the box it will not tell you which companies are landing on it. This guide shows you how to set that up on Webflow, what data you get, and how to stay compliant. It is the same company-level approach we cover in our website visitor tracking guide, applied to Webflow; for the wider how-to, see how to identify anonymous website visitors.
What Webflow visitor identification is (and what it is not)
It is not a visitor counter. Analytics tools tell you how many people visited; visitor identification tells you which companies visited. You see the business behind each visit, not an individual person. For B2B teams on Webflow, that is the difference between a traffic chart and a list of accounts you can actually act on.
How to set up visitor identification on your Webflow site
To identify the companies visiting your Webflow site, you add the Leadfeeder Tracker script to your site. Webflow has no plugin marketplace, so you add it as custom code. There are two ways:
Google Tag Manager (recommended): add the tracker script to your GTM container. This is the easiest route and does not need a paid Webflow plan.
Webflow custom code: in your Webflow project, go to Project Settings > Custom Code and paste the tracker script into the Head Code field (it injects before the closing </head> tag site-wide). This requires a paid Webflow Site plan (Basic or above), and the code only goes live once you publish the site.
Then set your traffic-filtering rules in your Leadfeeder settings; data typically starts appearing within about an hour. Full setup steps are in our guide to installing the tracker on a website builder.
What visitor data you get
Once the tracker is running, each identified company can include the company name and firmographics (industry, size, location), the pages they viewed, the traffic source and medium, and the time of the visit. You can push companies into your CRM or Slack through Leadfeeder’s integrations and follow up while intent is fresh. It stays company-level throughout, so you are acting on the business, not tracking a named individual. This helps sales and marketing teams spot engaged accounts before they convert.
Tracking visitor IP addresses on Webflow
Webflow does not hand you visitor IP addresses directly, and on their own they would just be numbers anyway. Visitor identification does the useful part for you: it matches a visitor’s IP to the company it belongs to using reverse-IP lookup and a business database, turning an anonymous visit into a named company. We break this down in how to find the company behind an IP address.
Is Webflow visitor identification GDPR-compliant?
Company-level identification points to the business behind a visit, not a named person, so it is treated differently from tracking individual personal data. Even so, your GDPR obligations still depend on implementation, jurisdiction and legal review, so treat this as guidance rather than a guarantee. We cover the detail in website visitor tracking in a post-GDPR world. Use a tool that is transparent about its data sources and honours objections.
Frequently Asked Questions for Webflow Visitor Identification
How do I see which companies visit my Webflow site?
To see which companies visit your Webflow site, add a website visitor identification tracker via Google Tag Manager or Webflow’s custom code. It reveals the companies behind your visits, even the ones who never fill in a form, along with the pages they viewed and where they came from.
Can I track visitors on Webflow without a plugin?
Yes. Webflow has no plugin marketplace, so you add a visitor identification tracker through Google Tag Manager or by pasting the script into Webflow’s custom code. Both work, and GTM does not require a paid Webflow plan.
Does visitor identification slow down my Webflow site?
The tracker is a lightweight script. For the smallest performance impact, load it through Google Tag Manager or add the async or defer attribute to the script.
Is Webflow visitor identification GDPR-compliant?
Company-level identification points to the business behind a visit, not a named person, so it is treated differently under GDPR. Your exact obligations still depend on implementation and jurisdiction, so involve legal for your setup.
Ready to see which companies are visiting your Webflow site? Start with Leadfeeder’s free plan.
Related articles
