This page contains the setup guide and reference information for the Cvent Event Management integrations.

Your Cvent event has been successfully linked with your Swapcard event.

You have the flexibility to adjust your integration settings according to the specific data requirements. It's crucial to highlight that the synchronization will only begin when you manually start the integration process and finish the necessary mapping.

The Cvent integration supports the following sync modes :

This integration is supporting the following Cvent streams

Cvent documentation is accessible here.

The Cvent integration does NOT capture deletions for records in the Attendees, Audience Segments, Exhibitors, Exhibitor Admins, and Exhibitor Booth Staff streams.

When a record is deleted on Cvent, it needs to be MANUALLY deleted on Swapcard accordingly.

The id of Attendees is employed as the main identifier to uniquely link records and store them within the Client Id field on the Swapcard side.

Attendees can be imported into Swapcard using two methods:

Both methods use the same attendee field mappings (see the Attendees fields table below) and import people with identical capabilities. The key difference is how attendees are selected:

An attendee may appear in multiple audience segments. If the same attendee is included in more than one enabled audience segment, the attendee record will be synced for each segment independently.

Note: The following API scopes must be enabled on your Cvent API credential depending on the import method used. You can configure scopes when creating or editing your Application in the Cvent Developer Portal.

The Cvent integration automatically establishes a connection between Exhibitor Admins from Cvent and their corresponding Exhibitors from Cvent.

This integration utilizes the id field from the Exhibitor Admins stream as the primary identifier. The exhibitor.id field is used to link each admin to its parent Exhibitor record on the Swapcard side.

The Cvent integration automatically establishes a connection between Exhibitor Booth Staff from Cvent and their corresponding Exhibitors from Cvent.

Booth Staff records reference an attendee.id which links to the Attendee stream and an exhibitor.id which links to the parent Exhibitor. The attendee contact information is used to populate the People record, and the exhibitor relationship is replicated within Swapcard.

The integration exclusively imports registrants with a status configured as Accepted (applies to both registration type and audience segment based imports).

The integration imports exhibitors and filters out records with hidden set to true. The id of Exhibitors is employed as the main identifier to uniquely link records and store them within the Client Id field on the Swapcard side.

Exhibitor Admins are imported as People records linked to their parent Exhibitor. The id of each Exhibitor Admin is employed as the main identifier to uniquely link records and store them within the Client Id field on the Swapcard side.

Exhibitor Booth Staff are imported as People records linked to their parent Exhibitor. Booth Staff records reference an Attendee, and the attendee's contact information is used to populate the People record fields. The attendee.id is employed as the main identifier to uniquely link records and store them within the Client Id field on the Swapcard side.

Booth Staff People records use the same field mappings as Attendees (see Attendees table above).

Integration with Cvent is subject to limitations imposed by the provider's API when it comes to incremental updates. The synchronization frequency is limited to the provider's API rate limits and the availability of the data.

Please be aware that any enhancements to this integration, which encompass any requirements not covered by the existing integration state, will be subject to custom development processes and associated costs.