Open Forum

 View Only
  • 1.  Custom Objects

    Posted 25 days ago

    Is there any way to create custom objects inside Cvent?

    We have a request to accommodate letting invitees register using any of the emails we know for them. Our engagements are with individuals who either use personal or work emails, and a highly tailored user experience is essential for what we're trying to provide, so instructing them to use the email we have on file for them is insufficient.

    The problem is that in order to enable them to use any of their emails to register, we have to create multiple contacts for what's really one person. While we can track the existence of really just one person in our CRM, it would better support our long-term use of Cvent as our definitive event planning tool if we could create a unified record for each person within Cvent.


    #Registration
    #ReportingandInsights

    ------------------------------
    Ivan Larson
    Technical Product Manager
    Stand Together, Inc.
    ------------------------------


  • 2.  RE: Custom Objects

    Posted 22 days ago

    This is also an issue for us, too. We're in the same boat, as we have had to create a separate contact record for every email we have for an individual. From a database standpoint, it creates a challenge for us to reconcile registration and event activities, and sometimes creates a bad user experience for our guests.



    ------------------------------
    Kelli Mahoney
    Associate Director, Global Events
    American Jewish CommitteeUnited States
    ------------------------------



  • 3.  RE: Custom Objects
    Best Answer

    Posted 20 days ago

    Hi All,

    Following up on your question about letting invitees register with any email address you have on file for them, here's a quick summary of what's possible in Cvent today:

    • Cvent doesn't support true custom objects or a single "person" record with multiple login emails. You can add custom contact fields (including additional email fields), but only one email can act as the unique identifier for matching and login.

    • There is an optional, account‑level "contact match key" change that allows multiple contacts to share the same email (First Name + Last Name + Email as the identifier). This is irreversible, creates more duplicates, and still doesn't give you one unified record per person, so it usually works against the long‑term data quality you're aiming for.

    • For scenarios where multiple people legitimately share one email (spouses, parents + children, shared inboxes for a single event), Cvent recommends guest registration: one primary invitee email with guests attached under that record.

    • The most promising path toward a unified "person" concept is to use your CRM as the system of record (with all known emails) and have Cvent key off a Source ID:

      • Store the CRM person ID in Cvent's Source ID field.

      • Configure the registration path to identify registrants by Source ID and still collect email on the form.

      • When someone registers with their Source ID, Cvent keeps them tied to the same underlying contact even if they use a different email for that registration.

    In practice, that means: Cvent alone can't model "one person with many emails" the way your CRM can, but a combination of CRM person ID + Cvent Source ID–based matching gets you very close to a unified record per person, while still giving invitees the flexibility to use the email that makes the most sense for them. I would definitely chat these options over further with your account team to ensure that you all are making the best decision for your overall account and data records. 

    Hope this helps!



    ------------------------------
    Julianna Hampshire
    Lead Customer Success Advisor
    SalesforceGenericAccountUnited States
    ------------------------------