Queue-it versus Akamai | Product Comparison

Queue-it’s Virtual Waiting Room vs. Akamai’s Visitor Prioritization

This comparison between Queue-it’s Virtual Waiting Room and Akamai’s Visitor Prioritization provides more insight into the key differences between the two solutions and how they each handle your visitors during high traffic peaks.

Feature Queue-it Akamai
Virtual Waiting Room

Queue-it is a dedicated Virtual Waiting Room (VWR) SaaS.

Akamai’s Visitor Prioritization cloudlet add-on can offload end-users into a Virtual Waiting Room.

First-in, first-out wait

Queue-it offloads overflow visitors to a Virtual Waiting Room system, passing them back to the website at a rate it can handle, in the correct, sequential order, following the first-in, first-out principle. All theories and research suggests that the FIFO principle drives fairness and end-user satisfaction.

Akamai is, per design, based on decentralized edge locations and the Visitor Prioritization cloudlet is forwarding users out of the Virtual Waiting Room in a random order independent to each edge location.

Page-level implementation

Queue-it’s waiting room can be implemented on specific page-levels, enabling the handling of the high-traffic event while keeping the rest of the website accessible, allowing the customers that are not visiting the website for the specific event to keep browsing and complete their purchases.

Akamai’s Visitor Prioritization cloudlet offloads traffic, but addresses the total number of requests to the whole website and doesn’t support different offload strategies on individual site pages.

Multiple queues

Queue-it offers the possibility of having multiple queues for the same event, providing the ability to create priority or ‘VIP’ access to specific users. These users will be able to see that they have priority access, as well as how many other people are waiting in the ‘public’ queue – offering a level of psychological validation by seeing they have special access.

Akamai’s Visitor Prioritization cloudlet can prioritize some users in the randomized queue, but cannot divide it into multiple waiting rooms. This results in some users gaining access faster, but no way of knowing that they were prioritized, as the forwarding is random.

Informed wait

Queue-it’s waiting room provides real-time information and communication to customers, including the reasoning for the wait, their position in line and the number of other people waiting, and custom up-to-date live posts. Customers then know how long they will have to wait in line and the expected time of arrival on the website.

As a CDN tracks page requests and does not track each unique site visitors, the system must offload them to the website in a randomized order and therefore cannot provide an informed wait. The lack of information provided results in uncertainty and frustration, thus driving up bounces and driving down conversion and customer satisfaction.

SDK running on origin servers

Queue-it offers a programmatic way of handling users coming out of the queue on origin servers. By knowing their unique user IDs, the users’ next actions can be directed after they have left the queue, and also gain insight into their individual user journeys, from applying promo codes, to opening multiple browsers, and other relevant information.

Akamai does not have SDK libraries running on the origin servers.

Real-time flow data management and control

Queue-it offers real-time flow analytics in a web based interface, with access to a dashboard to visualize and control the user inflow and outflow per minute.

Akamai Visitor Prioritization works by allowing a certain percentage of users in, but does not see or provide any analytics of the traffic. The system can let in a certain percentage of the users waiting, but does not know the number of users waiting.

Full history of all inflow and outflow per minute

Besides offering real-time access to the flow analytics, Queue-it also provides access to the full history of all +25 metrics like inflow, outflow per minute and queue size, which can be accessed at all times after the completion of the event.

Akamai Visitor Prioritization cloudlet does not store information about end-users’ journeys in or out of the waiting room.

Native app support

Queue-it has native iOS and Android SDK’s that can be embedded in native apps. The SDK can be connected to the same queue as desktop users or additional, separate queues. The same informed responsive queue-page is displayed to end users as on desktop. Queue-it supports sessions for the native app user, so once the user has gone through the queue, the user will not queue again.

Akamai Visitor Prioritization can be configured to respond to an API or service calls with an alternate, non-html asset, for example json or xml, when that service is at risk of becoming overloaded.

Utilizing any pre-existing CDN

Integrates with any CDN (Akamai, Fastly, Verizon, CloudFlare, InstartLogic, Amazon CloudFront, etc.)

Will only work with Akamai CDN.

Product demo

Looking for a more in-depth preview of the virtual waiting room?