The ON24 Cvent Registration Integration enables registration that occurs via a Cvent event to automatically flow into the associated ON24 event. This allows event planners to use Cvent to manage the overall registration and planning process via Cvent while enabling seamless registration into ON24’s suite of offerings.

Cvent to ON24 Registration

Enabling the integration in Cvent involves the use of webhooks. Before you move forward with the instructions on this page, please contact your Cvent account manager to verify your contract includes the use of webhooks and that it's been enabled for your Cvent account. 

If your Cvent contract includes "Integration Hub ON24," then do not follow the setup instructions on this page because you paid for Cvent's external registration solution. Since they own and manage the solution, please contact Cvent Support for next step instructions. 

Supported Elements

The following elements are supported by the ON24 Cvent Registration Integration

• Cvent’s Enterprise solution is supported - Conferences is not currently supported
• Cvent Events are supported - Sessions are not currently supported
• Cvent’s Classic (a.k.a. Standard) Registration and Express Registration events are supported – Ticketing events are not supported
• ON24 Webinars, Engagement Hubs, Target Experiences and Virtual Conferences are all supported
• Activity performed within Cvent will trigger registration actions in ON24.  The supported triggers / actions include:

Supported Elements

Enabling the integration in ON24 involves the following 4 steps. Steps 1 and 2 are one-time configurations done within the client account, steps 3 and 4 are done for each ON24 event to be integrated.

• API access must be enabled for the ON24 account where the target event(s) reside. 
• An API Access Token must be enabled in the API Dashboard for the applicable ON24 account (access tokens will not be able to be created unless the account is enabled for API access).  Visit https://wcc.on24.com/webcast/apitokensdashboard to view existing API access tokens or to create a new token.  It is recommended that a dedicated token be created for the Cvent integration. At a minimum, the token should be configured with access to "Registration endpoints" and "Event-level Analytics endpoints" (access for ‘All endpoints’ will work as well). 

• Individual events should be configured with the applicable registration fields to be passed from Cvent. If a field is configured as ‘required’ in ON24 then that field must be passed from Cvent for a registrant to be successfully registered to the ON24 event. Fields that can be passed from Cvent to ON24 are listed in below table (custom fields are not supported):

¹ jobtitle must be configured to be a Text Field

• Registration confirmation emails can be sent from Cvent, ON24 or both.  If confirmation emails are to be sent from ON24 then the registration confirmation email should be configured for the applicable event(s). This configuration should be done in the same manner as standard confirmation emails – there is no special configuration needed for this integration. 
   

Cvent Setup

Enabling the integration in Cvent involves the use of webhooks. Before setting up webhooks it must be enabled in the applicable Cvent account.  To do this contact your account manager.  For additional information on webhook usage and configuration visit https://developers.cvent.com/documentation/webhooks-integration-user-guide.

Configuring the webhook capability for use with ON24 involves 4 steps: Steps 1 - 3 are one-time account-level configurations, step 4 is done for each Cvent event to be integrated since the On24 Event ID will need to be inserted. 

1. Adding an integration configuration – see https://developers.cvent.com/documentation/webhooks-integration-user-guide/setting-up-webhooks/adding-a-configuration

a. Name can be any value
b. Type should be ‘Webhooks’
c. Default Endpoint should be https://connect-cvent.on24.com
d. Authentication Token can be any value’

2. Setting up the configuration – see https://developers.cvent.com/documentation/webhooks-integration-user-guide/setting-up-webhooks/setting-up-your-configuration

a. Within the Basic Information section
            i. Active should be ‘Yes’
            ii. Default is optional

b. The Webhooks Login section should be the same values entered when adding the integration configuration

c. Within the Synced Objects section:
            i. Attendees should be set to ‘Yes’
            ii. Sessions and Speakers should be ‘No’

d. The Endpoints section should include the default endpoint value entered when adding the integration configuration. No additional endpoints are necessary.

e. The Manual Syncing section should have ‘default’ for all options.

f. Failed Sync Notification Settings and Recipients are optional.

g. The following integration points should be added:
            i. Invitee/Guest Registered for Event
            ii. Invitee/Guest Event Registration Modified
            iii. Invitee/Guest Event Registration Cancelled

3. Setting up custom event fields – 4 custom event fields will need to be created within the applicable account.  These fields are necessary for passing required event information to ON24.  

a. Go to Admin > Account > General > Custom Fields > Custom Event Fields



The necessary custom fields to create are as follows:

i. on24.eventId
        1. *Name must be ‘on24.eventId’ (omit quotes)
        2. *Code can be any value
        3. Help Text is optional, but recommended
        4. Type should be ‘Open Ended Text – One Line’
        5. This field is required should be ‘Yes’
        6. Display in Event Creation Wizard should be ‘Yes’
        7. Field Settings are optional

ii. on24.clientId
        1. *Name must be ‘on24.clientId’ (omit quotes)
        2. *Code can be any value
        3. Help Text is optional, but recommended
        4. Type should be 'Choice - Single Answer (Drop-Down)'
        5. This field is required should be ‘Yes’
        6. Display in Event Creation Wizard should be ‘Yes’
        7. Field Settings are optional

iii. on24.accessTokenKey
        1. *Name must be ‘on24.accessTokenKey’ (omit quotes)
        2. *Code can be any value
        3. Help Text is optional, but recommended
        4. Type should be 'Choice - Single Answer (Drop-Down)'
        5. This field is required should be ‘Yes’
        6. Display in Event Creation Wizard should be ‘Yes’
        7. Field Settings are optional

iv. on24.accessTokenSecret
        1. *Name must be ‘on24.accessTokenSecret’ (omit quotes)
        2. *Code can be any value
        3. Help Text is optional, but recommended
        4. Type should be 'Choice - Single Answer (Drop-Down)'
        5. This field is required should be ‘Yes’
        6. Display in Event Creation Wizard should be ‘Yes’
        7. Field Settings are optional

4. Enabling the Integration for a Cvent event

a. The webhook configured in step 2 above should be activated – see Activating Webhooks for an Event at https://developers.cvent.com/documentation/webhooks-integration-user-guide/integrating-webhooks-in-an-event/activating-webhooks-for-an-event

b. The appropriate values should be input or selected in the custom event fields within Events > eventname > General > Event Information > Custom Fields:
            i. on24.eventId – this is the ID of the ON24 event that registrant data will be passed to
            ii. on24.clientId – this is the ID of the client account from step 2 of the ON24 Setup section above
            iii. on24.accessTokenKey – this is the token key from step 2 of the ON24 Setup section above
            iv. on24.accessTokenSecret – this is the token secret from step 2 of the ON24 Setup section above