Skip to main content

Troubleshooting

If you have integrated the Web Feedback JavaScript APIs but the intercept is not appearing or behaving as expected, check the following.

Intercept Not Appearing​

  • Verify the deployment snippet – Ensure the Qualtrics Website Feedback snippet is correctly added to your page and loads without errors.
  • Check for qsi_js_loaded – Listen for the qsi_js_loaded event before calling QSI.API. The API is not available until this event fires.
  • Verify QSI and QSI.API – Before calling any API methods, confirm that QSI and QSI.API are defined.
  • Call order for manual loading – When using QSI.API.load() manually, you must call QSI.API.run() after loading completes. Use QSI.API.load().then(QSI.API.run) to chain them.
  • Intercept and creative status – Verify that the intercept and creative are published and active in the Qualtrics portal.
  • Targeting logic – Ensure the intercept's targeting logic passes for your test scenario. Sampling rate and "Prevent Repeated Display" settings can block display during testing.
  • Debug mode – Use debug mode to diagnose loading and targeting issues.

SPA-Specific Issues​

  • Unload before load – When switching routes, call QSI.API.unload() before QSI.API.load() to avoid stale creatives.
  • Chain load and run – Use QSI.API.load().then(QSI.API.run) to ensure the intercept runs immediately after loading.

Session Recording Issues​

  • Consent before start – Call QSI.API.SessionRecording.start() only after the user has consented. See Pairing with Session Recording and Recording and Consent.
  • Error handling – start() can throw SampledOutError, MismatchSessionInfoCookieError, or MissingSessionInfoCookieError. Clear cookies and reload if you encounter these during testing.

API Reference​

For full method signatures and behavior, see the API Reference.