Fix NPS survey not displaying to eligible users

Expected Behavior The NPS survey should reliably display to eligible users when the configured trigger conditions are met (e.g., after session completion or on dashboard load), across supported browsers and devices, without blocking core interactions. Current Behavior Eligible users do not see the NPS survey. No modal/banner appears, resulting in zero impressions and reduced feedback capture. Occurs consistently in production and intermittently in staging. Possible Solution Verify feature flag/configuration and targeting rules are correctly enabled in production. Ensure the survey SDK initializes after consent/state is available and that event listeners fire (avoid race conditions). Check CSS/z-index and container visibility to prevent hidden or off-screen rendering. Review CSP and ad/script blockers that may block survey scripts/assets; host locally or adjust CSP as needed. Confirm cooldown/dismissal logic isn’t over-suppressing (e.g., long suppression windows, overly broad cohorts). Steps to Reproduce Log in as a user who meets NPS eligibility criteria (e.g., completed a session, not previously suppressed). Navigate to the dashboard/home page and perform the action that triggers the survey. Wait for the configured delay/trigger. Observe that the NPS survey does not appear; check browser console and network logs for survey-related errors or blocked requests. Context (Environment) Lack of NPS impressions prevents collecting user sentiment, affecting product decision-making and KPIs. The issue is observed in production and impacts desktop and mobile users across major browsers. Timely fix is needed to restore feedback collection and measurement.