# Glossary

The terms used across the Screeb SDKs, the Screeb API and this documentation.

The terms this documentation uses, in alphabetical order. The words of the admin (survey editor, reports...) are in the [help center glossary](https://help.screeb.app/getting-started/glossary/).

## Anonymous user

A user your code has not identified yet. Screeb gives each one an anonymous ID and can still target them. Anonymous users count toward your Monthly Tracked Users.

## Channel ID

The identifier of your Screeb channel: one per website or mobile app. You pass it when you initialize the SDK. Find it in your [install settings](https://admin.screeb.app/org/last/settings/install). Older pages call it the website ID.

## Distribution

One targeting setup of a survey. When you start a survey from code, you can pass the ID of the distribution to use; without it, Screeb uses the default one.

## Hook

A callback your code registers to react to a Screeb event: a survey shown, a question answered, a survey completed... You pass hooks when you initialize the SDK or when you start a survey or a message.

## Identity

The user profile attached to the current session: a user ID and its properties. Screeb uses it to target surveys, build segments and enrich responses.

## In-app message

A message Screeb displays inside your app or website: popover, banner, modal, sidebar or beacon. Targeting rules show it, or your code starts it.

## Monthly Tracked Users (MTU)

The number of unique users, identified and anonymous, that Screeb tracks in a month. Turn the SDK off in CI and test environments so they do not count.

## Session replay

A recording of what a user does in your app (clicks, scrolls, screens), replayed in the admin next to their responses. Every SDK supports it; your workspace settings and plan decide whether it runs.

## Survey

A questionnaire displayed inside your app: NPS, CSAT, open questions and more. Targeting rules show it, or your code starts it.

## Targeting

The rules that decide which users see a survey or a message, and when: user properties, events, groups, pages or screens. The product team sets them in the admin.

## Widget

The Screeb UI element rendered in your app: a survey or an in-app message.

## SDK names

| Name           | What it is                                                                                                                             |
| -------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| JavaScript tag | The HTML snippet that loads `tag.js` and exposes the global `$screeb()` function. No bundler needed.                                   |
| Browser SDK    | The `@screeb/sdk-browser` npm package: a typed wrapper around the tag for any JavaScript app.                                          |
| Framework SDKs | `@screeb/sdk-react`, `@screeb/sdk-vue`, `@screeb/sdk-angular` (also used by Ionic) and `@screeb/sdk-svelte`, built on the Browser SDK. |
| Native SDKs    | iOS, Android, and the React Native, Flutter, Kotlin Multiplatform and .NET MAUI SDKs, which wrap them.                                 |

## `shouldLoad` and `autoInit`

Options of the React, Vue, Angular, Ionic and Svelte SDKs:

- `shouldLoad: false` stops the SDK from loading the Screeb tag, which is useful in test environments.
- `autoInit: true` initializes Screeb as soon as the tag is loaded.
