Cvent

Overview

Cvent Integration allows Meetings and Events setup in Cvent to be imported into your iMIS database. This includes creating meeting and Activity records for your iMIS members who have registered via Cvent. It also features the ability to use an IQA query to determine which members are allowed to register for specifics events in Cvent. This includes a Single Sign On process to enable authenticated users from your association website to register for a Cvent meeting.

Included on this page is navigation to important aspects of the Cvent CSI Cloud product, requirements for the product, and a use case/workflow of the product.

Requirements

1. iMIS

   • ASI Scheduler Endpoint

     • iMIS version 2017, iMIS EMS Enterprise, and iMIS EMS Professional

     • Enable access to the CSI Cloud API endpoint. Instructions for this are available in the Environment Setup article.

   • IQA

     • Associated with each event

     • Must accept optionally as parameters either an iMIS ID or an Email Address

     • Columns name will be used to match a registrant field information in Cvent

   • Association's Website

     • For example: either RiSE or Public View

     • Requires installation of widget, either iPart or Web User Control

   

   It is highly recommended to limit external network access to your REST API endpoint. For this reason, we suggest using a whitelist to control who can access those services.

2. Cvent

   • Staff User Account

     • Enables event registration setup

     • Enables CSI Cloud Cvent integration configuration

       • Need to setup webhook endpoint and access token key

   • API Credentials – provided by Cvent

     • To be entered and used by CSI Cloud Cvent middleware

3. CSI Cloud

   • Cloud ID – provided by CSI

     • Enables access to the CSI Cloud middleware

     • Please contact us for additional information

Attendee Workflow

1. Potential attendee visits the association’s website and navigates to the Events page.

2. Potential attendee clicks on “Register” link for the desired event. This link is provided by a Registration Widget, either an iPart or a Web User Control (if the website is Public View).

3. If the IQA is set up and the potential attendee is not allowed to register, a message stating so will appear. If the potential attendee is allowed to register, or the IQA is not set up, then the link takes the potential attendee to a Cvent registration page in which the fields are already filled by CSI Cloud and the future attendee only has to click “Submit” to register.

4. Cvent triggers Webhooks, giving the registration information to CSI Cloud. CSI Cloud then makes an activity in iMIS.

5. If the potential attendee cancels their reservation, a webhook will be triggered once more, removing the activity from iMIS.