This page contains the setup guide and reference information for the eShow integrations.

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.

The eShow integration supports the following sync modes :

This integration is supporting the following eShow streams

In addition to Speakers, Sessions, and Attendees, the integration also supports importing Exhibitors and their Exhibitor Members (booth contacts). Exhibitors are imported as Swapcard exhibitors, and each booth contact is imported as a person and linked to the exhibitor as a team member.

eShow DOES NOT provide any online documentation.

The eShow integration DOES NOT capture deletions for records in Speakers, Sessions, Attendees, Exhibitors, or Exhibitor Members streams.

When a record is deleted on eShow, it needs to be MANUALLY deleted on Swapcard accordingly.

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.

The eShow integration also establishes a connection between Exhibitor Members (booth contacts) and their corresponding Exhibitors. Each booth contact listed on an exhibitor is imported as a person and added to that exhibitor as a team member.

This integration utilizes the COMPANY_KEY field from the Exhibitors stream as the primary identifier. This linked record is stored within the Client Id field on the Exhibitor record on the Swapcard side. Booth contacts use a combined identifier of EMAIL and COMPANY_KEY (EMAIL-COMPANY_KEY) as the Client Id, so the same contact remains a single Swapcard person across syncs.

eShow exhibitors purchase a listing package, returned inside the exhibitor's SALES_ITEMS array. The integration exposes the package via the Package Product ID field (SALES_ITEMS.PRODUCT_ID), which resolves to the list of product IDs across an exhibitor's sales items.

All approved exhibitors are imported regardless of package. To route upgraded exhibitors to a dedicated Swapcard group, configure a group-assignment rule on the Exhibitors object:

Exhibitors whose sales items include a PRODUCT_ID of Elite (the "Exhibitor Listing - Elite Upgrade" item) are assigned to the configured group; all others fall back to the default group.

Exhibitors are returned by the Exhibitor_List method with sales items included. Only exhibitors with a STATUS of Approved are imported. The COMPANY_KEY field is the unique identifier (stored as the Client Id on the Swapcard exhibitor).

The ADDRESS field is composed from the exhibitor's ADDRESS1 and ADDRESS2. SURVEY_DATA: fields read directory survey answers by question title. SALES_ITEMS.PRODUCT_ID is used for group assignment (see Exhibitor Group Assignment by Package Tier).

Exhibitor Members are the booth contacts (BOOTH_CONTACTS) listed on each exhibitor. Each contact is imported as a person and linked to its exhibitor as a team member, using EMAIL-COMPANY_KEY as the unique identifier.

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

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.

Similarly, for Exhibitor Members, the booth contact's EMAIL is combined with the exhibitor's COMPANY_KEY (EMAIL-COMPANY_KEY) to form a unique identifier. The EMAIL and COMPANY_KEY must remain consistent throughout the life of the event so that a contact continues to resolve to the same Swapcard person.

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.