Why can't I see the Leadfeeder Tracker firing on my website?
Warning! The article below is slightly more technical. If it leaves you with a headache forward this article to your website or technical team and ask for help!
If this is an issue for you, you may need them anyway!
Once you have installed Leadfeeder Tracker you should be able to see it 'fire' in the network tab of your browser. Use this article to do the basic checks for the script on the site.
If you see this (below), move along, the rest of this article doesn't apply to you.
If you know the script is on the site and you aren't seeing a '200' status as shown above Tracker may be blocked by a 'Content Security Policy'. In the example below, you can see by searching for 'lftracker' has a status of (blocked:csp).
Content Security Policies are set by your team, either manually or via a security tool. They are delivered as a header to all of your visitors' browsers whenever they visit your website.
These are the 'rules' used to only allow specific dynamic resources to load on your page. They are typically used to protect the site from scripts being placed for malicious or invasive reasons.
Having a Content Security Policy does not mean you can't use Leadfeeder Tracker! You will need to take a couple of extra steps to get it set up properly.
If you are using a default CSP we recommend adding *.lfeeder.com and *.leadfeeder.com to your default-src rules. For more granular rules you can add sc.lfeeder.com and lftracker.leadfeeder.com.
These are the basic steps, your web or technical team may know more. Every website is unique and yours may need something different.
If you have other questions or need more information please reach out, we are happy to help via our live chat or email to firstname.lastname@example.org