Hey there @Mailing!

 I've checked in with my team and we don't currently have a list like you're requesting, however, all of the resources will originate from klaviyo.com​ and so I believe that your example from the first email of using *.klaviyo.com​ is going to be the best way to accomplish this.

Hope this helped!
Alex​​​​​​​

Hi @alex.hong,

I’d like to follow this up with a request for a page in the documentation specifically related to CSP configuration for Klaviyo and any on-site scripts.

There are a number of different assets required to be added to the CSP and simply adding *.klaviyo.com to all directives is not best practice.

Providing the specific directives and the URLs such as here https://developers.google.com/tag-platform/tag-manager/web/csp so that a wildcard doesn’t need adding would be far more useful.

Regards,
David.

Hi there @dgreenwooduktf!
Thank you for your feedback and additional details regarding this manner with Klaviyo and CSPs. I have put your comments into a product request so that our team can get some eyes on this feature. 

Have a good day,

Alex

You’ll need the following:

connect-src *.klaviyo.com; script-src *.klaviyo.com;

It doesn’t inspire confidence when things like this aren’t documented.

Hi @alex.hong,

Wanted to get an update on this and also to point out that https://static-tracking.klaviyo.com/onsite/js/datadome.js is making a connection to https://api-js.datadome.co/js/ which also needs documenting.

Has this document been created yet? Searching for information on Klaviyos CSPs just brought me back here again.

Thanks,
David.