Team Member Matching
Team Member Matching adds visitors to an exhibitor's team automatically. When a visitor arrives from the source system carrying a reference to a parent exhibitor, the sync looks up that exhibitor in ExpoPlatform and adds the visitor as a team member with an assigned role.
Presence of the Team Member Matching 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.
How to configure
In the visitor field mapping, set the source field that carries the parent-exhibitor identifier to map onto Team Member Matching. Each integration uses a different source field — see the specific integration page for details.
The field has two configurable options.
Admin Role Rule
Determines which exhibitor role the matched visitor receives. Defaults to Member — with no rule configured, every matched visitor joins as a regular member.
Available rules:
-
Set as Admin if email matches exhibitor contact person email — compares the incoming team member's email with the contact person email on the matched exhibitor (case-insensitive, whitespace ignored). On a match, the team member is promoted to Admin. When either email is missing or they differ, the role stays at Member.
The rule list is designed to grow — new promotion rules can be added on request.
Matching Rule
How the value in the mapped source field resolves to an exhibitor:
-
External ID (default) — looks up the exhibitor by External ID. Use this when the source system provides the exhibitor's External ID directly. Applies to Visit and Aditus Visitors.
-
Internal ID — looks up by ExpoPlatform's internal exhibitor ID. Use this only when the exhibitor record has already been resolved upstream and the internal ID is being passed through. Currently only A2Z uses this.
A2Z-specific note: On A2Z team-member mappings, Matching Rule defaults to Internal ID. Don't change it — A2Z's exhibitor service dispatches team members with the parent exhibitor's ExpoPlatform internal ID directly, so External ID lookup wouldn't resolve.
Behaviour summary
|
Lookup outcome |
Result |
|---|---|
|
Exhibitor found |
Visitor is saved with Exhibitor ID set and Exhibitor Role from the Admin Role Rule (default: Member) |
|
Exhibitor not found |
Visitor is still saved, but as a standalone attendee with no exhibitor link |
The visitor is always saved — a failed lookup never skips the record, it just means no team-member link is created.
Related settings
If Registration Emails → Team Member Registration Email is enabled, this email fires only when Team Member Matching successfully links the visitor to an exhibitor. See Registration Emails.