This page explains what checkpoints are and how to use them.
A checkpoint is a key event within a customer’s journey where you can request a recommendation from Ravelin. The checkpoints you want to use within your integration will likely depend on the kind of behaviour you are trying to address and where you would like to intervene in the customer journey.
For example, to stop payment fraud you might want to request a recommendation when a customer registers a new payment method or at checkout. If you want to counter account takeover, you might want to request a recommendation at login and checkout.
Read MoreThere are two currencies sub-divided into 5 basic units, seven sub-divided into 1000, and eighteen without any subdivisions.
Read MoreYour customer service reps logging into customer accounts in your live system may result in them joining networks together.
Read MoreIt is common for merchants to offer different types of discounts in relation to the products they sell. This guide is intended to help explain how best to send this information to Ravelin.
Regardless of how you implement discounts, the guiding principle here should be that the order price sent to Ravelin must always match what the customer spent on the order.
There are two different ways you can share discount data with Ravelin. The main difference depends on whether you have access to the price of an item before a discount was applied.
Read MoreFor most of Ravelin’s merchant-related products, the customerId is the key identifier as many of our products focus on analysing the behaviour of an individual.
This guide explains what identifier to use as the Ravelin customerId for guest checkouts.
The guiding principle for guest checkout is that all orders placed by the same individual should be associated with the same customer profile in Ravelin. This is useful for visibility within the Ravelin dashboard and it is important for the performance of the machine learning models.
Read MoreWas this page helpful?