The Strivacity Lifecycle Event Hooks (LEH) provide a method to integrate your customer facing applications with homegrown systems and third-party products.
Lifecycle Event Hooks can be used in many different ways. Some of the more common use cases involve customizing registration, updating or fetching data from remote systems such as CRMs during certain lifecycle events, or alerting third-party systems on specific events of interest such as:
- Deep customization of registration - Brands often require extensive customization of the registration process. Information from external systems, such as CRMs, may be required to keep multiple disparate databases in sync. Often a brand will pull this in during a pre-registration hook to allow it to be submitted during the Registration process. New or additional information can be easily synchronized back to an external system in real time.
- Customer data synchronization - Brands may require keeping disparate customer databases in sync, such as the customer identity store and a remote CRM system. Customer Lifecycle Event Hooks can be used to dispatch information about events of interest to these remote systems.
- Alerting - Brands may desire to be alerted when an event of interest occurs, such as a password reset request.
- Consume and use threat information - Insert threat detection and mitigation into any point in the customer lifecycle, giving security teams highly contextual alerting when threats are detected. Existing threat information can be used to make risk analysis decisions.
- Synchronous - Control is transferred to the script for execution. Upon completion, control is returned to Strivacity's normal workflow execution.
- Asynchronous - The script is executed but control is not transferred, and Strivacity continues on with its normal workflow execution.
The brand decides and can configure, in the administration console, whether an event hook should execute synchronously or asynchronously.
Plugins make publishing lifecycle event hooks easy.
The plugin library provides you with hook templates for common use cases. Event hook templates are off-the-shelf integration and advanced capability packages that you can customize for your own needs and add to your applications.
The template packages come with all the necessary dependencies set up. Their point-of-entry into the customer lifecycle is also configured, so you don’t have to think about selecting the right event hook type:
After selecting the capability that you want to add to your application, you can publish the template as a new lifecycle event hook. You can customize the code inside the hook and assign it to an application to have it deployed.
Multi-stage progressive profiling
Strivacity’s "Before registration" and "Before progressive profiling" event hooks allow you to introduce progressive profiling steps to customer journeys on your conditions. You can configure steps to adapt to your customers' activity to make data collection a more personalized experience.
The following table shows a summary of the events that are supported by Strivacity with examples of how they can be used:
|Fetches data from an external system so it can be used and stored with a customer's account during the account registration process.
|Before progressive profiling
This event launches after a customer completes the first step of registration.
You can add extra steps to the registration workflow for various progressive profiling scenarios:
|Once a customer has successfully completed the account registration process this event is triggered to trigger an external event or fetch/update data with an external system.
|After account activation
|Triggers an external event once a customer has clicked the account activation link sent via email during self-service registration.
|Before ID token generation
|Used to add additional claims to OIDC and OAUTH by fetching data from an external systems before the ID token is generated
|Before SAML2 assertion generation
|This event triggers before assertion is generated during SAML login flow. You can add additional assertion data to the SAML assertion or deny the request based on certain criteria.
|After username request
|This event is triggered after a customer has completed a Forgotten Username request using the forgot my username via the login screen.
|After customer identification
This event is triggered once the customer has provided their identifier (email address or username) and before they are asked for any factor of authentication.
This can be used to step-up or step-down the authentication journey based on an external event, risk data from an external system, or other account attribute information for that customer.
|At failed identification
This event is triggered when a customer identity coming from an external identity provider doesn't exist in the application's identity store.
|Before password validation
This event is triggered when a customer identity is found eligible to be migrated from an external identity store.
|Before password reset
|This event is triggered after the customer has initiated the Forgot my Password process from the login screen, and before the customer completes the password reset workflow.
|After password change
|This event is triggered after the customer has successfully reset their password. You can use this event to keep an external identity store in sync.
|Before progressive profiling
This event launches after successful authentication, right before a customer login flow is completed.
Make the best of this extra step in the workflow and use hooks to adapt to various progressive profiling scenarios:
|After consent update
|This event is triggered after a customer opts into or opts our of any consents at registration or self-service. Use this event to synchronize consents with other third-party systems such as marketing hubs, email advertising platforms or CRMs.
|After MFA change
|Triggers an external event or fetches data from an external system once the customer has completed the verification of a new/additional MFA factor during enrollment or removed a factor.
|At failed authentication
This event occurs when customer authentication or registration fails for some reason.
|After self-service login
|Triggers an external event or fetches data from an external system after the customer has successfully authenticated and they have an ID token.
|After external login
|Triggers an external event or fetches data from an external system once a customer has successfully completed registration using a social login provider.
|After account disabling
|Once a customer account has been disabled then you can use this to trigger an account disabled event of notification or account disable process in other systems.
|After account termination
|Once a customer account has been deleted you can use this to trigger an external event of notification or account deletion process in other systems.
|Before identity verification
|This event launches before the identity verification workflow starts.
|After identity verification
|This event launches after the identity verification workflow has finished.
- Customize registration by bringing in and persisting external data
- Establish a single source of truth and synchronize customer data across multiple systems
- Insert threat detection and response into any point in the customer lifecycle
- Alert your customer service or security teams to events of interest
- Trigger workflow in external orchestration systems when customers perform specific actions
- Make location based decisions in customer login and registration flows
Updated 2 days ago