This page contains the setup guide and reference information for the Cvent Onsite integrations.
Prerequisites
An active Cvent Onsite account with a list of events (ensure you have access, especially if you are not the owner)
Setup guide
Step 1: Set up the Cvent Onsite integration in Swapcard
Sign in to your Swapcard account.
Navigate to your Event page within the Communities section.
In the left navigation bar, go to Event Builder, then select Integrations.
On the integration selection page, choose cvent from the list of integrations.
To activate the integration, you will need the next parameters:
Event ID : The Event ID on the cvent onsite end.
Account ID : The Account ID on the cvent onsite end.
API key and secret(supplied by cvent)
Select your event for integration - The integration displays all events your account has access to, including upcoming and past events.
Your Cvent Onsite 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.
Supported sync modes
The Cvent Onsite integration supports the following sync modes :
Feature | Supported? |
Yes |
Supported streams
This integration is supporting the following Cvent Onsite streams
Cvent Onsite documentation is accessible here.
Capturing deleted records
The Cvent Onsite integration does NOT capture deletions for records in the /attendees and the /exhibitors streams.
When a record is deleted on Cvent Onsite, it needs to be MANUALY deleted on Swapcard accordingly.
Stream Dependencies
In the context of integration functionalities, records are automatically linked with their corresponding records within Swapcard. For instance, if Attendees are associated with Exhibitors on Cvent Onsite, the integration will replicate these dependencies within Swapcard.
Attendee → Exhibitors
The Cvent Onsite Country Events automatically establishes a connection between Attendee(ExhibitorMember)) from Cvent Onsite and their corresponding Event from Cvent Onsite.
This integration utilizes the Attendee.id field from the Attendee(ExhibitorMember) or Exhibitors.id field from the Exhibitors streams as the primary identifier.
The id field of Exhibitors serves as the primary identifier for uniquely linking records. These linked records are stored within the Client Id field on the Event record on the Swapcard side.
Streams supporting fields
Exhibitors as Exhibitors
Exhibitor Fields | Label | Type |
description | description | STRING |
name | name | STRING |
location | location | STRING |
address1 | address1 | STRING |
address2 | address2 | STRING |
country | country | STRING |
state | state | STRING |
city | city | STRING |
zip | zip | STRING |
phoneWork | Phone Work | STRING |
phoneMobile | Phone Mobile | STRING |
phoneOther | Phone Other | STRING |
STRING | ||
website | Website | STRING |
STRING | ||
STRING | ||
STRING | ||
profileLogoUrl | ProfileLogoUrl | STRING |
Attendee as People(ExhibitorMember)
People Fields | Label | Type |
id | id | STRING |
STRING | ||
firstName | firstName | STRING |
lastName | lastName | STRING |
Limitations & Troubleshooting
Connector limitations
Maintenance
The Cvent Onsite API is a private source API, which adds complexity to maintenance and may lead to stability issues. Despite these challenges, Swapcard offers a connector to facilitate seamless integration.
Incremental Sync
Integration with Cadium is subject to limitations imposed by the provider's API when it comes to incremental updates. The synchronization frequency is strictly limited to 1 hours
Changelog
Version | Date | Subject |
0.0.9 | 2023-03-28 | Maintenance |
Enhancement
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.
Read more