iMIS Power Suite - Cvent Integration

iMIS Cvent Integration

The Cvent Integration allows meetings and events created in Cvent to be automatically imported into iMIS. This includes generating corresponding meeting and activity records for iMIS members who register through Cvent. The integration also supports an IQA query to define which members are eligible to register for specific events, and a single sign-on (SSO) process that enables authenticated users to register directly from the association’s website.

This article outlines the integration’s key components, requirements, and workflow.

Refer to the following resources for installation and setup guidance:

Requirements

The following components are required for the Cvent integration:

  1. iMIS
    • Query
      • 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

    Important! 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 Cvent integration configuration
        • Need to setup webhook endpoint and access token key
    • API Credentials – provided by Cvent
      • To be entered and used by Cvent middleware
  3. Cloud > Cloud Dashboard
    • Cloud ID – provided by ASI
      • Enables access to the middleware
      • Please contact us for additional information

Registering for events

The following process outlines how event registration works with the Cvent integration:

  1. A prospective registrant visits the association’s website and navigates to the Events page.
  2. The registrant clicks Register, which is provided by a Registration Widget—either a content item or a web user control (for Public View sites).
  3. If a query restriction prevents registration, a message appears indicating that registration is not allowed. If registration is permitted (or if no query is configured), the registrant is redirected to a Cvent registration page prefilled with data from the Cloud. The registrant clicks Submit to complete registration.
  4. Cvent triggers webhooks to send registration data to the Cloud, which creates an activity record in iMIS.
  5. If the registrant cancels, another webhook is triggered, and the Cloud automatically removes the associated activity from iMIS.