This page contains the setup guide and reference information for the ASP Events integrations.
Prerequisites
An active ASP Events account with a list of events (ensure you have access, especially if you are not the owner)
Setup guide
Step 1: Set up the ASP Events 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 ASP Events from the list of integrations.
To activate the integration, you will need two parameters, and these will be supplied by ASP Events.
API Key
Password
Select your event for integration - The integration displays all events your account has access to, including upcoming and past events.
Your ASP Events 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 ASP Events integration supports the following sync modes :
Feature | Supported? |
Yes |
Supported streams
This integration is supporting the following ASP Events streams
ASP Events documentation is accessible here.
Capturing deleted records
The ASP Events integration ONLY capture deletions for records in the Sessions streams.
For all others records and strams (Exhibitors) when a record is deleted on ASP Events, 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 ASP Events, the integration will replicate these dependencies within Swapcard.
Speakers → Sessions
The ASP Events integration automatically establishes a connection between Speakers from ASP Events and their corresponding Sessions from ASP Events.
This integration utilizes the Uuid field from the Sessions & Uuid field from the Speakers stream as the primary identifier.
The Uiid 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.
Exhibitors -> Contacts → Exhibitors
The ASP Events integration automatically establishes a connection between Exhibitors -> Contacts from ASP Events and their corresponding Exhibitors from ASP Events.
This integration utilizes the Contacts field from the Exhibitors & Uuid from the Contact as the primary identifier.
The Uiid field of Exhibitors -> Contacts serves as the primary identifier for uniquely linking records. These linked records are stored within the Client Id field on the Profile record on the Swapcard side.
Streams supporting fields
Speakers
Speakers Fields | Mapping Label | Type |
| "First Name" |
|
| "Last Name" |
|
| "Email" |
|
| "Job title" |
|
| "Company" |
|
| "Description" |
|
| "Photo" |
|
| "Speaker Type" |
|
| "Title" |
|
| "Awards" |
|
| "Code" |
|
Exhibitors
Exhibitor Fields | Mapping Label | Type |
| "Name" |
|
| "Description" |
|
| "Logo" |
|
| "Website" |
|
| "Country" |
|
| "Address" |
|
| "Booth" |
|
| "Email" |
|
| "Linkedin" |
|
| "Twitter" |
|
| "Facebook" |
|
| "Youtube" |
|
| "Instagram" |
|
| "Status Name" |
|
| "Site Name" |
|
| "Site URL" |
|
| "Site UUID" |
|
| "Site Self href" |
|
Sessions
Sessions Fields | Mapping Label | Type |
| "Title" |
|
| "Start date" |
|
| "End date" |
|
| "Description" |
|
| "Streams" |
|
| "Location" |
|
| "Abstract" |
|
| "Session Code" |
|
| "Session ID" |
|
| "Session Categories" |
|
| "Session Seminar" |
|
| "Session Type" |
|
Exhibitors -> Contacts
Exhibitor Contacts Fields | Mapping Label | Type |
| "First Name" |
|
| "Last Name" |
|
| "Primary Email" |
|
| "Primary Phone" |
|
| "Name" |
|
| "Profile Image" |
|
| "Username" |
|
| "Job Title" |
|
| "Is main contact?" |
|
| "Last Login" |
|
| "Client Reference" |
|
Limitations & Troubleshooting
Connector limitations
Incremental Sync - Overwrite
Integration with ASP Events 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 |
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.