What are some of the most asked questions about Leadfeeder Tracker?
We answer a lot of questions every day but these are what we hear the most often!
Q: What is Leadfeeder Tracker?
This type of script can also be referred to as a tag, tracking pixel, or script. We call it a script, Google Tag Manager calls it a tag and Facebook calls it pixel. All meaning a piece of code that's inserted on the website.
Q: Will Leadfeeder Tracker slow down my site?
Leadfeeder Tracker shouldn't have any impact on your site speed. Tracker is an asynchronous script, meaning it doesn't have to load before your site loads. It works in the background making page loading your priority.
The tracker script is delivered from the AWS Cloudfront content delivery network, which ensures that no matter where the visits come from the script is always loaded close to them with minimal latency. Cloudfront has over 200 edge locations all over the world, including, most likely one near your visitor.
Q: With many web browsers leaning to protect privacy by blocking cookies and tracking how will that impact Leadfeeder and it's a tracker?
The majority of these theoretical changes are in regards to 3rd party cookies. Browsers blocking 3rd party cookies in the future has no effect on how Leadfeeder operates since we don't use them.
Though Leadfeeder uses 1st party cookies, we rely mainly on a completely different type of technology which means to us 'no cookies, no problem'.
Even if all cookies were blocked we would still be able to ID companies visiting your site.
Q: Why is Leadfeeder Tracker ‘blocked’ on my site?
The Tracker may be blocked by a 'Content Security Policy' on your site. Learn more about how to get this fixed here.
Q: How do I know Leadfeeder Tracker is on my site and working?
If you have just installed Tracker on your site give it at least an hour to begin tracking. If you have a LITE account you will want to wait for 24 hours for the update. At that point, you can check your status here. You can also see some tips to check your installation here if you want to see if the script is on the site properly.
If you have lower amount of Leadfeeder leads, it might be that there has been a lower amount of companies visiting and instead more ISP visits.
Q: Why do I need Tracker, I have Google Analytics connected?
As of Feb 4, 2020, at 8 am San Francisco time (Pacific Time) Google Analytics stopped providing information required for visit identification. Any visits seen after that time can not be identified until Tracker is/was installed and updated.
Q: Is Leadfeeder Tracker GDPR compliant? IP - anonymization
Yes, it is. You can also turn IP-address anonymization on in your Leadfeeder Tracker settings if desired. IP address anonymization 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 184.108.40.206 would become 220.127.116.11. This anonymisation makes it impossible to connect outside IP address information later, preventing singling out an individual visitor.
Q: What information do I see in Leadfeeder once I install Leadfeeder Tracker
For each visit from an identified company you will see:
Time and Date of visit
Source and Medium
Number of pages visited
Pages visited (Title, URL, and Length of the page visits)
Visitor ID number
The total length of visit
Q: Should I also connect Google Analytics with Leadfeeder?
We recommend that you do. Although it isn’t identifying leads it may enhance some information as time goes on such as keyword data and query information.
Q: Does Tracker work on single-page applications/sites?
Yes, the tracker works on SPAs. The Leadfeeder tracker does not rely on a page-load but it tracks changes in the page URL to identify pageviews. If your SPA changes the page URL without a page-load, the new page URL will be identified as a new pageview by default.
Learn more about SPA tracking here.
Note: This is the default tracker behaviour after May 2022. If you signed up before and need this feature, please reach out to support and we’ll be happy to help!
Q: Is there Any limitations on installing the tracker on a desktop app instead of a website?
The “webpages” in such an app might be loaded by a different browser view than https or http protocol, which we need to do proper tracking. It maybe could work if it is just a website “packed” into an app with “webpages” loaded only by http or https protocol.
Q: How do I install Leadfeeder Tracker?
We have detailed instructions on how to install tracker here!
Q: Can I install Tracker on any website?
Q: Loading Tracker twice on my website = more data?
You should never load Track on your website more than once as it will skew the numbers we will give you regarding your leads and visits (you will see more). How can you check if you are loading the tracker only once? Add this into developer tools/console:
Array.prototype.slice.call(document.scripts).map(s => s.src)
Watch if it shows the tracker twice:
If you see it loaded twice, you need to fix your code to load it only once.
Q: I don't see my question here, how do I get an answer?
Ask us! You can contact our support either by clicking on the lower right corner or by sending us an email to firstname.lastname@example.org. Also, search our help center! It has many other articles that may answer your questions as well.