Team Member Matching Field

Adds visitors to an exhibitor's team. When this field is present in a visitor mapping, every matched visitor becomes a team member of the resolved exhibitor and is assigned an exhibitor role. Offered in visitor mappings across integrations.

Presence of this field in the mapping is what enables team-member behaviour for the integration. There's no separate enable toggle. Remove the field from the mapping to treat those visitors as regular attendees instead.

For the shared-setting overview and its role in the pipeline, see Team Member Matching.

ExpoPlatform target

Sets Exhibitor ID (the team link) and Exhibitor Role on the visitor's ExpoPlatform record. The visitor becomes a team member of that exhibitor on save.

Behaviour

The mapped source value is used to look up an exhibitor on the event (see the Matching Rule option). When the lookup succeeds, the field writes the exhibitor link and a role — Member by default, or Admin when the Admin Role Rule matches.

When the lookup fails, no exhibitor link is set and the record is still saved as a standalone visitor. The record is never skipped by this field.

Options

Option	What it does	Default
Matching Rule	How the source value resolves to an exhibitor. External ID looks up by the exhibitor's External ID (use when the source feed carries it directly); Internal ID looks up by ExpoPlatform's internal exhibitor ID (use only when the exhibitor was resolved upstream and its ExpoPlatform ID is passed through the payload).	External ID
Admin Role Rule	Whether a matched visitor is promoted to the Admin team role. With no rule set, every matched visitor joins as a regular Member. Currently one rule is available: Set as Admin if email matches exhibitor contact person email — case-insensitive, whitespace-trimmed comparison.	none (Member)
Conditional Path	Together with Conditional Value: apply this field only to records that satisfy a condition. The path points into the source record.	empty (no condition)
Conditional Value	The value the record must carry at the Conditional Path for the field to apply (string comparison). Records that don't match keep processing, just without the team-member link. Leaving either conditional option empty disables the condition.	empty (no condition)

The Admin Role Rule list is designed to grow — new promotion rules can be added on request.

A2Z-specific note

On A2Z team-member mappings, Matching Rule defaults to Internal ID. Don't change it — A2Z dispatches team members from inside its exhibitor service and passes the parent exhibitor's ExpoPlatform internal ID directly, so an External ID lookup wouldn't resolve.

Value handling

An empty or unresolvable source value (or a conditional mismatch) means no lookup succeeds — the visitor is saved without a team link. Nothing is cleared — the field only ever adds the link and role; it does not detach existing team members.

Source paths by integration

In the visitor field mapping, the source field that carries the parent-exhibitor identifier maps onto Team Member Matching:

Integration	Source path	Notes
Visit	`partner.id`
Aditus Visitors	`exhibitor.externalId1`
A2Z Team Members	`_exhibitorId`	System-injected key set when the parent exhibitor was processed. Matching Rule = Internal ID.
Swoogo	Per-event company custom field's ID (e.g. `c_XXXXXXX.id`)	Configured by the manager.

Some integrations expose a custom-field-based variant for sites where the upstream identifier isn't the External ID — see the per-integration mapping page for those.

Team Member Matching shared setting — the overview and pipeline role
Registration Emails — the team-member registration email fires only for visitors matched via this field