Screeb Inspector

Screeb Inspector is a visual debugging tool that helps you understand how Screeb behaves on a page without using the browser console. You can use it to troubleshoot Surveys, Messages, and Session Replay, check whether your installation is healthy, inspect what Screeb receives from the page, and test targeting in controlled conditions.
Instead of relying on technical commands, you can read the current state of Screeb from a dedicated interface and understand why something is working, not working, or waiting to start.

Screeb Inspector is a debugging interface for Screeb installations on web and mobile web.
It helps you answer questions such as:

• Why is my survey not showing?
• Why is my message not starting?
• Is session replay recording?
• Is the Screeb SDK installed correctly?
• What events and properties is Screeb receiving?
• Would this survey or message match under different conditions?

Screeb Inspector is designed to make this information accessible directly from the page, without opening developer tools.

Legend: Screeb Inspector centralizes health checks, targeting diagnostics, events, properties, and simulation in one interface.

Who is it for?

Screeb Inspector is especially useful if you work in a product, marketing, or operations role and need to troubleshoot Screeb behavior without relying on browser console commands.
It is built for teams who want to debug quickly from a clear interface instead of using technical tooling.
Anyone can install the browser extension and open the inspector on a site where Screeb is installed, but the level of detail you can access depends on whether you are in Guest mode or Logged-in mode.

Where to find it

You can open Screeb Inspector from two places: the Screeb admin and the browser extension.

From the Screeb admin

In the account contextual menu, click Open Inspector.
This opens a modal where you can enter a URL or select one of the most recent URLs. Once you choose a page, it opens with Screeb Inspector.
This same entry point is also where you can obtain the JWT used later to authenticate the inspector.

Legend: Open Screeb Inspector from the admin and choose the page you want to debug.

From the browser extension

You can also open Screeb Inspector from the Screeb extension in Chrome, Firefox, or Safari.
When the current site does not expose the Screeb SDK, the extension appears inactive. When Screeb is detected, the extension lights up and clicking it opens the inspector.
If Screeb is not accessible on the current page, clicking the extension opens a healthcheck popover instead of the full inspector.

Legend: The extension becomes active when Screeb SDK is detected on the current page. If Screeb cannot be reached, the extension shows a quick healthcheck instead of the full inspector.

Extensions per Browser:

• Chrome
• Firefox
• Safari (coming coon)

Guest vs Logged in

Once you open Screeb Inspector, you may use it either in Guest mode or in Logged-in mode.

Guest mode

Guest mode gives you access to public runtime information. You can inspect the current session, review events, and see which surveys and messages are eligible or excluded. This is useful when you want a quick diagnostic without exposing workspace-sensitive information.
In Guest mode, some information is intentionally hidden. For example, survey and message names are not shown, and the Properties tab remains empty.

Logged-in mode

Logged-in mode unlocks the full debugging experience. You can see survey and message names, inspect visitor properties, run simulations, use advanced controls, and access storage tools.
To switch to Logged-in mode, paste a JWT token into the authentication block in Settings. This token is obtained from the same admin flow where you open the inspector.
The token is:

• valid for 24 hours
• restricted to one workspace
• used to unlock private details such as names and properties

This separation helps preserve confidentiality when the inspector is opened by someone who should only access public runtime information.

Legend: Paste a temporary JWT token to unlock authenticated mode for one workspace.

Healthcheck

When you first open Screeb Inspector, the best place to start is the Overview tab. This is where you confirm that Screeb is installed correctly and currently running in healthy conditions.
The Overview tab shows the current visitor, the detected environment, a summary of surveys and messages, and the current session replay status.
It also includes the Installation & Health Doctor, which checks whether the Screeb installation is operational. This section helps you verify that the key dependencies required by Screeb are available and properly configured.
The health checks include:

• API reachable
• Report reachable
• Websocket reachable
• Fonts allowed and loaded
• Media allowed
• Respondent identified
• Monthly user quota within usage
• Targeting engine running
• Session recording active

This is the fastest way to understand whether the issue comes from installation health or from something more specific such as targeting.

Session replay status

In the Overview tab, Screeb Inspector also reports the current replay state. It can show:

• unavailable when the session is not loaded
• stopped when no session is currently running
• recording when session replay is active

Legend: Start in Overview to confirm installation health and identify whether the problem is technical or targeting-related.

Targeting

Once the installation looks healthy, the next step is usually to understand targeting.
Screeb Inspector helps you investigate targeting in both the Surveys and Messages tabs.
In these views, you can see whether an item is:

• excluded, meaning the targeting rules are not all validated
• eligible, meaning the targeting rules are validated but the item is not yet visible
• started or displayed, meaning it is on screen

For messages, you can also inspect step-level status. A step may remain not displayed if its own display conditions are not fully validated, even when the message itself has already started.
The key value of these tabs is not only the status label, but the explanation behind it. Screeb Inspector shows why a rule passes or fails, so you can immediately see what blocks eligibility. For example, you may see that the current URL does not match an expected value, or that a property rule is not satisfied.
In Guest mode, each item is shown by ID. In Logged-in mode, names are displayed instead.

Surveys

In the Surveys tab, you can review the survey list, refresh the data, inspect each survey’s interaction format, and drill into the start conditions that determine whether it should run.

Messages

In the Messages tab, you can do the same for messages, with the additional ability to inspect step-level display conditions after a message has started.

Legend: Use the Surveys tab to understand whether a survey is excluded, eligible, or already started.

Legend: Use the Messages tab to inspect both message-level targeting and step-level display conditions.

Events & properties

After you confirm health and targeting, the next question is often whether Screeb is receiving the right data from the page.
Screeb Inspector lets you investigate this through Events and Properties.

Events

The Events tab shows the events sent by the current visitor with live refresh. You can search and filter the list to focus on a specific event or timeframe, then open an event to inspect its properties.
This is helpful when you want to verify that the expected trigger event has actually been sent and received.

Properties

The Properties tab shows the current defined properties, including their name, type, value, and source.
This tab is only available in Logged-in mode. In Guest mode, it is intentionally empty to protect potentially private information that your company may send to Screeb.
Together, these two tabs help you verify that Screeb is receiving the right inputs before you conclude that a targeting rule is wrong.

Legend: Use the Events tab to confirm which events Screeb receives from the page.

Legend: In Logged-in mode, the Properties tab helps you inspect the exact visitor data used by Screeb.

Simulation

When you want to go one step further, use the Simulate tab.
Simulation lets you test how targeting would behave under conditions you define yourself. This is useful when the live page does not currently match the scenario you want to validate.
You can edit the simulated environment, including URL, platform, locale, app version, mobile screen, current time, and session start. You can also add, update, or remove visitor events and properties.
Once your setup is ready, run the simulation to see which rules validate and which rules exclude each survey or message. You can save scenarios and reuse them later, or reset everything back to the live default state.
If you need to test the full real targeting flow, you can use Start Live Simulation. This behaves like a preview, but instead of forcing a preview directly from the admin, it lets the survey or message appear through targeting logic. This makes it useful when you want to validate how Screeb behaves in realistic conditions.
A live simulation does not count responses and does not create new users.

Legend: Use simulation to reproduce conditions that are not currently present on the live page.

Legend: Simulation results explain exactly why each survey or message would match or fail.

Settings

The Settings tab gathers the controls you need to manage how Screeb Inspector behaves and how it stores local Screeb state.
This is where you authenticate with your JWT token, enable automatic reopening on a domain, inspect Screeb-related storage, and clear local data when you need a clean troubleshooting state.

Auto open on this domain

If you enable Auto open on this domain, Screeb Inspector follows you as you navigate pages on that domain. This is useful when you want to keep the inspector available during a full test flow.

Storage inspection

The storage section displays JSON data fetched from local storage. You can copy the whole payload or individual entries. This is especially useful when you need to share technical context with support or compare stored state across sessions.

Danger Zone

When local Screeb state may be affecting behavior, you can clear specific storage areas:

• stored survey responses
• identity
• server cache
• session
• all

This can help you restart testing from a clean local state.

About

The About section repeats core runtime information such as SDK version and, when authenticated, workspace name.

Legend: Use Settings to authenticate, manage Inspector behavior, inspect storage, and reset local Screeb state.

A recommended troubleshooting flow

When something is not working as expected, this is the easiest way to use Screeb Inspector from start to finish:
First, open the inspector and go to Overview. Confirm that the installation is healthy and that session replay, connectivity, and the targeting engine are in the expected state.
Next, move to Surveys or Messages, depending on what you are troubleshooting. Check whether the item is excluded, eligible, or started, and inspect the explanation for the failing rule.
Then, go to Events and Properties to verify that Screeb is receiving the right inputs from the page.
If the live page does not let you reproduce the expected scenario, switch to Simulate and create the conditions manually. Run the simulation, inspect the result, and use Start Live Simulation if you need to validate the real targeting path.
Finally, use Settings if you need to authenticate, inspect stored Screeb data, or reset local state before testing again.

Why Screeb Inspector matters

Screeb Inspector removes the friction of traditional debugging. Instead of asking you to open the console and paste commands, it presents everything you need in a structured interface.
That makes it much easier to troubleshoot Screeb when you are part of a product or marketing team and want to work directly from the page.

Updated on: 28/07/2026