Having trouble with surveys? Below are some tips for getting past some common issues
The most common solution is...
Surveys requires either the latest version of the PostHog snippet or version 1.81.3 or greater of
posthog-js to be installed on your website.
We're always making improvements to the surveys feature, so you'll want to make sure that you're running the latest version.
To check the version that you're using, you can run the following in your browser console:
Surveys still not showing up
If updating PostHog doesn't solve your problem, there are a few reasons why your survey might not be showing up:
1. Configuration is off
Surveys are enabled through the surveys opt in toggle in the app. If you're not seeing any surveys, make sure that this toggle is enabled.
You can read more about
posthog-js configurations here.
2. Content security policy
When surveys are enabled,
posthog-js will fetch a
survey.js script from the PostHog server. It is not included in the default
posthog-js installation to minimize the default bundle size.
Depending on your content security policy, this script may be blocked. If it is, you should see an error message in your developer console with more details.
You may need to add
https://eu.posthog.com, or your host URL if you are self hosted) to your allow list.
If you're running behind a proxy, the
/static/survey.js endpoint may be blocked. Read more about how to configure your proxy to allow this endpoint.
3. Ad or tracking blockers
Some ad or tracking blockers block PostHog from fetching
posthog-js. If you're testing your app locally, you may need to disable any ad/tracking blockers that you're running in your browser.
In production, using a reverse proxy can help prevent this.
Debugging surveys in console
You can call
getActiveMatchingSurveys in your browser console to see which surveys are currently active for the user. If the method doesn't exist, it means that you're not running the latest version of
posthog.getActiveMatchingSurveys(surveys => console.log(surveys))