Skip to main content
If you have a Content Security Policy on your website, it can block the JS agent. JS agent will throw a special error in this case:
JavaScript
Add the following directives to your policy to unblock the JS agent: 
script-src https://fpjscdn.net;
connect-src https://api.fpjs.io https://*.api.fpjs.io;
If you already have such directives in your policy, add the given addresses to the directives. An example of combining a couple of policies: 
default-src 'self';
connect-src 'self' example.com;
style-src 'self' 'unsafe-inline';
An example of an HTML code with a Content Security Policy that lets JS agent work: 
<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Security-Policy" content="
      default-src 'self';
      script-src 'self' https://fpjscdn.net;
      connect-src 'self' https://api.fpjs.io https://*.api.fpjs.io;
    ">
  </head>
  ...
</html>

​
Automatic updates

The default endpoints used by JS agent may change with automatic updates. JS agent uses fallback endpoints to evade ad blockers that block JS agent. The fallback endpoints are changed when they get to ad blocker lists. So you should check this guide from time to time for up-to-date CSP recommendations to ensure your CSP doesn’t block the fallback endpoints. The primary endpoint (https://api.fpjs.io or https://*.api.fpjs.io) is never changed automatically to prevent JS agent from being blocked by your CSP.

​
Subdomain setup

If you’ve set up JS agent to use a custom endpoint, add the endpoint to the policy instead of the built-in endpoint. For example, if your custom endpoint is https://fp.yourdomain.com, your policy is: 
script-src https://fpjscdn.net;
connect-src https://fp.yourdomain.com;