Virtual Waiting Room and Visitor Prioritization Comparison
Virtual Waiting Room and Visitor Prioritization both offer a waiting room experience when your website (origin) is not available to accept all visitors. This section explains the differences between Virtual Waiting Room and Visitor Prioritization to help you select the best waiting room product for your needs.
| Comparison criteria | Virtual Waiting Room | Visitor Prioritization |
|---|---|---|
| Availability Status | Beta - available for trial. | General Availability - available now. |
| How it works and use cases | Uses a fair request processing mechanism called FIFO (First In First Out). Visitors who enter your waiting room first, are the first to leave the waiting room to enter the origin. You can control the number of visitors admitted to the origin by setting the number of visitors per second. Once the number of visitors exceeds the set value, new visitors are sent to the waiting room. The number of visitors allowed to enter your origin; - default is 1000 visitors/second - minimum is 10 visitors/second - maximum is 10,000,000 visitors/second Typical use cases; - Flash-Sale - Vaccine sign-up queues - Maintenance - When you need to set up a large number of waiting rooms. - Campaigns | Uses percentages and probability to control the percentage of visitors sent to the waiting room. You can configure to send 0 - 100% of all visitors to the waiting room. Visitor Prioritization is recommended for waiting room applications when fair queuing is not required. Typical use cases; - Flash-Sale - Maintenance - Campaigns |
| Number of customizable waiting rooms. You can customize the waiting room page and assets for each property to give your visitors a unique customer experience. | Create one policy for each waiting room queue. A single policy can be used on one property, or on multiple properties. When the same policy is used on multiple properties, all visitors from the multiple properties are placed in the same Virtual Waiting Room queue. | Create one policy for each waiting room queue. A single policy can be used on one property. |
| Status updates for your visitors | While in the FIFO waiting room, visitors see their estimated arrival time to enter the origin. Updates to the time remaining, and retries to the origin are all automatic. | Not available. |
| How to configure | There are 2 ways to set up Virtual Waiting Room; classic method and EdgeWorkers method. Use the EdgeWorkers method when creating and managing a large number of waiting rooms. Classic method 1. Create a Virtual Waiting Room policy (Visitor Prioritization with FIFO enabled), and add rules using Edge logic Cloudlets Policy Manager. 2. Download and set up your waiting room html page. 3. Add the policy and Virtual Waiting Room behaviors to one or more properties using Property Manager. EdgeWorkers method 1. Create EdgeWorkers scripts for Virtual Waiting Room. 2. Download and set up your waiting room html page. 3. Configure the Virtual Waiting Room for EdgeWorkers behaviors in Property Manager. An Edge logic Cloudlets policy is not required for this set-up. | Visitor Prioritization uses the classic cloudlets method for set up. Classic method 1. Create a Visitor Prioritization policy, and add rules using Edge logic Cloudlets Policy Manager. 2. Download and set up your waiting room html page. 3. Add the policy and Visitor Prioritization behaviors to the property using Property Manager. |
| What’s coming next in the roadmap | In the roadmap; - Traffic Monitoring. Near real time visibility on waiting room traffic. - Bot Detections. A separate queue to detect bots. - Mobile Applications Support. Expand waiting room to mobile applications. | No items in the roadmap at this time. |
The Virtual Waiting Room behavior in Property Manager requires a Virtual Waiting Room policy. You can not use a Visitor Prioritization policy with the Virtual Waiting Room behavior. The Virtual Waiting Room and Visitor Prioritization Cloudlet behaviors can’t be used together on the same property version.
Updated 9 days ago