Updating Consent in Cvent

  • iPad
  • Online
  • Windows

This feature enables pushing consent from CRM to Cvent whenever an account is added as an attendee to an event. This allows event organizers who use Cvent’s native email functionality to confirm consent before sending emails.

The Cvent Consent field on both attendees and speakers in CRM is set to reflect the linked account’s consent to receive emails. When attendees and event speakers are pushed to Cvent, the value of the Cvent Consent field is used to update the consent of the corresponding contact record in Cvent.

Consent in Cvent is stored at the contact level, meaning each contact record can either be Opted-In or Opted-Out of receiving emails from Cvent.

Additional information about how Cvent manages consent is available here.

For example, Dr. Ackerman and Dr. Adams are accounts in CRM, as well as contacts in an integrated Cvent instance. When Sarah Jones creates a new event in CRM, she adds both Dr. Ackerman and Dr. Adams as attendees for her event. Sarah’s company has implemented custom code that automatically populates the Cvent Consent field value on each attendee and event speaker to reflect the linked account’s consent in CRM. When the integration pushes both of the attendee records from CRM to Cvent, the values of the Cvent Consent field on each attendee record are used to update consent on the Cvent Contact records for both Dr. Ackerman and Dr. Adams.

Considerations

Customers must create custom code to evaluate an account’s consent and stamp the appropriate consent value on the Cvent_Consent_vod field.

Configuring Syncing Cvent for Consent

To configure this feature:

  1. Grant integration users FLS read permission to the Cvent_Consent_vod field on the following objects:

    • EM_Attendee_vod
    • EM_Event_Speaker_vod
  2. Place the Cvent_Consent_vod field on the appropriate page layouts of the following objects. This step is optional:

    • EM_Attendee_vod
    • EM_Event_Speaker_vod

Managing Consent for Attendees and Speakers in Cvent

Whenever an attendee or speaker is added to an event in CRM, the value of the Cvent_Consent_vod field affects how consent is updated in the corresponding Contact record in Cvent:

  • None – The email and optOut fields on the corresponding Contact record in Cvent are not changed during the sync
  • Opt-in – The following fields are updated on the corresponding Contact record in Cvent:
  • optOut = No
  • email = The mapped email address from the account, user, Contact, or speaker in CRM
  • Opt-out – The following fields are updated on the corresponding Contact in Cvent:
  • optOut = Yes
  • email = The mapped email address from the account, user, Contact, or speaker in CRM

If the Cvent_Consent_vod picklist for either attendees or speakers is any value other than the values listed above, or if there is no mapped email address in CRM, the attendee or speaker is not pushed to Cvent.

Cvent Transaction Logs for Updating Consent

Transaction logs are created whenever the integration attempts to update consent of a contact in Cvent. The logs can be viewed and downloaded from the Cvent Integration History table to provide details of every transaction performed during the sync process.