Skip to main content
The on page QA overlay has not shipped. The QA Overlay tab in the preview modal currently shows a “Shipping next” placeholder where the overlay control will go. There is no debug panel injected onto your site yet.What the tab does give you today is a QA session link, described below. For inspecting what the snippet did on a page, use the dev debugger, which is fully working.
A normal preview link carries a token scoped to one experiment. A QA session link carries a broader, site scoped token: it authorizes every draft and paused experiment on that site, so you can append another experiment’s pair to the URL by hand without going back to the dashboard for a new link.
1

Open the preview modal

Go into the experiment and open Preview, then switch to the QA Overlay tab.
2

Create the link

Click the action to create a QA session link. Nothing is minted until you click, because this is the wider credential.
3

Copy it

The link is built from the variation currently selected, so it opens something immediately. Copy it, or regenerate it if you need a fresh one.

​
What it is scoped to

  • Every draft and paused experiment on that one site. It is not limited to the experiment you happened to open.
  • 24 hours. After that the link stops working and you create another.
  • Your registered domain, and localhost only if you tick that option before creating the link. The choice is baked into the token, so changing it means minting a new one.

​
Who can create one

The action appears only for users whose role grants QA session access on that site. The server enforces this on the mint request itself, so the hidden button is a convenience rather than the boundary. If you do not see the action, ask an admin about your role in Team and Access.
A QA session link reads all of a site’s unpublished experiment code for 24 hours. Treat it as a developer credential rather than something to forward. If one leaks, use Revoke all preview links in the site’s Settings → Danger zone, which invalidates every preview link and QA session link for that site immediately, including ones already open in someone’s browser.
QA Overlay tab showing a Shipping next placeholder

The overlay half of the QA Overlay tab today. The QA session link action appears above it for users whose role grants it.

​
What the overlay will do

When it ships, the overlay is planned as a floating panel showing which experiments and variations are active on the page, whether the visitor matched targeting, and goal fires as they happen, built on the same debug store the dev debugger already reads.

​
What an overlay could not prove

Worth knowing in advance, because it also applies to the debugger today: a panel like this observes what the snippet does in your browser. It can show that the snippet decided to send an event. It cannot show that the event was accepted by the ingest endpoint, passed filters such as blocked IPs, or was written to your results. See What the debugger does not prove. Last verified against the shipped dashboard and snippet on 2026-09-01.
Last modified on September 11, 2026