If your web app uses a Content Security Policy (CSP), the policy has to allow the domains Userflow.js loads from and connects to. If it doesn’t, Userflow content won’t show, or shows without its images and videos.
Which domains does my Content Security Policy need to allow for Userflow?
Your Content Security Policy must allow these domains for Userflow.js:
connect-src:
https://cdn.userflow.com
https://e.userflow.com
https://e.eu.userflow.com
https://js.userflow.com
wss://e.userflow.com
wss://e.eu.userflow.com
script-src:
https://cdn.userflow.com
https://js.userflow.com
style-src:
https://cdn.userflow.com
https://js.userflow.com
img-src:
https://blob.userflow.com
https://cdn.userflow.com
https://js.userflow.com
https://storage.googleapis.com/studio1-prod-blob/
media-src:
https://blob.userflow.com
https://cdn.userflow.com
https://storage.googleapis.com/studio1-prod-blob/
frame-src:
https://cdn.userflow.comThe storage.googleapis.com/studio1-prod-blob/ address is a legacy name: studio1 was the company’s original name.
How can I tell my Content Security Policy is blocking Userflow?
If your Content Security Policy is missing one of the domains Userflow.js needs (the userflow.com addresses and storage.googleapis.com/studio1-prod-blob/), you’ll usually see one of these:
Userflow content doesn’t appear at all, or the installation check says Userflow.js isn’t loading.
Your browser console shows an error like Refused to load… or Refused to connect… because it violates the following Content Security Policy directive, naming a userflow.com address.
Content shows, but images or videos inside steps are broken. This usually means
img-srcormedia-srcis missing a domain.
To fix it, add the domain named in the error to the directive it mentions, then reload the page. The full list is in Which domains does my Content Security Policy need to allow for Userflow?
Userflow works for some users or networks but not others
Userflow’s domains can also be blocked outside your Content Security Policy. Corporate firewalls, proxies, DNS filters, and ad-blocking or privacy browser extensions can all block them. If Userflow works for some users or networks but not others:
Ask an affected user to try with browser extensions turned off, or on a different network.
If that fixes it, have their IT team allow these domains: cdn.userflow.com, js.userflow.com, e.userflow.com, e.eu.userflow.com, blob.userflow.com, and storage.googleapis.com/studio1-prod-blob/.