MeetMax ➔ Engagefully (CDA)

Source System
MeetMax
Destination System
Engagefully
Version
1.3.2026.9020

Description

Imports meetings from MeetMax into Engagefully as appointments, for CDA only. Records sharing a meeting ID are consolidated into one appointment, and attendees are matched to existing Engagefully registrants by CDA group ID.

Mapping Information

MeetMax Engagefully Notes
Meeting ➔ Appointment MeetMax returns one record per participating group, so a meeting with three groups arrives as three records sharing a meeting_id. Records are consolidated into a single appointment on that shared meeting_id. Only records where both meeting_status and attendee_status are CONFIRMED are imported.
Meeting.meeting_id ➔ ExternalKey The shared ID of the consolidated meeting.
Meeting[].company ➔ Name The company portion of each record's company value, taken from the text before the first " - ". Records with no " - " contribute the whole value. Unique company names are alphabetized and joined as "Acme Co and Mars", or "Acme Co, Jones Brothers, Inc., and Mars" for three or more.
Meeting[].company ➔ Description The full company value of every record, alphabetized, one per line under a configurable heading. Unlike Name, the group portion is kept.
Meeting.date + Meeting.start_time ➔ StartTime Taken from the first record. Consolidated records are expected to share a start time.
Meeting.date + Meeting.end_time ➔ EndTime Taken from the first record. Consolidated records are expected to share an end time.
Meeting.room ➔ Location Taken from the first record. Consolidated records are expected to share a room.
Meeting[].attendee_id ➔ UserEmailList For CDA, attendee_id is a group ID rather than a person. The group IDs of every consolidated record are matched against the group IDs stored on Engagefully registrants in Lead Custom Report 1, and the email addresses of the matching registrants become the pipe-separated attendee list.
 
Engagefully RosterEntry ➔ Appointment Registrants are read from Engagefully rather than from MeetMax. They are expected to have been imported already by the Expo Tracker connector, which is what populates the group IDs.
LeadCustom1 ➔ (match key) The registrant's CDA group IDs, as Expo Tracker's "Meet Max ID" field sends them: separated by semicolons, such as "6106301; 6106303". Commas are accepted as separators too. A registrant belongs to a meeting when any of these matches any group ID on the meeting.
Email ➔ UserEmailList Email is the identifier Engagefully uses for appointment membership.