User Sign-In & Registration

The authenticated, registeredAccount and updatedUserInfo events help Brytelytics understand who your users are by providing their contact information and associated user account data. It is important to capture all of these events when they happen in your system in order to provide the lead contact information to the Brytecore platform, which in turn provides this information to the assigned agent(s).

Capture one registeredAccount event

The API expects a user only registers a single time over the lifecycle of an application. Therefore, only use the registeredAccount event when the user actually creates their user account. Do not use it for user login events.

Since registeredAccount is a "Lead Creation Event" Brytecore will attempt to create a new lead every time the event is received. The system will not create duplicate leads, but it will merge the event into the existing lead and will trigger any automations that depend on it.

Capture authenticated on sign-in

The API expects many authenticated events over a user's lifecycle. Best practice is to trigger the authenticated event every time a user signs into a new credentialed session. It is perfectly fine to have a sessionStarted event followed by an authenticated event.

Capture user information changes

When a user changes their information in your system, such as first and last name, email address, or telephone number, make sure to trigger the updatedUserInfo event to keep the user data synced with the Brytecore platform.