Behavioral Biometrics Setup

Behavioural Biometrics is the way a user navigates a page and interacts with page elements and their device.

Darwinium has the ability to profile Page Biometrics data, including:

Mouse: Clicks, movement, off-page
Keyboard: Typing pattern, shortcuts, unusual keys, corrections
Touch (mobile device only): Taps, swipes
Sensor (mobile device only): Accelerations, rotations, light, pressure, magentic field

Additionally, features can be generated in the engine that compare the biometrics now vs. previously, forming powerful Behavioural Biometrics data.

Availability

Behavioural Biometrics data can only be produced when Javascript is running on a consumer's browser

Setup

Behavioural Biometrics data can be configured through the Darwinium workflow on Portal.

Enabling by adding snippet

To enable behavioural biometrics on a journey, open the journey file in the Portal Workflow tab and enter the journey settings.

Add a reference to the Darwinium Behavioural Biometrics snippet. This provides the journey with behavioural biometrics.

The snippet should be included in the src folder at top level. See snippets for more on snippets in general.

Injecting into a Step

Behavioural Biometrics is profiled by Javascript code.

This code can be inserted into any step where desired.

Choose GET steps

For maximum benefit, the Behavioural Biometrics scripts need to be injected on GET requests (i.e page load),
The intelligence will then be available on the subsequent POST request (i.e page submit)

To inject a script, open the journey file, click on a step and navigate to the Data Mappings tab,

Scripts are injected in the body of the response. This is because they need to be included in the page being served back to the end user.

There is a different script to inject depending on intelligence desired to scrape:

Mouse
Keyboard
Touch
Sensor

Finally, the following must be added to ensure script runs:

Map Page Inputs to Darwinium Attributes

Darwinium Behavioural Biometrics can be collected and stored on a per field basis (eg. username textbox, address fields, first name, last name). The benefit is that different forms have different risky interaction profiles. A paste into a confirm email field is more common and less risky than a paste into a first name field (what genuine user would paste their first name?).

Mapping to Darwinium Biometrics attributes is done in the same place as script injects: Journey file -> Click on Step -> Data Mappings -> Response -> Body Mappings.

See data for preconfigured list of attribute contexts to map into.

The following XPath format can be used to identify (and therefore map) forms on the page by their id (here, the id of the fields are id_profile_city and id_preferred_contact).

//input[@id="id_profile_city"]

Manual Mapping

Manual mapping is needed if a site is structured as a Single Page Application.