Cadence Prerequisites in order to integrate Cvent with Cadence:


This integration allows you to map Cvent registration fields to standard profile and/or custom profile fields within your event in Cadence. You can also map information like Cvent Registration Paths and Registration Answers to Groups within Cadence.

Support for mapping Cvent Sessions and Speakers to Cadence Schedule Items and Speakers is on our roadmap.

NOTE: Cvent may require an additional cost to enable these integration options in your Cvent account. If you aren't already familiar with the below options work with your Cvent team to determine the best route for your organization.

Cvent Webhooks

  • Quickest setup for a single event

  • Requires manual setup within Cvent for each event

  • New registration activity is sent from Cvent to Cadence every 5 minutes

  • Read more on Cvent's Webhooks Integration Guide.

Cvent REST API

  • Cvent's newest/most actively maintained integration option

  • Great for multiple/many events as it only requires a one time integration setup within Cvent, each event's integration configuration then happens on the Cadence end.

  • Cadence checks for new registration activity in Cvent every 3 minutes

  • Read more on Cvent's REST API Integration Guide.

Cvent SOAP API

  • Somewhat legacy solution but still used by many enterprise Cvent customers, may even be required (meaning REST isn't an option) if you are still using certain legacy features of Cvent, such as their legacy Meeting Request Form tool.

  • Great for multiple/many events as it only requires a one time integration setup within Cvent, each event's integration configuration then happens on the Cadence end.

  • Cadence checks for new registration activity in Cvent every 3 minutes

  • Read more on Cvent's SOAP API Integration Guide.

Formal Steps to Apply Integration

  1. Inform your customer success manager or email intergrations@eventcadence.com with the version of Cvent your own and whether integration options are enabled.

  2. Work with Cadence to add us to your account to apply the integration

  3. Per event, define the registration types and registration form fields to integrate with Cadence. Which registration types/registration form fields should be included, excluded along with which ones should be admin only/visible to attendees

  4. Per event, define which registration form fields should auto-generate the groups and assignment of attendees to the respective group

  5. Once passed to the Cadence team, we'll finish the rest!

Did this answer your question?