> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.screeb.app/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# My survey is not displayed to my users. Help me!

Your survey should be showing up, but it's not? Follow this checklist in order: it covers the three most common reasons a survey fails to display, from the most basic (Screeb isn't even loaded) to the most specific (a targeting rule blocks it).

### More about targeting:

[👉 How to choose who will see your surveys (Targeting)](https://help.screeb.app/en/article/how-to-choose-who-will-see-your-surveys-targeting-zabc2s/)

[👉 How to use your users' properties to choose when to display surveys](https://help.screeb.app/en/article/how-to-use-your-users-properties-to-choose-when-to-display-surveys-1njz51k/)

## Step 1 — Is Screeb even loaded on the page?

Before looking at targeting rules, make sure the Screeb tag is actually running on the page you're testing. If it isn't, no targeting rule will ever matter.

**The easiest way: Screeb Inspector.** Open the [Screeb Inspector browser extension](https://help.screeb.app/en/article/introduction-to-screeb-inspector-1atchwk/) on the page, and check the **Overview** tab. If the installation is healthy, you'll see the health checks (API reachable, targeting engine running, etc.) all green. If Screeb isn't detected on the page at all, the extension shows a quick healthcheck popover instead of the full inspector, that's your answer right there.

![Screeb Inspector Overview tab showing installation health checks](https://storage.crisp.chat/users/helpdesk/website/-/1/c/7/c/1c7c00efcec1120/image_7oaflm.png)

**Without the extension:** open your browser's Developer Tools (right-click your page → "Inspect"), go to the **Console** tab, and type:

```
$screeb('debug');
```

If you get an error like `$screeb is not defined`, the tag isn't loaded on this page at all. This is a different problem from targeting, common causes are:
- A cookie consent banner (CMP) that hasn't been accepted yet: by design, Screeb only loads once consent is given (see [Consent Exemption](https://help.screeb.app/en/article/consent-exemption-1cyabdf/) if your organization is legally exempt from this).
- A corporate network, firewall or VPN blocking our domains.
- The tag not being installed on this particular page/environment.

If `$screeb('debug')` returns a session context instead of an error, the tag is loaded, move to Step 2.

## Step 2 — Is your survey actually running?

A survey that isn't started can't be displayed to anyone, no matter how your targeting rules are configured. This is an easy one to miss because everything else can look correctly configured.

Check your survey's **Diffusion** tab in the Screeb admin: it needs to be started/published there. You'll also see this directly in the debug tools below (a survey shown as **NOT RUNNING** in the targeting debug is simply not live yet).

## Step 3 — Check your targeting rules

Since the targeting engine built by Screeb runs in the background, you may not understand which rules prevent your survey from being displayed to a user. Two ways to check this:

### Option A: Screeb Inspector (recommended, no console needed)

Open [Screeb Inspector](https://help.screeb.app/en/article/introduction-to-screeb-inspector-1atchwk/) on the page and go to the **Surveys** tab. Each survey is shown as **excluded**, **eligible**, or **started/displayed**, with the exact rule that blocks it when it's excluded (URL not matching, property rule not satisfied, etc.). If you want to test conditions that aren't currently present on the live page (a different URL, a different property value...), use the **Simulate** tab instead of trying to reproduce them live.

![Screeb Inspector Surveys tab showing targeting status per survey](https://storage.crisp.chat/users/helpdesk/website/-/1/c/7/c/1c7c00efcec1120/image_8i0edy.png)

### Option B: the console command

On your website, right-click your page, then click "Inspect". In the Developer Tools, click on the "console" tab and enter the following Javascript command:

```
$screeb('targeting.debug');
```

Then <enter>.

You will get the list of your running surveys and the associated targeting rules.

![](https://storage.crisp.chat/users/helpdesk/website/-/9/4/6/6/94665f3b7aa5e800/94457feb-60a7-4134-a0b4-5823c7_ett5h4.png)

The rules with a green dot 🟢 are the ones that have been validated for this user. The rules with a red dot 🔴 are not validated and maybe the reason why your survey is not displayed.

![](https://storage.crisp.chat/users/helpdesk/website/-/8/1/4/1/8141291bdeffa000/62f5a18e-78b8-46fe-9d60-cd3480_1vz1qdc.png)

### The most common rule to trip on: URL targeting

A 🔴 on the **URL** rule means the current page doesn't match the pattern configured for this survey. Watch out for **subdomains**: a rule set to match `app.example.com` will **not** match `app.eu.example.com` or `staging.app.example.com`, even though they look like "the same site". If your survey needs to run on several (sub)domains, add each one as its own condition, or use a pattern/wildcard that covers all of them.

### What does 'Multiple display' mean?

When the "**Multiple display**" rule is set to "false 🔴", it means your survey has been already displayed to the current user and so you can't see it again.

This information is also visible in the user **timeline** where you can see that the survey has already been displayed:

![](https://storage.crisp.chat/users/helpdesk/website/-/7/a/9/b/7a9b599f6e2eb400/4038daec-2f14-484e-a0e3-61338a_r2p9bl.png)

## Still stuck?

If you've gone through all three steps and your survey still doesn't show up, reach out to us with: the exact URL you tested, and either your Screeb Inspector Overview + Surveys tab screenshots, or the output of `$screeb('targeting.debug')`. That's the fastest way for us to pinpoint the issue.