Challenges are measures put in place to identify genuine visitors from non-genuine visitors. For non-genuine visitors the objective is to increase the complexity and cost of joining the waiting room, in order to provide a fairer user experience for genuine visitors in the waiting room.
Challenges can be utilized to limit the amount of non-genuine visitors by requiring visitors to prove that they are committed to joining a waiting room.
Challenges and access blocking are both ways of mitigating non-genuine activity in waiting rooms, where challenges are less restrictive as it leaves the visitor with the option to continue the user journey when the challenge is solved.
Supported types of challenges
There are different types of challenge that visitors can be requested to solve. Some requires visitor interaction to be solved, others run in the background and are solved by the browser. Supported challenges are:
- Proof-of-Work: A challenge–response test that requires your visitor’s browser to solve an algorithmic puzzle using computing power, while being invisible to real visitors.
- Queue-it CAPTCHA: A type of CAPTCHA provided by Queue-it which prompts the visitor to enter a set of characters displayed on an image.
- reCAPTCHA: A type of CAPTCHA provided by Google which uses an advanced risk analysis engine and adaptive CAPTCHAs.
- Invisible reCAPTCHA: A type of CAPTCHA Challenge provided by Google which builds on reCAPTCHA and allows valid known visitors to pass through with ease.
How to challenge visitors/reasons traffic to get challenged
Queue-it allows you to configure challenges for different scenarios. Ranging from where the visitor traffic originates from, to challenges that every visitor has to solve.
Furthermore, if Queue-it's Anomaly Detection detects abnormal traffic - possibly originating from non-genuine visitors - visitors may also be prompted to solve challenges.
Why or when a visitor is challenged depend on the following features:
- Anomaly Detection: Queue-it analyzes HTTP requests and user behavior to detect abnormal traffic patterns. When abnormal traffic is detected Queue-it will present challenges or block requests. Anomaly detection is enabled on all accounts.
- Enter Queue Challenge: Waiting rooms can be configured to challenge all visitors who attempt to enter the queue.
- Traffic Access Rules (limited preview): Rules can be configured to challenge visitor segments before visitors enter the waiting room. Visitor segments are e.g., visitors originating from a specific country, IP subnet or ASN.
- Data Center Blocking: Queue-it maintains a list of IP addresses/subnets from verified data centers. Waiting rooms can be configured to challenge users or block access to visitors originating from data centers.
Please sign in to leave a comment.