This page contains the setup guide and reference information for the Maritz integrations.
Prerequisites
An active Maritz account with a list of events (ensure you have access, especially if you are not the owner)
Setup guide
Step 1: Set up the Maritz 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 Maritz from the list of integrations.
To activate the integration, you will need three parameters, and these will be supplied by Maritz.
password
showCode
username
Select your event for integration - The integration displays all events your account has access to, including upcoming and past events.
Your Maritz 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 Maritz integration supports the following sync modes :
Feature | Supported? |
Yes | |
Yes |
Supported streams
This integration is supporting the following Maritz streams
Maritz online documentation is accessible here.
Capturing deleted records
The Maritz integration DOES NOT capture deletions for records in Registrations streams.
When a record is deleted on Maritz, 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.
The RegistrantID field of Registrations serves as the primary identifier for uniquely linking records. These linked records are stored within the Client Id field on the Registrations record on the Swapcard side.
Streams supporting fields
Registrations
Registrations Fields | Label | Type |
| "firstName" |
|
| "title" |
|
| "prefix" |
|
| "lastName" |
|
| "company" |
|
| "company2" |
|
| "companyCode" |
|
| "degree" |
|
| "exCompanyExID" |
|
| "middle" |
|
| "phone" |
|
| "phone2" |
|
| "fax" |
|
| "email" |
|
| "Member type" |
|
| "Member number" |
|
| "member category" |
|
| "address" |
|
| "exCompanyID" |
|
| "ZipCode" |
|
| "City" |
|
| "StateCode" |
|
| "CountryCode" |
|
| "Registrant ID" |
|
| "Show Item Code" |
|
| "Show Item List" |
|
Limitations & Troubleshooting
Connector limitations
Modifications in External ID
In Maritz, the RegistrantID field serves as the unique identifier for each profile. However, a limitation of the Maritz system is that the same RegistrantID 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 RegistrantID is combined with the unique Swapcard Event ID and Event ExternalID to generate a distinct identifier for each profile. This combined identifier follows the format:
RegistrantID-EventExternalID-EventID
By appending the Swapcard EventID and Event ExternalID to the RegistrantID, we ensure that each profile in the Swapcard database has a unique identifier, even if the same RegistrantID is reused across different events in Maritz.
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.