Account events

Account events capture the activities of customer accounts and administrative users

Account events

Overview

Account events capture the activities of customer accounts and administrative users. Each account event is made up of phases that

  • tell what has happened during a user's session,
  • contain blocks that let you know what went down on the application's side,
  • and are given labels to let you know the outcome of customer journey points.
Admin account events

Phases

Phases are activities that are initiated by the user or the system. A phase starts and finishes and contains blocks and API calls. You will see the start of the phase and the result of the phase on the same line.

A flow is a string of phases that happen within each other.

Blocks

Blocks and API calls/responses make up the contents of a phase. Blocks represent what is happening with the application you created. The blocks talk with the API's to decide the outcome of the phase. You will see the action and the outcome of each block on the same line.

Labels

Labels are given when a user has passed through each journey point. The labels are either green for pass, or red for fail.

📘

Strivacity will store up to 30 days of account events by default. Additional storage durations are available on request.

Account activity

Phases

NameDescriptionOutcome nameOutcome description
Account activation started (accountActivation)The account activation phase has started.
Account activation required (accountActivationRequired)Account activation is required to continue.
Account activation finished (accountRegistrationFinish)The account activation phase has finished.Account has been registered and activated (account_registered_and_activated)The account has been registered and activated.

Blocks

NameDescriptionOutcome nameOutcome description
Login accepted (acceptLogin)When a user logs into an application and the login is accepted.
Send account activation (sendAccountActivation)Account activation has been triggered.
  • Email sent (emailSent)
An account activation link was sent via email.
Account activated (accountActivation)An account has been created and successfully activated.
Account registration finished (accountRegistrationFinish)The registration process for the account has finished.
  • Account activation required (activationRequired)
  • Identified (identified)
  • The account needs activation in order to be completed.
  • Account registration complete.
Account remembered (rememberedAccount)The account has been remembered.
  • Deleted (deleted)
  • The account was deleted.
Reset (reset)The account has been reset.

Labels

NameDescription
Account activation (success:account_activation, failure:account_activation)The account activation was either successful or failed.
Account enabled (success:account_enable)The account was successfully enabled.
Account verification invalidated (success:invalidate_account_proofing)Account verification was successfully invalidated.
Account verification invalidated (success:invalidate_account_proofing)Account verification was successfully invalidated.
Account created (success:account_creation)The account was created successfully.
Account disabled (success:account_disable)The account was disabled successfully.
Account deleted (success:account_deletion)The account was deleted successfully.
Account updated (success:account_update)The account was updated successfully.

Document verification

Phases

NameDescriptionOutcome nameOutcome description
Document verification started (documentVerificationPreparation)Document verification phase has started.
  • Prepared on smart device (smartDevice)
  • Prepared on PC (verificationUrlCreated)
  • Document verification is being prepared on a smart device.
  • The document verification is being prepared on a PC.

Document verification retrieval started(documentVerificationRetrieve)The document verification retrieval phase has started.
  • Exit (exit)
  • Next (next)
  • The phase exited.
  • The phase proceeded to the next step.
Step: Document verification on smart device (documentVerificationSessionFlow)Documentation verification flow will be done via smart phone.
Document identifier selection started (documentVerificationSessionIdentifierSelect)The document identifier selection phase has started.
  • Identifier selected (typeSelected)
  • The document identifier has been selected.
Document verification processing started (documentVerificationSessionProcessing)The document verification process phase has started.
  • Failed (failed)
  • Passed (passed)
  • Verification recaptured (recapture)
  • The document verification process failed.
  • The document verification process passed.
  • The document verification process needs to be recaptured.
Document scanned (documentVerificationSessionScan)The document for verification has been scanned.

  • Failed (failed)
  • Scanned (scanned)
  • Identifier selected (typeSelected)
  • The scan failed.
  • The scan was successful.
  • An identifier was selected.
Document verification selfie session started (documentVerificationSessionSelfie)The session in which the user takes a selfie for verification has started.
  • Captured (captured)
  • The selfie was captured for verification.
Document verification started (documentVerificationStart)The document verification phase has started.
  • Exit (exit)
  • Next (next)
  • Link clicked (verificationUrlClicked)
  • Link sent (verificationUrlSent)
  • The flow has exited.
  • The flow has moved onto the next part.
  • A verification link has been clicked.
  • A verification link has been sent.
Step: Document verification started on PC (documentVerificationSubFlow)Document verification flow has started on PC
Document verification link sent (documentVerificationTargetVerify)Document verification target link has been sent.

  • Exit (exit)
  • Next (next)
  • Link clicked (verificationUrlClicked)
  • Link resent (verificationUrlResent)
  • Exited the flow.
  • The session has moved onto the next step.
  • Verification link clicked.
  • Verification link resent.

Blocks

NameDescriptionOutcome nameOutcome description
Document verification preparation (documentVerificationPreparation)The document verification is being prepared to initiate via smart device or a URL.
  • Prepared on smart device (onSmartDevice)
  • URL created (urlCreated)
  • The document verification was prepared on a smart device
  • The document verification was prepared using a URL.
Document verification retrieved (documentVerificationRetrieve)The document verification information was retrieved.
  • Failed (failed)
  • Verification in progress (inProgress)
  • Success (success)
  • The retrieval rendered a failure.
  • The verification is in progress.
  • The retrieval rendered a success.
Document identifier selected (documentVerificationSessionIdentifierSelect)The document verification identifier has been selected.
  • Identifier selected (selectedType)
  • Identifier was selected as the document identifier selection type.
Document verification session processed (documentVerificationSessionProcessing)The document verification session was processed.

  • Failed (failed)
  • Passed (passed)
  • Verification recaptured (recapture)

  • The document verification failed.
  • The document verification passed.
  • The document verification needs recaptured.
Document scanned (documentVerificationSessionScan)The document has been scanned.
  • Failed (failed)
  • Scanned (scanned)
  • Document scan failed.
  • Document scan was successful.
Selfie captured (documentVerificationSessionSelfie)The document verification selfie was captured.
  • Captured (captured)
  • Failed (failed)
  • Selfie capture was successful.
  • Selfie capture failed.
Document verification started (documentVerificationStart)Document verification has started
  • Link clicked (clicked)
  • Link expired (expired)
  • Link not clicked (notClicked)
  • The link was clicked.
  • The link exceeded the allotted amount of time.
  • The link was not clicked.
Document verification target select started (documentVerificationTargetSelect)The document verification target select was started.
  • Link sent (urlSent)
  • The link was sent.
Document verification link sent (documentVerificationTargetVerify)The document verification link was sent.

  • Link clicked (clicked)
  • Link expired (expired)
  • Link not clicked (notClicked)

  • The link was clicked.
  • The link exceeded the allotted amount of time.
  • The link was not clicked.
NameDescription

Document verification (success:document_base_verification
failure:document_base_verification)

The document verification was either successful or failed.

Identity verification

Phases

NameDescriptionOutcome nameOutcome description
Identification started (Identification)An identification phase has started.
  • Account activation required (account_activation_required)
  • Account registered (account_registered)
  • Registered external login provider (external_login_provider_registration)
  • Identified (identified)
  • External provider identified (external_login_provider_registration)
  • Account activation is required.
  • The account was successfully registered.
  • An external login provider has been used to register.
  • The account has been identified.
  • The external provider has been identified.
Step: Identity verification login (identityProofingLoginFlow)The identity verification login flow has started.
  • Finished (finished)
The flow has finished.
Identity verification selection started (identityProofingSelectPhase)
  • Exit (exit)
  • Next (next)

  • The phase exited.
  • The phase proceeded to the next step.
Identity verification started (identityProofingStartPhase)The identity verification phase has started.
  • Already verified already_proofed)
  • Blocked (blocked)
  • Next (next)
  • The user is already verified.
  • The user has been blocked.
  • The phase proceeded to the next step.
Step: Identity registration verification (identityRegistrationProofingFlow)The identity registration verification flow has started.Finished (finished)The flow has finished.
Post id verification started (postIdProofing)The post id verification phase has started.
  • Exit (exit)
  • The phase has exited.
Pre-authenticator (preAuthenticator)The pre-authenticator phase has started.Authenticated (authenticate)The pre-authenticator has been authenticated.
Pre-id verification started (preIDProofing)The pre-id verification phase has started.
  • Next (next)
  • The phase proceeded to the next step.
Verification notification started (proofingNotification)The verification notification phase has started.
  • Next (next)
  • The phase proceeded to the next step.

Blocks

NameDescriptionOutcome nameOutcome description
Fast path identification assessment (fastPathIdentification)Fast path identification has started it's assessment.
  • Display (display)
  • Identify (identify)
  • The users information is present.
  • The user needs to be identified.
Identifier assessment (identifier)A user is trying to access their account from the identifier screen.
  • Activation is required (activationRequired)
  • Identified (identified)
  • Rejected (rejected)
  • Rendered (render)
  • Activation is required to access the account.
  • The user was identified.
  • The user was rejected.
  • The user was rendered.
Post id verification assessment (postIdProofing)Post ID verification is being assessed
  • Rejected (rejected)
  • Success (success)
  • The ID verification was rejected.
  • The ID verification was successful.
Post identification assessment (postIdentification)Post identification is being assessed.
  • Allowed (allowed)
  • Rejected (rejected)
  • Show error (showError)
  • The identification was allowed.
  • The identification was rejected.
  • An error occurred.
Pre-authentication assessment (preAuthenticator)The pre-authentication is being assessed.
  • Usable authenticators (usableAuthenticators)
  • The authenticators are usable.
Pre-id verification assessment (preIDProofingBlock)Pre-id verification is being assessed.

  • Rejected (rejected)
  • Success (success)

  • The ID verification was rejected.
  • The ID verification was successful.
Pre-id token generation assessment (preIdTokenGeneration)Pre-id token generation is being assessed.
  • Pre-id token claims (preIdTokenClaims)
  • Rejected (rejected)
  • Pre-id token claims
  • id-token generation was rejected.
Pre-verification notification assessment (preProofingNotificationBlock)Pre-verification notification is being assessed.
  • Verification notification needed (proofingNotificationNeeded)
  • Verification notification not needed (proofingNotificationNotNeeded)
  • Verification notification is needed.
  • Verification notification is not needed.
Verification data (proofingData)Verification data has been collected.
  • Failed (failed)
  • Success (success)
  • The verification failed.
  • The verification was successful.
Verification notification (proofingNotification)Verification notification has been collected.
  • Success (success)
  • Verification notification was successful.

Labels

NameDescription

Data input verified (success:proofing_data_input
failure:proofing_data_input)

Data input verification was either successful or failed.
Delete failed account verification (success:delete_failed_account_proofing)Failed account verification was successfully deleted.

Identification (success:identification
failure:identification)

The identification process was either successful or failed.

Identity verification (success:identity_proofing
failure:identity_proofing)

The identity verification process was either successful or failed.

Knowledge-Based Verification

Phases

NameDescriptionOutcome nameOutcome description
Knowledge-based verification started (knowledgeBasedVerification)Knowledge-based verification phase has started.
  • Exit (exit)
  • Next (next)
  • The phase has exited.
  • The phase proceeded to the next step.

Blocks

NameDescriptionOutcome nameOutcome description
Knowledge-based verification assessment (knowledgeBasedVerification)The user has entered a knowledge-based verification exam.
  • Failed (failure)
  • Success (success)
  • The user failed the KBV exam.
  • The user passed the KBV exam.

Labels

NameDescription

Knowledge-based verification (success:knowledge_base_verification
failure:knowledge_base_verification)

The KBV process was either successful or failed.

Miscellaneous

Phases

NameDescriptionOutcome nameOutcome description
Initializing (preInit)Every event starts with this phase. This phase calls to the api to access the login screen.
Rendered (render)The flow hasn't moved forward despite the user entering into the journey point e.g. the user entered their password, but it wasn't correct, and couldn't move to the next phase.
Subflow rejected (subflowReject)The subflow has been rejected.
Block (block)Blocks and API calls/responses make up the contents of a phase. Blocks represent what is happening with the application you created. The blocks talk with the API's to decide the outcome of the phase. You will see the action and the outcome of each block on the same line.
Exit (exit)When a phase has exited the flow.Finished (finished)When a phase has finished a flow.
Finish (finish)When the entire event has been completed.

Blocks

NameDescriptionOutcome nameOutcome description
Generic result (genericResult)When a user triggers an action in the flow and there's some kind of approval needed (depending on the context) to continue.Action (action)Represents the approval for continuing.
Assessing claims (calculateClaims)When the requested account metadata properties are being assembled to be handed over to the client application (brand portal) after the user has successfully authenticated.Claims calculated (claimsCalculated)Requested account metadata has been prepared to be handed over to the client application.
Canceled (cancel)The action was canceled.Claims session canceled (cancelSession)The claims session was canceled.

Labels

NameDescription
Redirected (success:redirect)The redirection was successful.
Third party (failure:third_party)The system could not reach the third party.
Flow abandoned (failure:abandoned)The flow has been abandoned.
Current sessions deleted (success:delete_current_sessions)The current session was successfully deleted.
Session deleted (success:delete_session)The session was deleted successfully.
Consent update (success:consent_update, failure:consent_update)The consent update in the self-service account was either successful or failed.
Data downloaded (success:download_data)The data was downloaded successfully from the self-service account.

Multi-factor authentication

Phases

NameDescriptionOutcome nameOutcome description
Multi-factor authentication started (mfaChallengeSubflow)The multi-factor authentication phase has started.
  • MFA skipped (skipped)
  • MFA not available (notAvailable)
  • Finished (finished)
  • MFA has been skipped.
  • MFA not available for the user to go through.
  • The multi-factor authentication phase has finished.
External Multi-factor authentication started (externalLoginMFAChallengeSubflow)Multi-factor authentication phase for external login provider has started.

  • MFA skipped (skipped)
  • MFA not available (notAvailable)
  • Finished (finished)

  • MFA has been skipped.
  • An MFA is not available.
  • The multi-factor authentication phase has finished.
MFA selection started (mfaSelection)The MFA selection phase has started.
  • MFA chosen (mfaChosen)
  • MFA skipped (mfaSkip)
  • MFA not available (mfaNotAvailable)
  • An MFA method is chosen.
  • MFA has been skipped.
  • MFA is not available.
MFA challenge started (mfaChallenge)MFA challenge started.
  • MFA authenticated (mfaAuthenticated)
  • The MFA has been authenticated.
Blocked by rule (blockedByRule)Blocked by rule set up in Adaptive Rules.

Blocks

NameDescriptionOutcome nameOutcome description
Pre-MFA (preMfa)The need for MFA is being evaluated.
  • MFA needed (mfaNeeded)
  • MFA valid (validMFA)
  • MFA not available (notAvailable)
  • MFA is needed to continue.
  • MFA is valid.
  • MFA is not available.
MFA method assessment (mfaMethod)The MFA method is being assessed.
  • MFA chosen (chosenMFA)
An MFA method has been chosen.
MFA passcode (mfaPasscode)The user has chosen MFA via passcode.
  • Passcode valid (validPasscode)
  • Rejected (rejected)
  • The passcode was successful.
  • The passcode was rejected.
Magic link sent (magicLink)A magic link was sent for authentication.
  • Magic link accepted (magicLinkAccepted)
  • Magic link expired (magicLinkExpired)
  • Magic link rejected (rejected)
  • Magic link not clicked (magicLinkNotClicked)
  • The magic link was accepted.
  • The magic link expired.
  • The magic link was rejected.
  • The magic link was not clicked.
MFA soft token assessment (mfaEnrollSoftToken)The MFA soft token method is being assessed.
  • Valid (valid)
  • Rejected (rejected)
  • The MFA method was accepted.
  • The MFA method was rejected.
MFA web authentication assertion started (mfaWebAuthnAssertion)MFA enrollment via web authentication has started.
  • Authenticator valid (validAuthenticator)
  • Rejected (rejected)
  • The method was authenticated and successful.
  • The method was rejected.
Adaptive rule initiated (adaptiveRule)An adaptive rule has been triggered.
  • Step up initiated (stepUp)
  • Step down initiated (stepDown)
  • Block (block)
  • No operation occurred (noop)
  • The user was stepped up.
  • The user was stepped down.
  • The user was blocked.
  • No adaptive rule triggered.

Labels

NameDescription
MFA authentication (success:mfa_authentication, failure:mfa_authentication)The MFA authentication process was either successful or failed.

Multi-factor authentication enrollment

Phases

NameDescriptionOutcome nameOutcome description
Step: MFA enrollment registration (mfaEnrollRegistrationFlow)MFA enrollment has started during the registration flow.Finished (finished)The flow has finished.
Step: MFA enrollment login (mfaEnrollLoginFlow)MFA enrollment has started during the login flow.Finished (finished)The flow has finished.
MFA enrollment started (mfaEnrollStart)MFA enrollment phase has started.
  • Skip enrollment (skipEnroll)
  • Enrollment types selected (typesSelected)
  • Enrollment has been skipped.
  • Enrollment type has been selected.
MFA enrollment selection started (mfaEnrollSelect)MFA enrollment selection phase has started.
  • All enrolled (allEnolled)
  • Enrollment types selected (typesSelected)
  • Different method selected (selectDifferentMethod)
  • Soft token selected (softTokenSelected)
  • Web authentication selected (webAuthnSelected)
  • All methods are enrolled.
  • Enrollment types have been selected.
  • A different method has been selected.
  • Soft token has been selected for MFA enrollment.
  • Web authentication has been selected for MFA enrollment.
MFA enrollment challenge started (mfaEnrollChallenge)MFA enrollment challenge phase started.
  • Different method selected (selectDifferentMethod)
  • Authenticator valid (validAuthenticator)
  • A different MFA method has been selected.
  • The authenticator is valid.
MFA enrollment soft token started (mfaEnrollSoftToken)MFA enrollment soft token phase has started.

  • Different method selected (selectDifferentMethod)
  • Authenticator valid (validAuthenticator)
  • A different MFA method has been selected.
  • Soft Token has been validated for MFA enrollment.
MFA enrollment web authentication (mfaEnrollWebAuthn)The MFA enrollment web authentication phase has started.

  • Different method selected (selectDifferentMethod)
  • Authenticator valid (validAuthenticator)

  • A different MFA method has been selected.
  • Web authentication has been validated for MFA enrollment.

Blocks

NameDescriptionOutcome nameOutcome description
Pre-MFA enrollment started (preMFAEnrollStart)Pre-MFA enrollment has started.
  • Enrollment needed (enrollNeeded)
  • Skipped (skip)
  • Enrollment is needed.
  • Enrollment was skipped.
MFA enrollment started (mfaEnrollStart)The MFA enrollment process has started.MFA enrollment types (chosenTypes)The user was given different types of MFA enrollment methods to choose from.
Pre-MFA target selection assessment (preMFATargetSelect)Pre-MFA target selection is being assessed.
  • All enrolled (allEnrolled)
  • Next type (nextType)
  • All MFA target selections are enrolled.
  • Next type.
MFA enrollment target select started (mfaEnrollTargetSelect)The MFA enrollment target select has startedMFA target selected (targetSelected)The MFA target has been selected.
MFA enrollment challenge (mfaEnrollChallenge)The selected method of MFA has started (eg. biometric, SMS, phone call, email).
  • Valid (valid)
  • Rejected (rejected)
  • The MFA method was accepted.
  • The MFA method was rejected.
MFA enrollment web authentication assessment (mfaEnrollWebAuthn)MFA enrollment via web authentication is being assessed.
  • Valid (valid)
  • Rejected (rejected)
  • The MFA enrollment was successful.
  • The MFA enrollment was rejected.

Labels

NameDescription
MFA enrolled (success:mfa_enrollment, failure:mfa_enrollment)MFA enrollment was either successful or failed.
MFA update (success:mfa_update, failure:mfa_update)Updating the MFA was either successful or failed.
MFA disenrolled (success:mfa_disenrollment)MFA disenrolled successfully.

Password authentication

Phases

NameDescriptionOutcome nameOutcome description
Password enrollment started (passwordEnroll)The password enrollment phase has started.Continue (continue)The password was a success and the phase proceeded to the next step.
Password started (password)The password phase has started.
  • Authenticated (authenticated)
  • Password reset by phone (password_reset_by_phone)
  • Password skipped (passwordSkip)
  • The password was authenticated.
  • The password has been reset by phone.
  • The password was skipped.
Password reset initiated (passwordReset)The password reset phase has been initiated.
Password reset by phone passcode (passwordResetPhonePasscode)The user has selected reset by phone passcode.Password reset allowed (password_reset_allowed)The password reset is allowed.

Blocks

NameDescriptionOutcome nameOutcome description
Pre-password (prePassword)The need for a password is being evaluated.
  • Password needed (passwordIsNeeded)
  • Password not needed (passwordIsNotNeeded)
  • A password is needed to continue.
  • The password is not needed to continue.
Password enrollment assessment (passwordEnroll)Enrollment via password is being assessed.Password enrolled (passwordEnrolled)
Password assessment (password)The password is being assessed.
  • Hook authenticated (hookAuthenticated)
  • Password authenticated (passwordAuthenticated)
  • Password authenticator created (passwordAuthenticatorCreated)
  • Rejected (rejected)
  • The hook was authenticated.
  • The password was authenticated.
  • The password authenticator was created.
  • The password was rejected.
Password reset (passwordReset)Enrollment via password is being assessed.
Forgotten password email triggered (forgottenPasswordEmail)A user clicked "forgot password" and chose email as their method of receiving the link.Magic link sent (magicLinkSent)A magic link has been sent to the user to reset their password.
Forgotten password phone triggered (forgottenPasswordPhone)A user clicked "forgot password" and chose phone as their method of receiving the passcode.Passcode sent (passcodeSent)A passcode has been sent to the user to reset their password.

Labels

NameDescription
Password authentication (success:password_authentication, failure:password_authentication)Password authentication was either successful or failed.
Password reset (success:password_reset, failure:password_reset)Resetting the password was either successful or failed.
Forgotten password requested (success:forgotten_password_request)The forgotten password request was successful.
Password changed (success:password_change)The password was successfully changed.

Phone-based Identity Verification

Phases

NameDescriptionOutcome nameOutcome description
Phone based identity verification started (phoneBasedIdentityAffirmation)The phone based identity verification phase has started.
  • Exit (exit)
  • Next (next)
  • The phase has exited.
  • The phase proceeded to the next step.
Phone number risk evaluation started (phoneNumberRiskEvaluation)The phone number risk evaluation phase has started.

  • Exit (exit)
  • Next (next)

  • The phase has exited.
  • The phase proceeded to the next step.

Blocks

NameDescriptionOutcome nameOutcome description
Phone record match (phoneBasedIdentityAffirmation)Phone based identity verification is being assessed.
  • Fail (fail)
  • Success (success)
  • The phone based identity verification failed.
  • The phone based identity verification was successful.
Phone number risk assessment (phoneNumberRiskEvaluation)The phone number risk evaluation is being assessed.

  • Fail (fail)
  • Success (success)
  • The phone number risk evaluation failed.
  • The phone number risk evaluation was successful.

Labels

NameDescriptionReason of failure

Phone-based identity verification {success:phone_based_identity_affirmation
failure:phone_based_identity_affirmation}

The phone-based identity verification process was either successful or failed.
  • missingPhoneNumber
    The user didn't provide a phone number or the wrong native claim was used.
  • missingConsent For some reason, user consent for the verification process wasn't provided or collected. The verification flow should never complete without gathering consent either explicitly or implicitly.
  • violation
    The name or address provided by the user does not match the expected threshold or the values are missing.

Phone risk evaluation {success:phone_risk_evaluation
failure:phone_risk_evaluation}

The phone risk evaluation process was either successful or failed.
  • allConfiguredAsRisky All of the phone types available in the phone risk evaluation setup are configured as a risk signal. None of the phone types used by a customer can possibly pass the evaluation.
  • forbiddenType
    The user’s detected phone type is not allowed. It’s considered a risk signal by the phone risk evaluation setup. Also contains further information that marks the exact phone type that's considered a risk signal: mobile, landLine, fixedVoip, nonFixedVoip, other
  • missingConsent For some reason, user consent for the verification process wasn't provided or collected. The verification flow should never complete without gathering consent either explicitly or implicitly.
  • missingPhoneNumber
    The user didn't provide a phone number or the wrong native claim was used.
  • nonForbidden None of the available phone types are configured as risk signals in the phone risk evaluation setup.
  • simChangeDetected
    The SIM card and subscriber phone number pairing has recently changed.
  • unsupportedPhoneNumber
    The line type detection returns, but without a phone type. (The phoneType response is null.)

Progressive profiling

Phases

NameDescriptionOutcome nameOutcome description
Step: Progressive profiling registration (progressiveProfilingRegistrationFlow)The progressive profiling registration flow has started.
  • Finished (finished)
  • The flow has finished.
Step: Progressive profiling login (progressiveProfilingLoginFlow)The progressive profiling login flow has started.
  • Finished (finished)
  • The flow has finished.
Progressive profiling started (progressiveProfiling)The progressive profiling phase has started.
  • Profiling completed (profilingCompleted)
  • The profiling phase is complete.

Blocks

NameDescriptionOutcome nameOutcome description
Pre-progressive profiling assessment (preProgressiveProfiling)Pre-progressive profiling is being assessed.
  • Has missing (hasMissing)
  • No missing (noMissing)
  • Rejected (rejected)
  • The progressive profiling is missing information.
  • The progressive profiling is not missing information.
  • The progressive profiling has been rejected.
Progressive profiling started (progressiveProfiling)Progressive profiling has started.
  • Next profiling step (nextProfilingStep)
  • Profiling completed (profilingCompleted)
  • Rejected (rejected)
  • The user has moved to the next profiling step.
  • The profiling is completed.
  • The progressive profiling was rejected.

Labels

NameDescription

Progressive profiling (success:progressiveprofiling
failure:progressiveprofiling)

The progressive profiling process was either successful or failed.

Registration and Login

Blocks

NameDescriptionOutcome nameOutcome description
External login provider assessment (externalLoginProvider)The system is checking if the user is registered with an external login provider.
  • Account already exists (accountAlreadyExists)
  • Created (created)
  • Email mismatched (emailMismatch)
  • Failed (failed)
  • External login provider identified (identified)
  • Rejected (rejected)
  • An account with the same credentials already exists.
  • The account was created successfully.
  • The email did not match.
  • The login failed.
  • An external login provider has been identified.
  • The attempt was rejected.
Loading device session (loadDeviceSession)"Remember this device" has been clicked and the device session is loading.
  • Success (success)
  • Device session load was successful.
Login hint provided (loginHint)The user needed a login hint to proceed.
  • Pre-fill (preFill)
  • The users data was pre-filled after login hint was completed.
Post external login assessment (postExternalLogin)The post external login is being assessed.
  • Allowed (allowed)
  • Rejected (rejected)
  • Show error (showError)
  • The action was allowed.
  • The action was rejected.
  • An error occurred.
Registration started (registration)Registration has started.
  • Sucess (success)
  • Rejceted (rejected)
  • Registration was successful.
  • Registration was rejected.
Post registration assessment (postRegistration)Post registration is being assessed.
  • New password accepted (accepted)
  • Rejected (rejected)
  • The new password was accepted.
  • The registration was rejected.
Reject login OIDC (rejectLoginOidc)Login via OIDC was rejected.
Reject login SAML 2(rejectLoginSaml2)Login via SAML2 was rejected.

Labels

NameDescription

Login (success:login
failure:login)

The login process was either successful or failed.

Logout (success:logout
failure:logout)

The logout process was either successful or failed.

Registration (success:registration
failure:registration)

Registration was either successful or failed.

Users, Roles, and Groups

Phases

NameDescriptionOutcome nameOutcome description
Step: Initiation (init)The initiation flow is processing.
  • Started (startFlow)
  • Invite started (startInvite)
  • The flow has started.
  • The invite guest flow is starting.
Step: Invite guest (invite)The invite guest flow has started.
  • Account registered (account_registered)
  • Registered external login provider (external_login_provider_registration)
  • The account is registered.
  • An external login provider is registered.

Blocks

NameDescriptionOutcome nameOutcome description
Forgotten username triggered (forgottenUsername)A user clicked "forgot username".
  • New username accepted (accepted)
The new username has been accepted.

Labels

NameDescription

Personal data download (success:personal_data_download
failure:personal_data_download)

Downloading personal data was either successful or failed.

Personal data update (success:personal_data_update
failure:personal_data_update)

Updating personal data was either successful or failed.
Forgotten username requested (success:forgotten_username_request)The forgotten username request was successful.
Group removed (success:group_removal)The group was successfully removed.
Admin role assigned (success:role_assignment)The admin role was assigned successfully.
Admin role removed (success:role_removal)Admin role was removed successfully.
Group assigned (success:group_assignment)The group was assigned successfully.