DXA Test Sessions banner not appearing

If your deployment code is otherwise working (like showing feedback buttons), this usually points to a few hidden blockers with initialization, network rules, or custom domains.

A big one to check right away is whether your organization uses a vanity URL (a custom Qualtrics domain). If your project runs on a custom domain, standard test-session cookies fail to write properly to *.qualtrics.com due to strict browser cross-domain restrictions. If that's the case, you actually have to use a specific javascript bookmarklet workaround to manually force-inject the test-session cookie into your browser before loading your site.If you aren't using a vanity domain, your best next step is to open your browser’s DevTools and look into the Network and Application tabs. Under cookies, verify if

QSI_ReplaySession_Info_<ZoneId> is present—this is the cookie that tells DXA to initialize and record. While you're in DevTools, refresh the page and filter the Network tab for sessions/create, sessions/validate, and sessions/record-playback. If the create or record-playback calls are missing or throwing errors, data isn't transmitting correctly. This is frequently caused by a strict Content Security Policy (CSP) blocking Qualtrics resources, so you may need your web engineering team to allowlist connect-src https://*.qualtrics.com along with the related script/frame directives.It is also worth noting that if you are using an event listener like qsi_js_loaded to kick off a custom consent flow, running it before the Website Feedback API fully initializes can cause the recording session to drop entirely before the banner ever gets a chance to render.