The CVent attendees feed integration allows Event Cadence to receive event registrant information from CVent and use it to maintain the attendee list inside an Event Cadence event.
This integration is intended primarily for attendee provisioning and group distribution. CVent remains the registration system, while Event Cadence uses the imported attendee list to control who has access to the event website, mobile application, schedule items, communications, materials, and event-specific features.
The main outcome of the integration is a properly populated Event Cadence event with attendees assigned to the correct Event Cadence groups.
The main purpose of the CVent attendees feed integration is to ensure that people registered for an event in CVent are available as attendees in the corresponding Event Cadence event.
The integration helps Event Cadence:
- Create the event attendee list based on CVent registrants.
- Keep the attendee list aligned with CVent registration data.
- Assign attendees to the correct Event Cadence event groups.
- Support attendee access to the Event Cadence website and native mobile applications.
- Enable group-based access and visibility rules inside Event Cadence.
- Reduce the need for manual attendee exports and imports.
Although attendee profile fields can technically be transferred as part of the feed, profile enrichment is not usually the main business purpose of this integration. The practical value for most customers is attendee availability inside Event Cadence and correct assignment to groups.
At the end of the integration process, Event Cadence will contain attendees from CVent in the target Event Cadence event.
The expected result is that:
- CVent registrants exist as attendees in Event Cadence.
- Attendees are assigned to one or more Event Cadence groups.
- Event Cadence administrators can use those groups to control the event experience.
- Attendees can access the correct event content, features, and communications based on their group assignment.
Groups are a key part of Event Cadence event configuration. They are commonly used to control what different attendee audiences can see or do inside the event website and mobile apps.
Group assignment can affect:
- Schedule item visibility.
- Access to agenda tracks or private sessions.
- Menu item visibility.
- Feature availability.
- Materials, files, videos, pages, and downloadable content visibility.
- Notification and communication targeting.
- Appointment-related eligibility and visibility, when applicable.
- Reporting and segmentation.
Because of this, the CVent attendees feed is not only about transferring a list of names. It also allows registration data from CVent to drive the Event Cadence attendee experience.
For example, if CVent identifies a registrant as a Speaker, Sponsor, Internal Team Member, VIP, HCP, Attendee, or another attendance category, Event Cadence can use that information to place the person into the appropriate Event Cadence group. That group can then determine which schedule items, files, menu options, or notifications are available to that person.
Event Cadence groups can be mapped from different types of CVent registration data, depending on how the customer’s CVent event is configured.
Several CVent fields or attributes can participate in group mapping at the same time. This means one attendee can be assigned to multiple Event Cadence groups during the same integration run. For example, an attendee may be assigned to one group based on their registration type, another group based on an answer to a registration question, and an additional group based on a custom field value.
Common group-mapping sources include:
- CVent registration type.
- CVent admission item or attendee type.
- CVent custom fields.
- CVent registration questions.
During setup, Event Cadence and the customer confirm which CVent fields or attributes should be used for group distribution, and how each value should translate into one or more Event Cadence groups.
Example mapping:
Registration Question: VIP Access
Registration Question: Breakout Track
The exact mapping is customer-specific and should be confirmed before the integration is activated.
Because multiple mapping rules can apply at once, the final attendee group list can be cumulative. For example, the same attendee could be placed into Attendees, Europe Group, and Track A Access if their CVent record satisfies all three mapping rules.
Event Cadence can currently communicate with CVent using two methods:
CVent REST API.
CVent SOAP API.
The correct method depends on the customer’s CVent account, available API access, and existing CVent configuration.
For CVent accounts using the REST API, Event Cadence can connect to CVent and pull registrant data on a timer-based schedule.
The feed is typically scheduled to run periodically. As the event date approaches, Event Cadence may increase the polling frequency so that late registrations and registration changes are reflected more quickly inside Event Cadence.
A typical REST API flow is:
Event Cadence authenticates against CVent using API credentials.
Event Cadence requests registrant or attendee data from CVent.
Event Cadence identifies the target Event Cadence event.
Event Cadence creates or updates event attendee records.
Event Cadence assigns attendees to groups based on the configured mapping rules.
Event Cadence repeats the process on a schedule.
For REST API access, Event Cadence needs the following credentials from the customer’s CVent Developer Portal:
These credentials are used for server-to-server authentication between Event Cadence and CVent. In practical terms, they allow Event Cadence to request an access token from CVent and then use that token to call the relevant CVent API endpoints.
The customer’s CVent administrator or technical team can create or manage these credentials in the CVent Developer Portal.
One easy way to complete this setup is to invite an Event Cadence engineer to the customer’s CVent Developer Portal. The Event Cadence engineer can then configure the required application credentials and confirm the correct API access, reducing back-and-forth during implementation.
In addition to the Client ID and Client Secret, Event Cadence may need:
- The CVent environment or region used by the customer account.
- The CVent event identifier.
- Confirmation that the API application has access to the required registrant or attendee data.
- Any required API scopes or permissions.
- The field or fields that should drive Event Cadence group assignment.
- Sample registrant data for mapping validation.
Some CVent customers may still use the SOAP API. This is usually because they have existing legacy integrations, older account configurations, or internal processes that were built before the newer REST API was adopted.
Cvent’s current public documentation identifies SOAP as a legacy API and directs new development toward REST API. However, some customers still have SOAP-based access or existing SOAP integrations in place, so Event Cadence can support this method when needed.
With SOAP API integration, Event Cadence can authenticate to CVent using SOAP credentials, retrieve registrant data, and process attendees into the target Event Cadence event using the configured mapping rules.
For SOAP API access, Event Cadence needs:
- AccountNumber.
- UserName.
- Password.
These credentials are used by Event Cadence to authenticate with the CVent SOAP API. Customers must contact CVent Support to obtain or confirm the correct SOAP API credentials for their account.
To enable the integration, Event Cadence needs enough information to connect to CVent, identify the correct event, retrieve registrants, and assign them to the correct Event Cadence groups.
The Event Cadence event must be created before attendee data can be loaded.
Event Cadence needs to know:
- Which Event Cadence event should receive the CVent attendees.
- The corresponding CVent event name or event identifier.
- Whether attendees should be active immediately or held until a specific launch date.
- Whether imported attendees should receive platform access automatically or only after communications are sent.
Group mapping is an optional but powerful setup step when the customer wants CVent registration data to control attendee segmentation, access, visibility, or communication targeting in Event Cadence.
Event Cadence needs to know:
- Which CVent field controls group assignment.
- Which CVent values map to which Event Cadence groups.
- Which CVent fields or attributes should participate in group assignment.
- Whether each field can assign one group or multiple groups.
- Whether one attendee can belong to multiple groups based on several CVent values at the same time.
- What should happen when a CVent value is empty or unknown.
- Whether group membership should be updated on each feed run.
- Whether manual group changes in Event Cadence should be preserved or overwritten by the feed.
The customer should provide sample values from CVent so the mapping can be validated before go-live.
Not necessarily. The integration creates or updates attendees and group assignments in Event Cadence. Whether attendees receive invitation emails, login instructions, or notifications depends on the event communication plan and platform configuration.
No. While some attendee fields may be transferred, the primary purpose is to populate the Event Cadence attendee list and assign attendees to the correct groups.
Groups are used throughout Event Cadence to control schedule access, menu visibility, feature availability, material visibility, file access, notification targeting, and other event-specific behavior.
Yes. REST API-based integrations commonly run on a timer, and the frequency can be adjusted based on the event timeline and operational needs.
If an attendee cancels in CVent, they will be removed from the Event Cadence attendee list during the next successful integration run.
No. Group mapping is not required for the integration to run. Event Cadence can import CVent registrants as event attendees without applying group mapping. Group mapping is used when the customer wants CVent registration data to automatically control attendee segmentation, access, visibility, or notification targeting in Event Cadence.
Yes. Several CVent fields or attributes can participate in group mapping at the same time. For example, the same attendee can be assigned to one group based on registration type, another group based on a registration question, and another group based on a custom field value.
Email address is required. Event Cadence matches incoming CVent registrants to Event Cadence attendees by email address, and email is treated as the primary attendee identifier for this integration.
The attendee cannot be reliably matched or created through the integration without an email address. The CVent registration record should include a valid attendee email before it can be processed correctly by Event Cadence.
Yes. Group mapping can use multiple CVent fields at the same time, including registration type, custom fields, registration questions, or similar attributes. Each configured rule can assign the attendee to a different Event Cadence group.