This page contains the setup guide and reference information for the DIA Global integrations.
Prerequisites
An active DIA Global account with a list of events (ensure you have access, especially if you are not the owner)
Setup guide
Step 1: Set up the DIA Global 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 DIA Global from the list of integrations.
To activate the integration, you will need three parameters, and these will be supplied by DIA Global.
Username : The Username on the DIA Global end.
Password : The Password on the DIA Global end.
Event Code : The Event Code on the DIA Global end.
Select your event for integration - The integration displays all events your account has access to, including upcoming and past events.
Your DIA Global 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 DIA Global integration supports the following sync modes :
Feature | Supported? |
Yes | |
Yes |
Supported streams
This integration is supporting the following DIA Global streams
DIA Global does NOT provide any online documentation.
Capturing deleted records
The DIA Global integration does NOT capture deletions for records in the Speakers, Sessions, Exhibitors, People streams.
When a record is deleted on DIA Global, 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 DIA Global, the integration will replicate these dependencies within Swapcard.
Speakers β Sessions
The DIA Global integration automatically establishes a connection between Speakers from DIA Global and their corresponding Sessions from DIA Global.
This integration utilizes the Speaker_ID
field from the Speakers stream as the primary identifier and Session_id
field from the Sessions stream as the primary identifier.
The Session_id
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
Sessions
Sessions Field | Mapping Label | Type |
| "Track Name" |
|
| "Session Name" |
|
| "Description" |
|
| "Venue" |
|
| "Product Code" |
|
| "Session Number" |
|
| "Room Number" |
|
| "CE" |
|
| "Session Level" |
|
| "Component Type" |
|
| "URL" |
|
| "Featured Topics" |
|
| "Interest Area" |
|
| "Start Date Time" |
|
| "Multi Tracks" |
|
| "End Date Time" |
|
Exhibitors
Exhibitors Field | Mapping Label | Type |
| "Company Name" |
|
| "Booth Number" |
|
| "Contact First Name" |
|
| "Contact Last Name" |
|
| "Email" |
|
| "Web Address" |
|
| "Phone" |
|
| "Company Profile" |
|
| "Other Attributes" |
|
| "Country" |
|
| "Services" |
|
| "Product ID" |
|
| "Exhibitor ID" |
|
| "Company ID" |
|
| "Image ID" |
|
Attendees
Attendees Field | Mapping Label | Type |
| "Customer ID" |
|
| "Customer Class Code" |
|
| "Badge ID" |
|
| "First Name" |
|
| "Last Name" |
|
| "Title" |
|
| "Company Name" |
|
| "Address Line 1" |
|
| "Address Line 2" |
|
| "State" |
|
| "Postal Code" |
|
| "Country" |
|
| "Email" |
|
| "Primary Phone" |
|
| "Core" |
|
| "Grip Opt In" |
|
| "Share Data" |
|
| "Days Attending" |
|
| "Sub Events" |
|
Speakers
Speakers Field | Mapping Label | Type |
| "First Name" |
|
| "Last Name" |
|
| "Company Name" |
|
| "Title" |
|
| "Bio" |
|
| "Email" |
|
| "Type" |
|
| "Session ID" |
|
| "Speaker ID" |
|
| "Image ID" |
|
| "Country Code" |
|
| "Person Disclosure" |
|
Limitations & Troubleshooting
Connector limitations
Maintenance
The DIA Global 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.0.23 | 2025-02-13 | 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.