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.
4️⃣ Questions customisation with variables
Customise your questions with data about your users and provide them with an awesome personalised experience!
I'm sold! How can I track my users properties?
Tracking your users properties with Screeb is pretty simple.
In that example, we added the email, firstname, lastname and plans properties. 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.