Default User Properties and How to Use Them

Screeb tracking supports a collection of standard properties. Using these optional properties, in the correct format, will unlock many features in the platform.

Properties you'd send to Screeb using those names but not respecting the correct value format would be dropped.

Default User Properties:

In SDKs, it is recommended to identify users by using an immutable user_id instead of user email. Providing these fields to Screeb will ease your user analysis in the platform.

A user will be considered as "identified" as soon as one of the following properties is provided: firstname, lastname, name, fullname, username and/or email. Otherwise, we'll consider them "anonymous" in our platform.

Default Group Properties:

In SDKs, it is recommended to identify groups by using an immutable group_id instead of a group name. Providing a "name" property to Screeb will ease your user analysis in the platform.

How to track user properties in Screeb

Unlock the full power of Screeb targeting and get a deeper understanding of your users by tracking their properties. Here's how.

You can add Screeb by simple copy and pasting the tag

For your web app, 👉click here

For your mobile app,👉 click here

And you can also track your users events in your web/mobile app. Read this complete guide to know how to.

But yo can go further and use this exact same tag to track your users properties in Screeb.

Why would I do that?

Tracking your users' properties in Screeb is useful for three things:

1️⃣ Enhancing targeting

You'll be able to use your users' properties as targeting conditions to decide who will see your surveys or not.

Let's say you want to display a survey to users who have a specific role at your customers. If you track the role property in Screeb, you'll be able to use it as a targeting condition, like this:

'Role' and 'manager' here only being examples. You can track any property you have about your users and check any type of value for these properties.

2️⃣ Better user identification in reports

Users properties are also 'attached' to data in the Screeb reports. It means that with every response or score you'll read in Screeb's reports, you'll be able to see all your users properties attached to it, like this:

On the same screen, you'll also find default properties we automatically track, such as their user agent, their device, their language, etc.

3️⃣ Complete data transmission through webhook

All the users properties you track are also 'attached' to responses when you send them via webhook to other tools. It means that you can crunch them in another solution as any other data, or that you can use them to filter or route responses in solutions like Zapier or Integromat.

👉 Please read our Webhook Documentation if you need more information about that.

4️⃣ Questions customisation with variables

Customise your questions with data about your users and provide them with an awesome personalised experience!

👉 Read our complete guide here to do that

I'm sold! How can I track my users properties?

Tracking your users properties with Screeb is pretty simple.

👉 You'll find detailed explanations in our Developer Documentation on Github.

Everything is made through our Javascript Tag. In the tag we provide, we already added some examples of properties you can track:

In that example, we added the email, firstname, lastname, plan properties, last seen at and authenticated. But feel free to track anything you want!

Those properties must be found in your app frontend. We don't provide a backend API yet for you to push them to Screeb. But for every data you have in your frontend, you can track them in Screeb.

Updated on: 15/01/2026