Installing Exatom with a Content Security Policy

Installing Exatom with a Content Security Policy

Exatom tags can be installed on websites that have a Content Security Policy (CSP). Typically, you will need to reach out to your website server, network, or IT department to request changes for this.

Option 1: Add Exatom to the default Content Security Policy

Use the default-src as CSP directive and add *.exatom.io to the list of allowed sources.

Example of a new Content Security Policy
  1. Content-Security-Policy: default-src 'self' *.exatom.io
Example of an existing Content Security Policy where Exatom was added to
  1. Content-Security-Policy: default-src 'self' *.example.com *.example.org *.exatom.io


Option 2: Add Exatom to the granular Content Security Policy controls

When more granular controls are needed, the following directives can be used script-src, connect-src, style-src and img-src to allow our *.exatom.io domain.
  1. Content-Security-Policy:
  2.   script-src 'self' *.exatom.io;
  3.   connect-src 'self' *.exatom.io;
  4.   style-src 'self' *.exatom.io;
  5.   img-src 'self' *.exatom.io;