Deutsch
Testen

Why is the Leadfeeder Tracker Blocked on My Site?

Installed the Leadfeeder Tracker but it's not firing? In this video, we’ll show you how to check if your site’s Content Security Policy (CSP) is blocking it. You’ll learn how to use your browser’s Developer Tools to spot a CSP issue, what a CSP is, and how to update your rules to allow the tracker. Using a CMS like WordPress? We’ve got tips for that too. Need help? Our support team is here for you!


Video Transcript

If you’ve installed the Leadfeeder Tracker but it’s not firing on your site—don’t worry. In this quick video, we’ll walk you through one common reason why: your own site’s rules might be blocking it.

First, let’s check if the tracker is actually loading. Open your browser’s Developer Tools and go to the Network tab.

Now refresh your site and search for lftracker. If it’s working correctly, you should see a request with a status code of 200.

But if you don’t see a 200 status—or worse, you see something like ‘blocked:csp’—that means the tracker is being blocked by your Content Security Policy, or CSP.

So what’s a CSP? In simple terms, it’s a set of security rules that your team or your content management system sets to control what external content your website is allowed to load.

These policies are like antibiotics - they are meant to protect your visitors from harmful scripts, but sometimes they block good ones too—like the Leadfeeder Tracker.

If you’re using a CMS like WordPress, you might have a plugin that manages your CSP settings.

If you are using a default CSP, we recommend making sure these domains are added to your default-src rules. 

For more granular rules, you can add these domains.

Also, if your rules include img-src and script-src, add these to those rules as well.

That’s it! Having a CSP doesn't mean you can't use Leadfeeder. You just need to update your rules a bit.

And of course, if you have any questions or run into issues, reach out to our support team — we’re happy to help!