I have a question on Matching rule of Event Administration as the following scenario:
1) In Event Administration, when a customer submit a registration in Event (required fields is First Name, Last Name and Email Address), system can create new Contact or map the event registration to an existing Contact without update First Name and Last Name of an existing Contact. So we had set the value of "Match contact based on" field is "Email". So when a customer submit the registration on Event, the event registration can map the email on a event registration to an existing Contact and don't change the First Name and Last Name of that Contact.
2) After a customer submit the event registration, they refer the email confirmation to send the First Name and Last Name that they have submitted before but not the First Name and Last that already exist in the system. So the question in this situation is: How can we collect the First Name and Last Name of the customer when they submit the Event registration, but without update the First name and Last Name of Contact that already existed?
We are considering about Custom registration fields, but if anyone have a solution on this case, please help us to rise it.
Hi Nya,
Thank you for your idea, but I wondering about how can we track the contact which have the existing email on the system? I don't think workflow can handle this complex query as form matching on Marketing Form.
Hi,
In the scenario 1:
If the Event Registration Duplicate Setting is set as your screenshot and an existing contact registered an event with the same email and a different name, the name will still be updated.
If you want to collect the name which is used to register the events and not update existing names of contacts, you can create two new custom fields, something like firstname1 and lastname1, in Contact entity.
As firstname and lastname are required fields for event registration, you cannot bypass them. It means that even if you create Custom registration fields, the required fields still need to be kept in the registration form. I think this will just confuse the user as to which name corresponds to what.
You can try to create a Flow to add a condition to judge if the contact is existing. If yes, do not update the existing firstname and lastname and insert the values into the new fields just created. If no, create a new contact. So that you can collect the names submitted by customers and remain the existing names of contacts at the same time.
If this helped you, I'd appreciate it if you'd mark this as a Verified Answer, which may in turn help others as well.
Best Regards,
Nya
André Arnaud de Cal...
291,979
Super User 2025 Season 1
Martin Dráb
230,848
Most Valuable Professional
nmaenpaa
101,156