This page contains the setup guide and reference information for the eShow integrations.
Prerequisites
An active eShow account with a list of events (ensure you have access, especially if you are not the owner)
Setup guide
Step 1: Set up the eShow 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 eShow from the list of integrations.
To activate the integration, you will need two parameters, and these will be supplied by eShow.
API Key
Endpoint Url
Select your event for integration - The integration displays all events your account has access to, including upcoming and past events.
Your eShow 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 eShow integration supports the following sync modes :
Feature | Supported? |
Yes | |
Yes |
Supported streams
This integration is supporting the following eShow streams
eShow DOES NOT provide any online documentation.
Capturing deleted records
The eShow integration DOES NOT capture deletions for records in Speakers, Sessions, Attendees streams.
When a record is deleted on eShow, 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 eShow, the integration will replicate these dependencies within Swapcard.
The eShow integration automatically establishes a connection between Speakers from eShow and their corresponding Sessions from eShow.
This integration utilizes the KEY_ID field from the Sessions & GUID field from the Speakers stream as the primary identifier.
The KEY_ID field of [Sessions] serves as the primary identifier for uniquely linking records. These linked records are stored within the Client Id field on the Sessions record on the Swapcard side.
Streams supporting fields
Speakers
Speakers Fields | Label | Type |
| "Address 1" |
|
| "Address 2" |
|
| "City" |
|
| "Company Name" |
|
| "Country" |
|
| "Credentials" |
|
| "Custom Member Number" |
|
| "Display Property" |
|
| "Email" |
|
| "First Name" |
|
| "GUID" |
|
| "Last Name" |
|
| "Member Number" |
|
| "Middle Name" |
|
| "Phone" |
|
| "Profile Picture" |
|
| "Salutation" |
|
| "State" |
|
| "Title" |
|
| "Twitter Handle" |
|
| "Updated" |
|
| "Website" |
|
| "Work Phone" |
|
| "Zip" |
|
Sessions
Sessions Fields | Label | Type |
| "Active" |
|
| "CE Credits" |
|
| "Class Code" |
|
| "Class End" |
|
| "Class Key" |
|
| "Class Start" |
|
| "Description" |
|
| "Display Group" |
|
| "Display Order" |
|
| "Do Not Display" |
|
| "Fee Code" |
|
| "Glance" |
|
| "Key ID" |
|
| "Maximum Seats" |
|
| "Paid" |
|
| "Parent Key" |
|
| "Room" |
|
| "Room Capacity" |
|
| "Room Level" |
|
| "Session Code" |
|
| "Session Code 2" |
|
| "Session Link" |
|
| "Speaker" |
|
| "Title" |
|
| "Track" |
|
| "Track Key" |
|
| "Type" |
|
| "Updated" |
|
| "Venue" |
|
Attendees
Attendees Fields | Label | Type |
| "Registration Date" |
|
| "Badge ID" |
|
| "Badge Name" |
|
| "Salutation" |
|
| "First Name" |
|
| "Middle Name" |
|
| "Last Name" |
|
| "Suffix" |
|
| "Email" |
|
| "Assistant Email" |
|
| "Credentials" |
|
| "Company Name" |
|
| "Title" |
|
| "Address 1" |
|
| "Address 2" |
|
| "City" |
|
| "State" |
|
| "Zip" |
|
| "Country" |
|
| "Phone" |
|
| "Home Phone" |
|
| "Cell Phone" |
|
| "Work Phone" |
|
| "Fax" |
|
| "Twitter Handle" |
|
| "Role Type" |
|
| "Status" |
|
| "AMS Order Number" |
|
| "Badge Printed" |
|
| "Form Title" |
|
| "Group Registration" |
|
| "Primary Group ID" |
|
| "Custom Member Number" |
|
| "Member Number" |
|
| "Sync ID" |
|
| "Member Status" |
|
| "Member Type" |
|
| "Profile Picture" |
|
| "Total Discount" |
|
| "Total Payment" |
|
| "Total Sales" |
|
| "Balance Due" |
|
| "Updated" |
|
| "Registered By User" |
|
| "Session Scan List" |
|
Limitations & Troubleshooting
Connector limitations
Maintenance
The eShow 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
Modifications in External ID
In eShow, the BADGE_ID field serves as the unique identifier for each profile. However, a limitation of the eShow system is that the same BADGE_ID can be reused for different profiles across multiple events. This can potentially cause mismatches in profile data when integrating with Swapcard.
To prevent this, Swapcard has implemented a solution where the BADGE_ID is combined with the unique Swapcard Event ID to generate a distinct identifier for each profile. This combined identifier follows the format:
SwapcardEventID-BADGE_ID
By appending the Swapcard EventID to the BADGE_ID, we ensure that each profile in the Swapcard database has a unique identifier, even if the same BADGE_ID is reused across different events in eShow.
Changelog
Version | Date | Subject |
1.0.19 | 2023-10-03 | 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.