Skip to main content
Version: iOS SDK

Identity

Set identity​

Tip: If you already know the user's ID at startup, pass it directly to Screeb.initSdk() to avoid creating an anonymous visitor.

When a user is identified in your app, you won't be able to identify who responded to surveys until you call the setIdentity command.

Thanks to this, you will be able to track this user over multiple platforms (desktop, mobile, tablet...).

The identifier of your app user must be unique and idempotent. User email is good, but can change over time. We recommend that you use the user id.

Requirements:
  • The unique app user id must have a length between 1 to 255 characters.
import Screeb
...
// assign current session to a user identifier (such as your internal user id, an email address...)
Screeb.setIdentity(uniqueVisitorId: "<USER-ID>")

// You can also add properties (see Attributes configuration below) when calling identity command :
Screeb.setIdentity(uniqueVisitorId: "<USER-ID>", visitorProperty: [
            "age": AnyEncodable(27),
            "category": AnyEncodable("cycle"),
            "purchasedAt": AnyEncodable(Date())
        ])

Reset current identity​

When the user logs out, please call the resetIdentity command.

This command must be called only once, since it creates a new identity on Screeb side. If you call it on every anonymous view, you won't be able to track app usage and surveys will be sent many times to the same app user.

Screeb.resetIdentity()

Ignore anonymous user​

If you want to ignore anonymous users and only track identified users, you can use the ignore Anonymous option. This will ensure that no data is collected for users who have not been identified.

To Activate the ignore Anonymous option, go to your screeb workspace settings and set the ignore Anonymous option to true. (go to your workspace Settings)

By setting ignore Anonymous to true, the widget will not collect any data until the identity command is called with a unique app user identifier.

Attributes​

Screeb allows tracking some custom data about your app users. Those properties can be inserted as "hidden fields" in your surveys or can be used for an advanced targeting rule.

Requirements:
  • Property names must be limited to 128 characters
  • No more than 1000 attributes
  • Supported types for values: string, number (Int, Long, Double), boolean and Date.
import Screeb
...
// set visitor properties
Screeb.visitorProperty(visitorProperty: [
  "email": AnyEncodable("support@screeb.app"),
  "age": AnyEncodable(29),
  "logged": AnyEncodable(true),
  "signed_up_at": AnyEncodable(Date()),
])

// Delete visitor property: set values to nil
Screeb.visitorProperty(visitorProperty: [
  "email": AnyEncodable("support@screeb.app"),
  "age": AnyEncodable(29),
  "logged": nil,
  "signed_up_at": AnyEncodable(Date()),
])

Good practices with an existing CDP​

When Amplitude, Segment or RudderStack is a Screeb source, Screeb resolves the respondent of each forwarded event from its user id, or from its anonymous id when the visitor is not logged in. Once both ids appear on the same event, Screeb aliases them to one respondent, so a visitor who logs in keeps a single profile. Screeb never moves an id from one respondent to another, and it does not read your CDP's identifiers from your app: keeping the two tools on the same identifiers is part of your instrumentation. Three rules do it.

1. One user id, the same string everywhere​

Identify the user in Screeb with exactly the value you give your CDP's identify: a stable internal id rather than an email, which can change. Do it in the same place in your code so neither tool lags behind the other.

Screeb.setIdentity(uniqueVisitorId: userId)

Amplitude drops user ids and device ids shorter than 5 characters, and the event then reaches Screeb as anonymous: use ids of 5 characters or more.

2. Give your CDP the Screeb anonymous id​

Before login, CDP events carry only the CDP's own anonymous id, which is not the Screeb respondent the SDK displays surveys for. Read the Screeb anonymous id and hand it to your CDP as its anonymous or device id; the Screeb respondent id is one of its own aliases, so nothing else is needed on the Screeb side.

Screeb.getIdentity { identity, _ in
    guard let anonymousId = identity?["anonymous_id"] as? String else { return }
    // give anonymousId to your CDP, e.g. amplitude.setDeviceId(anonymousId)
}

Do this before the CDP sends its first event, using the device or anonymous id setter of your CDP's mobile SDK (setDeviceId for Amplitude; see your CDP's documentation for Segment and RudderStack). Server-side events must carry the same ids, forwarded from the app.

Without this rule, anonymous visitors exist twice (one respondent per tool) and surveys triggered by CDP events cannot display for them.

3. Reset both tools together on logout​

Reset Screeb, read the new anonymous id, then reset your CDP and give it that id, in this order. Reset once, on logout only: resetting on every anonymous screen creates a new respondent each time on both sides.

Screeb.resetIdentity()

Then repeat rule 2 with your CDP's reset.

What the "ignore anonymous users" settings change​

The integration's "ignore events from anonymous users" option and the workspace-level "Ignore anonymous users" setting drop CDP events that carry no user id. Rule 2 needs both off to cover the pre-login window. An event carrying a user id is never dropped by them, so the login-time merge happens either way.

Check it works​

Read the current identity and compare anonymous_id and user_id with what your CDP reports for the same visitor. In Screeb, the respondent page then lists both ids among its aliases, and a survey targeted on a CDP event displays a few seconds after the event.