Kübar Yarcu

In our case, we want to add an event registration form to our website, which means that people who are not yet in our contact database could register. They would fill out an event registration form, not a marketing form and therefore would not have consent for marketing communication. Without this prior consent, they would be unable to receive any emails, such as the event confirmation email.

Unfortunately, this approach doesn’t meet our current requirements. We need a solution that accommodates non-registered contacts in the system who still need to receive event-related emails.

While I have no issue using a marketing form (since it would include the DOI process), it does not have the event-specific fields, such as session summaries or speaker information. Additionally, I would not be able to integrate the marketing form into the event system, where registrations, check-ins, and other event-related actions are managed.

As it stands, according to the current logic, a new contact must register twice: first with the marketing form, then with the registration form and finally confirm the DOI email.

However, this issue could be resolved if the registration form had the same functionality as a marketing form, triggering the DOI process and sending the automated first DOI confirmation email.

We would appreciate any suggestions on how this process can be streamlined while still meeting the necessary requirements.