SDK Users

The Applivery SDK creates and tracks user records automatically for every device that runs an app with the SDK integrated. These records appear in the Applivery Dashboard and allow you to get insights into who installs your apps, who reports feedback, and how builds are adopted across your user base.

SDK users come in two types depending on how they originate: SDK users (bound, named identities) and Temporal SDK users (anonymous, device-based). Both count as employees against your workspace's employee limit.

Types of SDK Users

SDK Users (Bound)

When you call bindUser() with an email address, Applivery links the current device session to a named identity. This allows you to:

• See who downloaded or installed each build.
• Attribute feedback reports and bug submissions to a specific person.
• Track update adoption per named user.
• Control app access by user identity when authentication enforcement is enabled.

Bound users appear with their email address in the Applivery Dashboard, making it easy to correlate SDK activity with your own user base.

Temporal SDK Users (Anonymous)

When a device runs the SDK for the first time without a bindUser() call, Applivery automatically creates a Temporal SDK User record identified by the device's unique ID. These records allow basic device-level analytics (installations, update adoption) even when no named identity is available.

Temporal SDK users expire after 30 days of inactivity. If the same device opens the app again after expiry, a new Temporal SDK User record is created.

Binding a User

Call bindUser after your app's own authentication flow completes, so the identity is known before any Applivery interactions occur.

AppliverySDK.shared.bindUser(
    email: "[email protected]",   // Required
    firstName: "Jane",           // Optional
    lastName: "Doe",             // Optional
    tags: ["beta", "ios-team"]   // Optional — used for filtering in the Dashboard
) {
    // onComplete callback — called when binding is confirmed
}

[[AppliverySDK shared] bindUserWithEmail:@"[email protected]"
                               firstName:@"Jane"
                                lastName:@"Doe"
                                    tags:@[@"beta", @"ios-team"]
                               onComplete:nil];

Applivery.getInstance().bindUser(
    email = "[email protected]",
    firstName = "Jane",
    lastName = "Doe",
    tags = listOf("beta", "android-team")
)

bindUser parameters

Unbinding a user

Call unbindUser when your app's user logs out, so subsequent SDK interactions are no longer attributed to that identity.

AppliverySDK.shared.unbindUser {
    // onComplete callback
}

[[AppliverySDK shared] unbindUserWithOnComplete:nil];

Applivery.getInstance().unbindUser()

Retrieving the current user

You can read back the currently bound user's profile at any point:

AppliverySDK.shared.getUser { userInfo in
    // userInfo is an NSDictionary, or nil if no user is bound
    print(userInfo ?? "No user bound")
}

Applivery.getInstance().getUser(object : GetUserCallback {
    override fun onSuccess(user: AppliveryUser?) {
        // user is null if no user is bound
    }
    override fun onError(error: Throwable) { /* handle */ }
})

Authentication enforcement

If your publication requires users to log in before accessing the app, you can enforce this at the SDK level. When enforceAuthentication is set to true in the SDK configuration, users must authenticate via Applivery (or your workspace's SSO) before the app becomes usable.

let config = AppliveryConfiguration(
    enforceAuthentication: true
)
AppliverySDK.shared.start(token: "YOUR_TOKEN", configuration: config)

val config = Configuration(
    enforceAuthentication = true
)
Applivery.start(APPLIVERY_TOKEN, configuration = config)

User visibility in the Dashboard

SDK users are visible per app in the Applivery Dashboard or in the Directory section under the Settings menu. For each user, you can see:

• Email address and display name (for bound users).
• Tags assigned via bindUser.
• Devices associated with the user.
• Download history — which builds were installed.
• Feedback submissions attributed to the user.

Anonymous users appear with a device identifier rather than an email address.

SDK users vs. other user types

Applivery has several distinct user types. Understanding the differences helps avoid confusion:

SDK users are the only type created programmatically from within the app itself. All other types are managed through the Applivery Dashboard or API.