Queue-it Connectors

Queue-it’s virtual waiting room can be deployed using our pre-built Connectors to integrate into your web technology stack. Once you have found and implemented the best Connector for your business requirements, you will be able to manage all of your waiting rooms through the web-based GO Queue-it Platform and/or the Queue-it Admin API.

For an in-depth guide to Queue-it's different Connectors, watch our product talk on Queue-it integrations demystified: How to ensure you’re set up for success.

Support levels vary by Connector. See the Connector Support table at the bottom of this page for an overview. 

Queue-it’s server-side integration uses a secure Connector SDK. Like the Edge Connectors, this integration prevents end-user manipulation and ensures an unskippable queue. A server-side integration can normally be done in one day by a skilled developer.

See our Technical Integration White Paper. Start with section 5: Known User Integration Method Details.

White papers are available in the GO Queue-it Platform under Help | White Papers. If you do not have access to the GO Queue-it Platform, you can get the white paper.

Queue-it's native mobile app Connectors allow you to prevent traffic overload on your native app. With the native mobile app Connectors, you can either 1) queue app users into the same waiting room as desktop users or 2) queue app users into a separate waiting room. By using WebView in the app, users can see the same responsive waiting room page in the app as users see on the desktop view.

See our Mobile App Integration White Paper.

White papers are available in the GO Queue-it Platform under Help | White Papers. If you do not have access to the GO Queue-it Platform, you can get the white paper.

See our Technical Integration White Paper. Start with section 5: Known User Integration Method Details.

White papers are available in the GO Queue-it Platform under Help | White Papers. If you do not have access to the GO Queue-it Platform, you can get the white paper.

For Queue-it’s client-side Connector, JavaScript code is inserted on the relevant pages that are to be protected by the waiting room. It is easy and quick to implement the JavaScript Connector. However, it is less secure than our server-side or edge Connectors, as tech-savvy end-users can potentially manipulate the client code and skip the queue.

To implement the client-side Connector, insert the JavaScript snippet below into the page(s) on your site and you are ready to protect them. You find the snippet with your account ID on the events Deployment tab in GO Queue-it, our web-based admin platform.

See our Technical Integration White Paper. Start with section 6: JavaScript Integration Method Details.

White papers are available in the GO Queue-it Platform under Help | White Papers. If you do not have access to the GO Queue-it Platform, you can get the white paper.

Queue-it’s Queue Token SDK is used to ensure that end-users cannot enter the waiting room without a valid token. This token could be for example a promo code, a login id, etc. The token is generated by your logic. It also serves as a container which can carry sensitive user information from integrating system into the waiting room.

The Queue Token SDK is a powerful way to combat bots. For example, when running a members-only ticketing sale, the venue could require members to enter their membership ID to get a spot in the waiting room.