User Identification

Identifying users is how you connect the people using your app to the targeting and personalization features in Setgreet. Once a user is identified, you can target them with flows based on their attributes, personalize content with their data, and track their behavior across sessions.

The identifyUser call

The identifyUser method sets the current user's ID and optional attributes. Call it whenever you know who the user is -- typically after login or signup.

// iOS
Setgreet.shared.identifyUser(userId: "user_123", attributes: [
    "email": "jane@acme.com",
    "plan": "pro",
    "signupDate": "2026-01-15"
])

// Android
Setgreet.identifyUser("user_123", mapOf(
    "email" to "jane@acme.com",
    "plan" to "pro",
    "signupDate" to "2026-01-15"
))

// React Native
import { identifyUser } from '@setgreet/react-native-sdk';

identifyUser('user_123', {
  email: 'jane@acme.com',
  plan: 'pro',
  signupDate: '2026-01-15',
});

// Flutter
await Setgreet.identifyUser(
  userId: "user_123",
  attributes: {
    "email": "jane@acme.com",
    "plan": "pro",
    "signupDate": "2026-01-15",
  },
);

The userId should be a stable, unique identifier from your system -- the same ID you use in your database or authentication provider. Do not use ephemeral identifiers like session tokens.

Anonymous users

Before identifyUser is called, the SDK assigns an auto-generated anonymous ID to the device. This allows Setgreet to:

Display flows that do not require user targeting (for example, a generic welcome screen).
Track flow analytics for unidentified users.
Associate pre-identification behavior with the user once identifyUser is called.

The anonymous ID is a UUID stored on the device and persists across app launches until resetUser is called.

Every SDK exposes the anonymous ID if you need it for server-side correlation:

// iOS
let anonId = Setgreet.shared.anonymousId

// Android
val anonId = Setgreet.anonymousId

// React Native
import { getAnonymousId } from '@setgreet/react-native-sdk';

const anonId = getAnonymousId();

// Flutter
final anonId = await Setgreet.anonymousId;

In React Native, getAnonymousId works on iOS from React Native SDK 1.7.0.

Updating attributes

You can call identifyUser multiple times with the same userId to update attributes. By default each call merges the new attributes with the existing ones rather than replacing the full set. An optional operation parameter (create or update) lets you control this explicitly.

// Update a single attribute after a plan change
Setgreet.shared.identifyUser(userId: "user_123", attributes: [
    "plan": "enterprise"
])

This is useful for keeping Setgreet in sync when user properties change mid-session (for example, after a plan upgrade or a profile update). If a flow should reflect the change, see Identify before showing a flow.

Reset

Call resetUser when the user logs out. This clears the identified user and generates a new anonymous ID.

// iOS
Setgreet.shared.resetUser()

// Android
Setgreet.resetUser()

// React Native
import { resetUser } from '@setgreet/react-native-sdk';

resetUser();

// Flutter
Setgreet.resetUser();

After resetUser, the SDK behaves as if it is a fresh, unidentified device. Call identifyUser again when the next user logs in.

Always call resetUser on logout. If you skip this step and a second user logs in on the same device, flows may be shown based on the previous user's attributes.

When to identify

Moment	Why
After login	The most common place. You know the user ID and can pass current attributes.
After signup	Identify the user immediately after account creation so onboarding flows can be personalized.
When attributes change	Call `identifyUser` again with updated attributes so trigger conditions, Condition nodes, and variable bindings reflect the latest data.
On app launch (if already authenticated)	If the user is still logged in from a previous session, re-identify on launch to ensure the SDK has fresh attributes.

Identify before showing a flow

Trigger conditions and Condition nodes are decided on Setgreet's servers from the attributes stored for the user at the moment the flow is requested. Call identifyUser before showFlow, so the flow is decided for the right user with their latest attributes. A flow that the identifyUser call itself brings up is decided with the attributes from that call.

On SDK versions up to 1.3.0, identifyUser sends its update in the background and returns before Setgreet has stored the attributes. A showFlow or trackEvent called right after it can reach Setgreet first and be decided on the attributes stored before that call. That can mean the previous or anonymous user. It also applies when you call identifyUser again for the same user to update attributes: a flow shown right after a plan upgrade can still be decided with the old plan. Identify at login or on app launch, and send attribute updates when the data changes, not in the same moment as the call that shows the flow. Later SDK versions wait for a pending identifyUser before these calls, but only for a short time, so an identifyUser that takes longer than that can still arrive after them.

What counts as an MAU

Each unique userId (or anonymous ID if the user is not identified) that triggers at least one SDK request during a billing period counts as one Monthly Active User (MAU) for billing purposes. Calling identifyUser itself does not consume additional MAU -- the user is counted once per billing period regardless of how many times identifyUser is called.

User Identification

On this page