This page contains the setup guide and reference information for the A2Z Events - Personify integrations.
Prerequisites
An active A2Z Events - Personify account with a list of events (ensure you have access, especially if you are not the owner)
Setup guide
Step 1: Set up the A2Z Events - Personify 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 A2Z Events - Personify from the list of integrations.
To activate the integration, you will need four parameters, and these will be supplied by A2Z Events - Personify.
Event code
xTenantId
Attendee API Key (Optional)
Event UUID (Optional)
Select your event for integration - The integration displays all events your account has access to, including upcoming and past events.
Your A2Z Events - Personify 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 A2Z Events - Personify integration supports the following sync modes :
Feature | Supported? |
Yes |
Supported streams
This integration is supporting the following A2Z Events - Personify streams
The online documentation of A2Z Events - Personify is accessible here.
Other documentations available are :
Capturing deleted records
The A2Z Events - Personify integration does NOT capture deletions for records. When a record is deleted on A2Z Events - Personify, it needs to be MANUALY deleted on Swapcard accordingly.
Object Mappings
The A2Z Events - Personify integration provides a list of available objects for mapping, which is generated from ExhibitorInformation.
For the Swapcard integration, one object is created to be mapped per UpgradeLevelID.
The object name corresponds to UpgradeLevelDescription on ExhibitorInformation.
Stream Dependencies
In the context of integration functionalities, records are automatically linked with their corresponding records within Swapcard. For instance, if ExhibitorInformation are associated with Company Information on A2Z Events - Personify, the integration will replicate these dependencies within Swapcard.
ExhibitorInformation → Company Information
The A2Z Events - Personify integration automatically establishes a connection between ExhibitorInformation from A2Z Events - Personify and their corresponding Company Information from A2Z Events - Personify.
This integration utilizes the coId field from the ExhibitorInformation stream as the primary identifier.
The coId field of ExhibitorInformation serves as the primary identifier for uniquely linking records. These linked records are stored within the Client Id field on the Exhibitor record on the Swapcard side.
Subsequently, Company Information is utilized to generate the appropriate Exhibitor Members on the Swapcard side.
The coId and email field of Company Information functions as the primary identifier for uniquely linking records. These linked records are stored within the Client Id field on the People record on the Swapcard side.
Importing attendees is optional. However, if they are imported, the barcodes field of an Attendee serves as the primary identifier for uniquely linking records. These linked records are then stored in the Client Id field of the Exhibitor record on the Swapcard side.
Streams supporting fields
Exhibitor Information
Exhibitor Field | Mapping Label | Type |
| Booth ID (Not to be used for Client ID) |
|
| Company ID |
|
| Booth Number |
|
| Event ID |
|
| Contact Email |
|
| Contact City |
|
| Contact Country |
|
| Contact Zip |
|
| Contact Address 1 |
|
| Contact Address 2 |
|
| Contact State |
|
| Booth number |
|
| Company number |
|
| Welcome message |
|
| Print Profile |
|
| Online profile |
|
| Exhibiting as |
|
| Booth Size |
|
| Badge allotment (free) |
|
| Badge allotment (max) |
|
| Booth status |
|
| Booth map ID |
|
| Booth Pavlion code |
|
| Hall code |
|
| Sub expo code |
|
| Web URL |
|
| Brands |
|
| Co Exhibitor |
|
| Upgrade level ID |
|
| Upgrade level description |
|
| Parent booth ID |
|
| Date modified |
|
| Custom Badge Allotment 1 |
|
| Custom Badge Allotment 2 |
|
| Custom Badge Allotment 3 |
|
| Custom Badge Allotment 4 |
|
| Product categories |
|
| Custom fields |
|
Company Information
ExhibitorMemberStandard Field | Mapping Label | Type |
| ContactFName |
|
| ContactLName |
|
| ContactEmail |
|
| ContactPrefix |
|
| ContactSuffix |
|
| ContactTitle |
|
| ContactCompany |
|
| ContactAdd1 |
|
| ContactAdd2 |
|
| ContactCity |
|
| ContactState |
|
| ContactZip |
|
| ContactCountry |
|
| ContactPhone |
|
| ContactFax |
|
| ContactURL |
|
| Contact Types |
|
Attendees
Attendee Standard Field | Mapping Label | Type |
| Registration Type |
|
| Age Range |
|
| Are you more interested in buying or selling products? |
|
| Industry Sectors |
|
| Specify Sector(s) You Seek to Purchase… |
|
| Company Size |
|
| Buying Decision |
|
| Company Information - Number of Years Established |
|
| Registrant Id |
|
| First Name |
|
| Last Name |
|
|
| |
| Job Title |
|
| Company Name |
|
| City |
|
| State |
|
| Country |
|
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.
Filtering Records by Contact Type
To filter records by Contact Type, use the in operator when defining the filter criteria.
Maintenance
The A2Z Events - Personify 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 |
0.0.9 | 2023-03-28 | Maintenance |
Read more

