Warning! The article below is slightly more technical. If it leaves you with a headache, forward this article to your website administrator or your technical team and ask for help!

Once you have installed the Leadfeeder Tracker, you should be able to see it 'fire' in the network tab of your browser. Use this article to do the necessary checks for the script on the site. 

If you know the script is on the site and you don't see a '200' status, as shown above, the tracker may be blocked by a 'Content Security Policy' (CSP). In the example below, you can see by searching for 'lftracker' has a status of (blocked:csp).

You may also see that it appears that the script is run, but is later blocked (see below). This would also impact the Leadfeeder Tracker, and your CSP should be checked.

Content Security Policies are set by your team, either manually or via a security tool. In WordPress it's also possible to use a plugin. They are delivered as a header to all of your visitors' browsers whenever they visit your website.

These are the 'rules' used only to 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 the Leadfeeder Tracker! You will need to take a couple of extra steps to get it set up correctly.

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.

Also, if your rules include img-src and script-src, add *.lfeeder.com and *.leadfeeder.com also to those rules.

These are the basic steps; your web or technical team may know more. Every website is unique, and yours may need something different.
​

--

Questions, comments, feedback? Please let us know by contacting our support team via the chat or by sending us an email at support@dealfront.com.

RELATED: