Behavioral Data Collector
Vesta’s Behavioral Data Collector integrations enhance the device and behavioral tracking information we obtain from your application, which improves our risk assessment and fraud detection services. We offer tools and SDKs, which make it easy to incorporate behavioral data collection into your application.
For details about incorporating Behavioral Data Collector components into your application, see the documentation for your development platform: Web, Android, or iOS.
Data Collector integrations for mobile apps require additional libraries. Visit the Downloads page to obtain the most up to date version of the Behavioral Data Collector files for Android or iOS apps.
Our Behavioral Data Collector integrations use field tagging and events to identify details about how your customers interact with your application:
- Field Tagging - Field tagging associates elements of your application, like user name fields, with FieldNames defined by Vesta. Identifying these application elements makes it possible for Vesta to identify when and how your customer interacts with your app, and analyze the data for indications of fraud.
- Events - Specifying events makes it possible for your app to alert Vesta when your customer interacts with a specific element of your app. Vesta tracks the user over the course of the event and analyzes the behavior and metadata about the event for indications of fraud.
See the Field Tagging and Events sections on this page for details about defining field tags and events that Vesta will track.
Field Tagging
Field tagging associates the field name or id of an element in your application with the FieldName used by Vesta. This makes it possible for Vesta to relate device and behavioral data with specific activities performed by your customers when they use your app. Field Tagging is typically used for tracking text entry in fields like login ID and password, but it can also be used to identify buttons to watch for clicks. Use the field tags listed in the table below to identify the associated UI elements:
| Field Tag | Description |
|---|---|
| LoginID | The username field of your login form. |
| Password | The password field of your login form. |
| ProductSearch | The text field used to search for products. |
| AddToCart | The button used to add a product to the shopping cart. |
| RemoveFromCart | The button used to remove a product from the shopping cart. |
| TransferRecipient | The text field used to identify the recipient of a transfer payment. |
| TransferSender | The text field used to identify the sender of a transfer payment. |
| TransferToAccount | The text field used to identify the account that will receive the funds from a transfer payment. |
| TransferAmount | The text field used to define the amount of a transfer payment. |
| TransferDate | The text field used to define the date that a transfer payment should be made. |
| BillingFirstName | The text field used to collect the first name of the cardholder. |
| BillingLastName | The text field used to collect the last name of the cardholder. |
| BillingAddressLine1 | The text field used to collect the first line of the cardholder’s billing address. |
| BilllingAddressLine2 | The text field used to collect the second line of the cardholder’s billing address. |
| BillingCity | The text field used to collect the city portion of the cardholder’s billing address. |
| BillingRegion | The text field used to collect the region of the cardholder’s billing address. |
| BillingPostalCode | The text field used to collect the postal code of the cardholder’s billing address. |
| BillingCountryCode | The text field used to collect the country code of the cardholder’s billing address. |
| PurchaseCardNumber | The text field used to collect the customer’s payment card number. |
| PurchaseCardExpirationDateFull | The text field used to collect the expiration date of the customer’s payment card. |
| PurchaseCardExpirationDateMonth | The text field used to collect the month portion of the expiration date of the customer’s payment card. |
| PurchaseCardExpirationDateYear | The text field used to collect the year portion of the expiration date of the customer’s payment card. |
| PurchaseCardCVV | The text field used to collect the CVV number associated with the customer’s payment card. |
| PurchaseAlternateAccount | The text field used to define an alternate payment method for the purchase. |
| DeliveryMethod | The UI element used to select the shipping method. |
| DeliveryRecipient | The text field used to collect the name of the person who will receive the shipment. |
Events
Designate events for Vesta to track by calling the event methods when your customers interact with different elements of your application. For logical events, which have an implied end, call the vCustomer.startEvent(); method. For screen tracking events, which require the application to designate the start and end of an interaction, call the vCustomer.startEvent(); method when the customer begins an interaction. Then, call the vCustomer.finishEvent(); method when the customer completes the interaction.
For screen tracking events, you must end the current event before starting another event. Vesta will not track multiple simultaneous events. See the Example User Flows below for details about how to implement Vesta’s fraud detection services using events.
The sections below define the logical and screen tracker events supported by Vesta.
Logical Events
Include the event name listed in the table below as a parameter in the startEvent method to track the associated action. Logical events end automatically, when the action is complete.
| Event Name | Description |
|---|---|
| LOGIN_ATTEMPT | Start this event when your customer clicks the login button. |
| SIGN_UP | Start this event when your customer clicks the button for creating a new account. |
| SIGNUP_ATTEMPT | Start this event when your customer clicks the button for creating a new account, but the credentials have not yet been validated. |
| SEARCH | Start this event when your customer activates the search field or clicks the button to perform a search. |
| ADD_TO_CART | Start this event when your customer clicks the button to add a product to the shopping cart. |
| REMOVE_FROM_CART | Start this event when your customer clicks the button to remove a product from the shopping card. |
| SHOW_CART | Start this event when your customer clicks the button to view the contents of the shopping cart. |
| PROCEED_TO_CHECKOUT | Start this event when your customer clicks the button to begin the checkout process. |
| CONFIRM_PAYMENT_METHOD | Start this event when your customer clicks the button to confirm the payment method. |
| CONFIRM_SHIPPING_METHOD | Start this event when your customer clicks the button to confirm the shipping method. |
| COMPLETE_ORDER | Start this event when your customer clicks the button to complete the order. |
Screen Tracker Events
Use screen tracker events to make it possible for Vesta to identify the screens that your customer visits during shopping and payment. Include the event name listed in the table below as a parameter in the startEvent method to track the associated action. You must call the associated finishEvent method when the user has completed the action. You cannot start another event until you have ended the current event.
| Event Name | Description |
|---|---|
| LOGIN | Start this event when your customer lands on the login screen or activates the text fields associated with logging in. End the event after your application processes the log in request, or if your customer abandons the login attempt. |
| FORGOT_PASSWORD | Start this event when your customer lands on the forgot password screen. End the event after your application processes the password reset request. |
| SIGNUP | Start this event when your customer accesses the screen you used to create a new account. End the event after your application processes the new account request. |
| PRODUCTS_LIST | Start this event when your customer lands on a screen that displays a list of products. End the event when your customer leaves the product list. |
| PRODUCT_DETAIL | Start this event when your customer opens a page that displays details of a single product. End the event when your customer leaves the page. |
| SHOPPING_CART | Start this event when your customer accesses the shopping cart. End the event when your customer leaves the shopping cart page. |
| CHECKOUT | Start this event when your customer lands on the checkout screen. End the event when the customer completes or abandons the checkout process. |
| PURCHASE_CONFIRMATION | Start this event when your customer lands on the final screen to confirm the purchase. End the event after your application processes the purchase confirmation. |
| SETTINGS | Start this event when your customer lands on any of your account settings screens. End the event when the customer saves or cancels and account updates. |
| PROFILE | Start this event when your customer lands on the screen that displays profile information. End the event when your customer leaves the profile screen. |
| PAYMENT_DETAILS | Start this event when your customer lands on the screen that you use to collect payment details. End the event after your customer clicks a button to confirm the payment details. |
| SHIPPING_DETAILS | Start this event when your customer lands on the screen or activates a text field that you use to collect shipping details. End the event when your customer clicks a button to confirm the shipping information. |
| SEND_MONEY | Start this event when your customer lands on a screen used to send money to a specified recipient. End the event when the send money request has been processed or abandoned. |
| GIFTCARD | Start this event when your customer activates a text field used to enter gift card information. End the event after the customer clicks a button to confirm the gift card data. |