We have an issue where we created an event form for pre-registration and a second event form (for the same event) for day-of-event "other fees". Registrants (doesn't seem to matter if they are named guests, hosts, or guests who are already have constituent records) are being duplicated within the event when they purchase day-of items on the "other fees" form. The system should be smart enough to match those up, rather than treating it as an additional event participant record. There should also be functionality to merge those participant records within the event so that we don't end up with a bunch of duplicated data and have skewed participant numbers on the event record. To be clear, it is NOT creating duplicate constituent records (the unmatched constituent review process is functioning as expected), but only duplicating the participant within the event.

Need to have the option to create different types of forms within an event - forms specifically for registration (that could capture "other fees", also) and the option to create non-registration forms that capture only other fees, as long as those "other fees" forms will then be tied to the existing participant records (whether the participant is a host or a guest) when available, rather than creating a 2nd participant record for the same participant.

This does not already exist. If an existing constituent registers under another email or doesn't enter their name exactly as it is entered on their record, the system creates a duplicate constituent and event registration.

We currently offer duplicate matching on registration forms.

For hosts (the person who pays for or completes the registration), the form automatically checks whether they have an existing record. It uses the required First name, Last name, and Email fields from the payment section to perform these checks.

For guests (the additional people a host includes in their registration), the form must be configured to include Email and/or Phone to automatically check whether they have an existing constituent record. If the registrant only provides first and last names for their guests, the form creates guest records for all named guests and does not search for matches on existing constituent records. To ensure the form searches for a match on guests, we recommend setting either Email and/or Phone to required.

I’m also including a few links to our documentation covering this specific topic:

• Automatic Constituent Matching

• Constituent Matching for Participant Records