We're looking for guidance on a registration and authentication challenge.
Current Setup
- Contacts are managed in Salesforce and synced to Cvent as Campaign Members/Invitees.
- An integration provisions invited attendees into Okta.
- Cvent registration is protected behind Okta authentication, ensuring only invited attendees can access the registration site.
- Each attendee is currently associated with a single email address.
Challenge
Many of our invitees may attempt to register using an alternate email address rather than the email listed in Salesforce/Cvent.
We would like to support multiple valid email addresses for a single individual without:
- Creating duplicate attendee records in Cvent
- Breaking Salesforce ↔ Cvent integrations
- Impacting agenda syncs or downstream reporting
- Creating multiple registrations for the same person
Desired State
We're exploring whether Cvent can:
- Keep the registration site fully protected behind authentication.
- Allow Okta to authenticate a user using any approved email address associated with that person.
- Permit registration once authenticated, even if the email used for login is not the exact email on the Cvent invitation list.
- Maintain a single attendee record within Cvent for reporting, agenda management, and Salesforce synchronization.
Questions
- Has anyone implemented a similar solution where attendees can authenticate using multiple email addresses while maintaining a single Cvent attendee record?
- Are there Cvent settings, SSO configurations, identity matching options, or integration patterns that support this use case?
- What are the recommended best practices for handling alternate email addresses without introducing duplicate contacts or registration records?
Any guidance, examples, or architectural recommendations would be greatly appreciated! Thanks!
#Registration------------------------------
Sang Le
Systems Engineer
Stand Together CommunicationsUnited States
------------------------------