Skip to main content

Frequently asked questions about the Leadfeeder tracking script

Answers to the most common questions about the Leadfeeder tracking script.

Written by Ruthie Keith

Here are answers to the questions we hear most often about the Leadfeeder tracking script.
​

What is the Leadfeeder tracking script?

The Leadfeeder tracking script is a small piece of JavaScript you add to your website so Leadfeeder can identify the companies visiting it. It powers both Web Visitors and Web Insights. Other tools call this kind of code a tag (Google Tag Manager) or a pixel (Facebook).

The tracking script matches each visit's IP address against company databases to find out which company the visit came from. It then adds business details such as company name and industry.
​

Will the tracking script slow down my site?

No. The tracking script loads asynchronously, so your site doesn't wait for it to load.
​

AWS CloudFront delivers the script from over 200 locations worldwide, so it loads from a server close to each visitor.
​

How do browsers blocking cookies affect the tracking script?

They don't affect it. Most browser changes block third-party cookies, and Leadfeeder doesn't use them.
​

Leadfeeder uses first-party cookies, but identification relies mainly on other technology. Leadfeeder can still identify companies even if a browser blocks all cookies.
​

Does the tracking script collect personal data?

By default, Web Visitors shows you companies, not named individuals. Leadfeeder uses the visitor's IP address to match the visit to a company and add business details.
​

How does the tracking script handle consent?

The Leadfeeder tracking script works with or without cookies. If your website uses a Consent Management Platform (CMP), you can configure the script to set its cookie only after a visitor grants consent. See Configuring the Leadfeeder tracking script with your consent management platform (CMP) for setup steps. If no cookie is set (for example before consent is granted, or if you choose not to use cookies at all), the tracking script can still identify the visiting company, though it won't recognize a repeat visit from the same browser as the same visitor. How you configure consent and cookie use on your website, and what your applicable laws require, is a decision for your organization to make with your own legal counsel.
​

Why is the tracking script blocked on my site?

Your site's Content Security Policy is probably blocking it. To fix it, see Why is the Leadfeeder tracking script blocked on my site?
​

How do I know the tracking script is working?

Give it at least an hour after you install it, or 24 hours on the free Lite plan. Then check the status in Settings > Company > Website Tracker > Tracker status. To check the script is on your site, see How to check the Leadfeeder tracking script is working.
​

The tracking script turns off temporarily if your website gets no visits from an identifiable company for 48 hours. It starts again with the next identifiable visit.
​

If Leadfeeder identifies fewer companies than usual, you may have had fewer company visits and more ISP visits.
​

Also check your hostname rules in your Leadfeeder settings, so the script records visits from the right domains.
​

Why do I need the tracking script if I have Google Analytics connected?

Google Analytics stopped providing the information Leadfeeder needs to identify visits on February 4, 2020. Leadfeeder can only identify visits after you install the tracking script.
​

Is the tracking script GDPR compliant?

Web Visitors is built to support a privacy-conscious implementation: by default it surfaces company-level intent data rather than named individuals, and it works whether or not cookies are used. Whether your specific implementation is GDPR-compliant depends on your own data processing activities and configuration. That assessment is yours to make, ideally with your legal or privacy team.
​

You can also turn IP-address anonymisation on in your tracking script settings if desired. IP address anonymisation does not impact company recognition (unlike Google Analytics) nor does it slow down the recognition. However, we won't be able to later debug based on IP addresses anymore, since we won't have them.
​

IP addresses are anonymised by dropping the last octet. As an example, IP address 212.50.143.138 would become 212.50.143.0. This anonymisation makes it impossible to connect outside IP address information later, preventing singling out an individual visitor.
​

For this processing, you (as controller) and Leadfeeder (as processor) are bound by our Data Processing Agreement (DPA), which is part of our GTC.
​

What information do I see in Web Visitors once I install the tracking script?

For each visit from an identified company, you see:

  • Time and date of the visit

  • Source and medium

  • Number of pages visited

  • Pages visited (title, URL and time on each page)

  • Visitor ID number

  • Total length of the visit

  • Form submissions (when form tracking is switched on)

  • File downloads

  • Video plays: YouTube and Vimeo videos played on your website, including the video title (when video tracking is switched on)

  • Outbound clicks: the destination URL of links that lead away from your website, and for email or phone links, the email address or phone number shown on your website (when outbound link tracking is switched on)

New visits usually appear within 5 to 10 minutes.
​

Should I also connect Google Analytics with Leadfeeder?

Yes, we recommend it. Google Analytics doesn't identify companies, but it can add information such as keyword and query data.
​

Does the tracking script work on single-page applications?

Yes. The tracking script doesn't rely on page loads. It tracks changes in the page URL, so when your single-page application changes the URL without a page load, Leadfeeder counts the new URL as a new pageview. Learn more in SPA tracking.

This has been the default since May 2022. If you signed up before then and need this feature, contact our support team.

Can I install the tracking script in a desktop app instead of a website?

It depends on how the app loads its pages. The tracking script needs pages loaded over http or https. If your app is a website packaged as an app and loads its pages over http or https, it may work.
​

How do I install the tracking script?

Copy the script from Settings > Company > Website Tracker > Tracker script, then add it to your website using the guide that matches your setup:

For all installation options, see Installing the Leadfeeder tracking script.
​

Can I install the tracking script on any website?

Yes, if you can add custom JavaScript to your site directly, through Google Tag Manager, or with a plugin. If your website builder or CMS doesn't allow custom scripts or Google Tag Manager, ask its support team about your options.
​

Does loading the tracking script twice give me more data?

No. Loading the script more than once inflates your numbers for identified companies and visits. To check how many times it loads, run this in your browser's developer console:
​

Array.prototype.slice.call(document.scripts).map(s => s.src)

If the tracking script appears twice, as below, change your code so it loads only once:
​


​

--

Still not working? Contact our support team via chat or at support@leadfeeder.com. Please include your account ID, the URL where the issue happens, and a screenshot, so we can help you faster.

Did this answer your question?