Operation purposes

When you set up an operation, you need to choose the task your transactional page serves. If you can’t find it on the list, select the most similar option. The following operation purposes are available:

Login: Allows the user to log on to their account – either a bank account, an eCommerce one, etc. For this operation type, you must set the origin success and failure conditions.
Account creation: Allows the user to open a new account.
If you selected Account Creation and are part of our Account Opening Abuse program, you must make a selection in the User Data Parameters section. Select at least one value you use to identify users and specify the parameter where that user identification value lives. For example, if your visitors log in with their email address, then beside Email, enter the parameter where email addresses live and turn on its Used for login checkbox. You can select and specify several ID parameters here. Note that the first value in the list that you specify as login, appears in reports as username, even if it is an email value or other identifier. Also, for this operation type, you must [set the origin success and failure conditions](elect at least one value you use to identify users and specify the parameter where that user identification value lives. For example, if your visitors log in with their email address, then beside Email, enter the parameter where email addresses live and turn on its Used for login checkbox. You can select and specify several ID parameters here. Note that the first value in the list that you specify as login, appears in reports as username, even if it is an email value or other identifier. Also, for this operation type, you must set the origin success and failure conditions.)
Account verification: Verifies if an account exists. For example, you can use it on a page meant for logging in to or creating an account. When the user enters their email address in a form, if there is an account tied to that address, they are asked for their password and then logged in. If there is no account tied to their address, they are redirected to the account creation process.
Add to cart: Allows the user to add an item to their cart.
Giftcard balance check: Allows the user to enter identifying information, such as a card number and PIN, to view their gift card balance.
Loyalty points: Allows the user to enter identifying information and view the amount of loyalty points they have for the retailer.
Password reset: Allows the user to get a new password when they don’t know the previous one. For example, the user enters their email address in a form, then proves their identity by clicking a link they got in an email, and chooses a new password. Note that you can define the username and Origin Response Success/Origin Response Failure parameters for this operation.
Search: Allows the user to enter a word into the search bar to look for a specific product or service on a company website.

As a part of the Account Lifecycle Protection program, you can choose from the additional operation purposes:

📘
To perform these operations:

The user has to be logged in.

We recommend you set the origin success and failure conditions.

Account update: Allows updating details on the user’s account, such as email address, phone number, credit card number, etc.
Password change: Allows changing the password, for example, if the user’s previous password was compromised or if they want to change it regularly for safety reasons.
Payment: Allows conducting checkout transactions or money transfers. It can be used for checkout as a guest or as a logged-in user. Carding attacks usually happen at guest checkout, and you can use account protection detections for this type of abuse. For best results, set the email address or phone number of the user who is doing guest checkout, the username parameter for Guest Checkout operation, and the origin success/failure conditions