Skip to main content

🔐 User identity

The Gleap identify call lets you tie a user to their feedback items. It includes a unique User ID and optional meta information such as email & name.

Identify your users

To effectively manage your contacts, we advise using Gleap.identify() each time a user signs in or registers. This practice ensures accurate identification of your contacts from the outset. Additionally, for scenarios where contact information needs to be updated during active usage – such as when a user subscribes to a new plan or modifies their existing data – we recommend utilizing Gleap.updateContact(). This method allows for seamless real-time updates to contact details.

Identify your user by calling the following method.

Gleap.identify(
userId: '12345',
userProperties: GleapUserProperty(
name: 'Franz',
email: '[email protected]',
phone: '+1 (902) 123123',
companyName: 'ACME inc.',
companyId: '19283',
plan: 'Pro plan',
value: 199.95,
customData: <String, dynamic>{
'key1': 'Test',
'key2': 'ACME',
},
),
);
info

When transmitting custom data, only primitive numeric and string values are supported for later use in segment filters. Please note that you can send only 15 custom data keys with an identify call.

info

Gleap defaults to guest sessions when feedback items get reported without calling the identify method first. All feedback items of an existing guest session are merged with the user session once you've identified it.

Enforce identity verification

Enforce identity verification to prevent third parties from impersonating logged-in users. Get started here.

Gleap.identify(
userId: '12345',
userProperties: GleapUserProperty(
name: 'Franz',
email: '[email protected]',
phone: '+1 (902) 123123',
companyName: 'ACME inc.',
companyId: '19283',
plan: 'Pro plan',
value: 199.95,
customData: <String, dynamic>{
'key1': 'Test',
'key2': 'ACME',
},
),
userHash: 'GENERATED_USER_HASH'
);

Update contact properties

To effectively manage your contacts, we advise using Gleap.identify() each time a user signs in or registers. This practice ensures accurate identification of your contacts from the outset. Additionally, for scenarios where contact information needs to be updated during active usage – such as when a user subscribes to a new plan or modifies their existing data – we recommend utilizing Gleap.updateContact(). This method allows for seamless real-time updates to contact details.

Gleap.updateContact(
userProperties: GleapUserProperty(
plan: 'Pro plan',
value: 199.95,
),
);

The updateContact method takes in the same contact parameters as the identify method. Partial updates are possible.

Gleap.updateContact(
userProperties: GleapUserProperty(
name: 'Franz',
email: '[email protected]',
phone: '+1 (902) 123123',
companyName: 'ACME inc.',
companyId: '19283',
plan: 'Pro plan',
value: 199.95,
customData: <String, dynamic>{
'key1': 'Test',
'key2': 'ACME',
},
),
);

Clear the identity on logout

We recommend to clear the identity once the user logs out. Clearing the identity will automatically detach the current session and create a new guest session.

Gleap.clearIdentity();

Get the identification status of a user

With the following method, you can get the status of the current user identity.

Gleap.isUserIdentified();

Get the current user identity

With the following method, you can get the current user identity.

Gleap.getIdentity();