Non siete sicuri del significato di alcune frasi del Piano? Ecco un pratico elenco di definizioni:

2FA

Two Factor authentiction for admin panel users is supported using apps such as Google Authenticator. 

More about 2FA.

Rilevamento delle anomalie e blocco delle minacce

If your plan supports these advanced security features you will be able to automatically block IPs that are known threats (based on third party intelligence data), and automatically block the IPs of sessions that exhibit anomalous behaviour based on session analysis. 

More about anomaly detection.

Autotune

If your Plan supports Autotune, you will be able to have CrowdHandler set your ingress rate, by analysing the performance of your web pages. You will need to use one of our integrations in order to supply performance information.
Using Autotune.

CAPTCHA

If your plan supports CAPTCHA you can require users to complete a CAPTCHA in order to access the waiting room, or the resource protected by the waiting room. This provides basic but effective bot protection, especially for queues abuse. The Open Source ALTCHA captcha provider is included. You can also use Google ReCAPTCHA or hCAPTCHA but you must bring your own account and you may need to pay extra fees to those providers depending upon the number of captcha completions required. 

More about CAPTCHA.

Modelli personalizzati

If this feature is available, you will be able to upload or link Custom Templates on your Plan. Each Waiting Room can use a different Custom Template if you wish. If your Plan does not have this feature you will still be able to upload your own logo. 

More about Custom Templates.

Impronta digitale del dispositivo

Incorporation of user agent and IP/geolocation data to fingerprint each queue session, making it harder for users to collude in token sharing.

Implementazione DNS

If your Plan supports DNS implementation, you can skip server-side integration and validate all of the traffic to your website by routing your traffic through our reverse-proxy. This requires a DNS change, and is subject to reasonable-usage data limits, which vary based on your Plan. 

Setting up DNS Implementation.

Domini

Questo è il numero di nomi di dominio unici supportati dal vostro piano. I domini unici includono i sottodomini, quindi:

Conterebbe come 4 domini.

API completa

If your Plan enables full API access, you will be provided with a private API key, and access to API documentation that will allow you to control everything in your CrowdHandler account via the API. If this box is not ticked, you still get access to a public API key and documentation that will help you to integrate your website with CrowdHandler to verify the users visiting your website. 

Getting started with the API.

Inbound req/min

This is the maximum number of users we will ingest into your queue in a given minute. If you exceed this number, excessive requests will be directed to the waiting room without a position in line, those waiting users will then re-poll until they get a position.

Tasso di ingresso

This is the maximum rate, measured over a minute, at which a domain can accept new users from CrowdHandler. You can think of this in more than one way:

If your domain name has one waiting room protecting all traffic to your domain, this would be the maximum rate at which users can leave that waiting room to be redirected to your site. (If you have more than one waiting room operating simultaneously on your domain then the rate is balanced across those rooms based on demand.)

If the website at your domain is operating as normal, it's the maximum rate of inbound users that your website can handle before it needs to queue users. So if you are running an ingress rate of 60, then the 61st user to visit your site over a one minute period would be sent to a waiting room to wait.

This is the maximum rate allowed by your Plan for each domain. You can set the actual rate on a domain-by-domain basis.

More help understanding the rate.

Controllo IP

If your Plan supports IP control you will be able to block, promote, prioritise, or ignore users from IP ranges that you register.

Log Retention

CrowdHandler tracks queue numbers and active session totals minute by minute, after the specified log retention period, data will be summarised by hour. Detailed data can be exported from the control panel or the API.

Accesso prioritario

If your Plan supports Priority Access you will be able to set up VIP priority access lanes, using single-use or multi-use codes. The number of single use codes is limited by the capacity of the waiting room to which the codes apply. Code groups can be set to allow pre-activation access which means that users with a code can access behind the queue during the waiting room countdown period. 

More about Priority Access.

Segnalazione

Ability to review historical queue data, filtered by domain, waiting room and date range, to see waiting user counts, average and maximum wait times and export data.

Risposta di supporto

Support is delivered via our support portal, where you are able to submit a ticket for support. We guarantee response times based on your Plan. 

More about support.

User Accounts

The number of customer representatives with access to the control panel.

Sale d'attesa

Questo è il numero di sale d'attesa che è possibile impostare nel proprio account. Tutte le sale entro questo limite possono essere attive contemporaneamente. Se non si ha più bisogno di una sala d'attesa, è possibile eliminarla e aggiungerne una nuova, fino a questo limite massimo.

Capacità della sala d'attesa

This is the total number of users you can have queueing at any given time across all your Waiting Rooms and domains. You can manually apportion the capacities of each Waiting Room to split the capacity where you need it if you need to run simultaneous queues. Alternatively, you can check the apply capacity automatically box, and CrowdHandler will automatically balance waiting room capacity in proportion to traffic. 

When a waiting room reaches its capacity, new users will see a message letting them know that the room is full. But they are able to wait until the room empties a little to receive a queue position. The messaging and experience for a room full state can be customised in a custom template.
What happens if the room is full?