Try or ByeTry or Bye

PostHog Surveys Not Showing

Workaround available Web Updated October 21, 2026

Quick answer

PostHog surveys don't appear when surveys are disabled in project settings or the SDK config, posthog-js is too old, or CSP, a proxy or an ad blocker blocks surveys.js. Run getActiveMatchingSurveys in the console to see what matches.

Most likely fix: Enable surveys.

Symptoms

A launched popover or feedback-button survey never appears for users who match targeting.

Why it happens

  • Surveys not enabled in project Settings
  • disable_surveys or advanced_disable_feature_flags set to true
  • posthog-js older than 1.81.3
  • CSP or a proxy blocking /static/surveys.js
  • Ad or tracking blocker
  • Event-triggered survey relying on a backend event (only client-side events trigger surveys)

How to fix it

Try these in order — the most common fix is first.

  1. 1. Enable surveys

    1. Open Settings in the left sidebar and turn surveys on for the project/environment
    2. Remove disable_surveys and advanced_disable_feature_flags from posthog.init()

  2. 2. Update and debug the SDK

    1. Run window.posthog.LIB_VERSION and update posthog-js
    2. Run posthog.getActiveMatchingSurveys(s => console.log(s)) to see which surveys match the current user

  3. 3. Unblock surveys.js

    1. Allow PostHog domains in your CSP script-src and connect-src
    2. If you use a proxy, allow /static/surveys.js through it
    3. Test without ad blockers

  4. 4. Fix targeting

    1. Capture the triggering event client-side, not from the backend
    2. Replace dynamic behavioral cohorts in person-property targeting with a static cohort

This guide also covers

  • posthog survey not showing
  • posthog surveys not working
  • posthog popover survey not appearing

Still not working?

If PostHog keeps failing, you're not alone. See every PostHog problem users report or the alternatives people switch to.

Other PostHog errors