Field Mapping Reference

Every native integration uses field mapping to decide which source-system fields go where in ExpoPlatform. Most fields are simple pass-throughs — you set the source path, pick the ExpoPlatform target, and the value flows across on every sync. Some fields, though, do more than that: resolve values against a lookup table, download and re-upload images, iterate over an array, link entities together.

The pages in this section document the field types that need more than a one-line description. Come here when a field isn't behaving the way you expect, or when you're setting up a mapping and want to know what options are available.

What's in this section

Field type	What it does
Custom Field	Writes a single value into a named ExpoPlatform custom field. Explains what happens when the source value is empty, blank, or missing.
Batch Custom Field	The array variant of Custom Field — iterates over source question objects and writes one custom field per entry. Powers custom-questions imports.
Country Field	Resolves the incoming value against ExpoPlatform's Countries catalogue. Explains ISO vs name matching, and how City and Region depend on the resolved Country.
Default Language Field	Sets the account's interface language. Includes the fixed lookup tables for ISO country codes and Aventri codes.
Product Categories Field	Fills the exhibitor's Product Categories from a source array. Read this together with the Product Categories Mapping shared setting.
Profile Image Field	Downloads the source image and uploads a copy to ExpoPlatform storage. Explains what happens when the download or upload fails.
Speaker Matching Field	Marks an account as a speaker when the source value matches a configured list. One-way — never removes the speaker role.
Stand & Stands Fields	The booth-placement family — Hall, Stand (single), and Stands (multiple). Explains how they interact.
Tags Field	Links pre-existing event tags to an exhibitor. Additive only — a sync never removes tags.
Team Member Matching Field	Adds visitors to an exhibitor's team based on a source field. See also the Team Member Matching shared setting.

Where field mapping is configured

Field mapping is configured per integration, per event, per entity. Open the integration's page in the admin UI (Admin → Integrations → integration name) and use the Field Mapping tab. Each mapping row pairs a source path (a field in the incoming record) with an ExpoPlatform target (the account, exhibitor, or event-participation field to write to).

The default mapping for each integration is documented on that integration's own page under Supported Integrations. You can override or extend it as needed.

Create mapping vs update mapping

Every field mapping row belongs to one of two sets:

Create mapping — applied once when a record is first imported.
Update mapping — applied every time the record is re-imported. Fields not included in the update mapping are preserved in ExpoPlatform.

See How Sync Works → What happens when a record is re-imported for the full picture.