This page contains the setup guide and reference information for the Bizaboo integrations.
Prerequisites
An active Bizaboo account with a list of events (ensure you have access, especially if you are not the owner)
Setup guide
Step 1: Set up the Bizaboo 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 Bizaboo from the list of integrations.
To activate the integration, you will need one parameter, and these will be supplied by Bizaboo.
API Key : The API Key on the Bizaboo end.
Select your event for integration - The integration displays all events your account has access to, including upcoming and past events.
Your Bizaboo 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 Bizaboo integration supports the following sync modes :
Feature | Supported? |
Yes | |
Yes |
Supported streams
This integration is supporting the following Bizaboo streams
Capturing deleted records
The Bizaboo integration does NOT capture deletions for records in the Speakers, Registrations, Sessions, Partners streams.
When a record is deleted on Bizaboo, 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 Speakers are associated with Sessions on Bizaboo, the integration will replicate these dependencies within Swapcard.
Speakers → Sessions
The Bizaboo integration automatically establishes a connection between Speakers from Bizaboo and their corresponding Sessions from Bizaboo.
This integration utilizes the speakerId field from the Speakers stream as the primary identifier and id field from the Sessions stream as the primary identifier.
The speakerId field of Speakers serves as the primary identifier for uniquely linking records. These linked records are stored within the Client Id field on the Session record on the Swapcard side.
Streams supporting fields
Speakers
Speakers Field | Mapping Label | Type |
| "First Name" |
|
| "Last Name" |
|
| "Email" |
|
| "Job title" |
|
| "Company" |
|
| "Biography" |
|
| "Photo" |
|
| "Website" |
|
| "Linkedin" |
|
| "Twitter" |
|
Partners
Exhibitor Field | Mapping Label | Type |
| "Name" |
|
| "Description" |
|
| "Logo" |
|
| "Website" |
|
| "Type" |
|
| "Booth" |
|
| "Contact email" |
|
| "Contact phone number" |
|
| "Linkedin" |
|
| "Twitter" |
|
| "Facebook" |
|
Sessions
Session Field | Mapping Label | Type |
| "Title" |
|
| "Start date" |
|
| "End date" |
|
| "Description" |
|
| "Description HTML" |
|
| "Status (Hidden)" |
|
| "Location" |
|
Limitations & Troubleshooting
Connector limitations
Maintenance
The Bizaboo 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
Changelog
Version | Date | Subject |
1.1.3 | 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.