Skip to content
Open Screeb

How Screeb collects user data, decides which survey or message to show, and where the data goes next.

Screeb collects data about your users, checks it against the targeting rules of your surveys and messages, and displays the ones a user is eligible for. Responses and user data are then analyzed in the admin and can be sent to your other tools.

Four kinds of data describe a user:

Data What it is
Identity The unique ID you give the user, usually your own user ID. Without it, the user stays anonymous.
Properties Key-value pairs that describe the user: plan, role, sign-up date…
Events What the user does in your product, tracked as named events with optional properties. Screen views and page views are events too.
Groups The groups the user belongs to, such as a company or a team, used to build segments.

Identity is optional: an anonymous user can still be targeted and answer surveys.

  1. Your app initializes the SDK once, as early as possible, with your channel ID.
  2. As the user moves through your app, your code identifies them and tracks their properties, events and screens.
  3. On each change, Screeb evaluates the targeting rules set in the admin.
  4. When the user matches the rules of a survey or a message, Screeb displays it inside your app.
  5. The answers come back to Screeb, where they are analyzed, and can be forwarded to your tools.

You can also skip targeting and start a survey or a message from your code, for example right after a key action.

The Screeb SDK is the main source of data, and the only one that can display surveys and messages. Install it in your website or mobile app first.

If your user data already flows through a customer data platform, Screeb can read it from there instead of tracking it a second time:

Your backend can also send data directly with the Screeb API.

Screeb sends responses and user data to the tools your team uses: webhooks, data warehouses through Stitch or SFTP, and a catalog of integrations listed in the help center.