MapYourShow Exhibitor Field Mapping

The default mapping ExpoPlatform uses when reading exhibitor records from MapYourShow, plus the MapYourShow-specific composite fields for Marketing Contact, Custom Question, and Product Categories.

MapYourShow returns records as JSON objects with nested arrays (booths, additionalcontacts, product categories), so external paths use standard dot notation to reach into nested values.

Default mapping

The default mapping is what ships with the MapYourShow integration. You can override or extend any row through the Field Mapping tab on the MapYourShow configuration page.

MapYourShow field	ExpoPlatform target	Notes
`exhid`	External ID (identity)	Used for exhibitor identity matching across syncs
`exhname`	Company Name
`email`	Email	Owner-account email. Marketing Contact Email overrides this — see below.
`country`	Country	Matched by country name, resolved to an ISO code
`city`	City
`zip`	Zip / Postal Code
`address1`	Address
`phone`	Phone
`website`	Company Website
`newexhibitor`	Is New	Boolean flag
`leadprofile`	Exhibitor Category	Mapped to an ExpoPlatform exhibitor category through the integration's Category Mapping setting
`booths.0.hall`	Hall	First booth entry only — see First booth only below
`booths.0.boothnumber`	Stand / Booth Number	First booth entry only
`additionalcontacts`	Marketing Contact (composite)	Populates the five Contact Person fields from the first Marketing Contact entry

Not in the default mapping: Product Categories and Custom Questions. Add them as extra rows in the Field Mapping tab when the event needs them.

Country matching

Country is matched by name, then resolved to an ISO code. If MapYourShow returns country names that don't match ExpoPlatform's Countries catalogue, the record is still saved — without a country, and without its City and Region values. See Country Field for the full behaviour.

Integration-specific fields

Marketing Contact (composite)

What it does: Reads a single Marketing Contact entry from the MapYourShow additionalcontacts array and writes its details to the five Contact Person fields on the ExpoPlatform exhibitor in one go. Saves configuring five separate rows for Name, Surname, Position, Email, and Phone.

ExpoPlatform targets: Contact Person Name, Contact Person Surname, Contact Person Position, Contact Person Email, and Contact Person Phone — all on the exhibitor record.

Behaviour: Filters the additionalcontacts array to entries flagged as Marketing Contact in MapYourShow (contact type 2). The first matching entry is used; later Marketing Contact entries are ignored. If no Marketing Contact is present, none of the five Contact Person fields are written by this rule.

Configuration: None at the client level. The field is hard-wired to the Marketing Contact role.

Worked example — a source exhibitor with:

JSON

"additionalcontacts": [
  { "contacttypeid": 1, "fname": "Pat", "lname": "Doe" },
  { "contacttypeid": 2, "fname": "Sam", "lname": "Lee", "title": "VP Marketing", "email": "sam@example.com", "phone": "+1-555-0123" }
]

produces Contact Person Name = Sam, Contact Person Surname = Lee, Contact Person Position = VP Marketing, Contact Person Email = sam@example.com, Contact Person Phone = +1-555-0123. The type-1 entry is ignored.

Marketing Contact Email

What it does: Companion to the Marketing Contact composite. Extracts the email from the same Marketing Contact entry and writes it as the owner-account email, overriding whatever the standard Email field produced.

ExpoPlatform target: Owner-account email.

Behaviour: Runs after the standard Email field and overwrites its value. The owner-account email ends up reflecting the Marketing Contact's email when one exists, falling back to the company-level email when none does.

Configuration: None at the client level.

Custom Question

What it does: Maps a single MapYourShow custom-question answer to a named ExpoPlatform custom field. MapYourShow delivers custom-question answers as a delimited string of labels (for example, Woman-Owned||Black-Owned); this field splits the string and matches each label to an option value on the configured custom field.

ExpoPlatform target: A named custom field on the per-event participation record.

Behaviour: Not in the default mapping. Add a row in the Field Mapping tab pointing at a single MapYourShow custom-question source path.

Options:

Option	What it does	Default
Custom Field Name	The ExpoPlatform custom field to write to. Required.	—
Separator	The delimiter used to split the MapYourShow answer string.	`\|\|`

Value handling:

Labels that match an option on the target custom field are written (case-insensitive)
Labels that don't match any option are skipped silently
An empty or missing source value is a no-op

Product Categories

What it does: Maps an array of MapYourShow product-category IDs to ExpoPlatform Product Categories on the exhibitor. The MapYourShow-side IDs are translated through the per-event Product Categories Mapping table (managed on the Exhibitor Settings tab — see the MapYourShow integration page for how to import the CSV).

ExpoPlatform target: The exhibitor's Product Categories collection.

Behaviour: Not in the default mapping. Add a row in the Field Mapping tab pointing at the source array of category objects, after populating the Product Categories Mapping panel for the event.

Options:

Option	What it does	Default
Category ID Path	Dot-notation path within each category object to the source-side ID	`categoryid`

Value handling:

Source array state	Mapping table state	Result
Present but empty	Any	Existing Product Categories on the ExpoPlatform exhibitor are cleared
Has IDs, but none match the mapping	Has entries	Existing Product Categories are preserved
Has IDs, some or all match the mapping	Has entries	Mapped ExpoPlatform Product Categories are applied
Has IDs	Empty	Same as none-match — existing categories preserved

See Product Categories Field in the Field Mapping Reference for the shared behaviour that applies to all integrations using this field type.

Notable behaviours

Marketing Contact email overrides the company email

The standard Email field maps the company-level email field of every MapYourShow exhibitor record to the owner-account email. The Marketing Contact Email field runs after that and overwrites it whenever a Marketing Contact entry with an email exists in the same record.

The end result: the owner-account email reflects the Marketing Contact when one is present, and falls back to the company email when not. To check which value landed for a given exhibitor, inspect the additionalcontacts array for a type-2 entry with an email.

First booth only

The default mapping reads the first entry of the booths array for Hall and Stand. Exhibitors with multiple booths in MapYourShow will have only their first booth represented in the default ExpoPlatform mapping.

To capture all booths, swap the Hall and Stand rows for the multi-stand variant through the Field Mapping tab. See Stand and Stands Fields for the field types.

Product Categories require a two-step setup

Product Categories are not in the default mapping. Adding them is two steps:

Populate the Product Categories Mapping panel on Exhibitor Settings with the per-event MapYourShow-ID-to-ExpoPlatform-Product-Category translations (via CSV import).
Add a Product Categories row to the Field Mapping tab pointing at the source category array.

Skipping step 1 means source IDs won't match anything and existing Product Categories will be preserved on every sync — which can be confusing because the sync completes cleanly but no categories appear.

MapYourShow always sends the full profile

Unlike some integrations that support partial updates, every profile call to MapYourShow returns the exhibitor's full record. Update field mapping decisions are applied to the fetched values every time. Fields excluded from the update mapping are preserved in ExpoPlatform regardless of what MapYourShow returns.