Overview

This article discusses the key business requirements that should define the configuration of the Cvent Salesforce App. As a highly customizable solution, it’s important to involve business stakeholders, the Salesforce Administrator, and the Cvent Administrator in defining these requirements.

By following the guidelines provided in this article, you can configure the App to meet your specific event management and customer relationship management needs.

Field Mappings

The App includes default mappings for first name, last name, and email address. Beyond this, your business stakeholder can choose what other data you’d like to sync across both systems. Include required fields in the field mapping, or new contacts/leads creation fails. For example, Salesforce leads require last name and company, whereas Cvent contacts have email address as their required field.

Field Matching

Your Salesforce Administrator should define which fields identify a unique contact or lead. For example, only email address, or a combination of fields, such as both email address and first name. Based on the chosen field for uniqueness, a Salesforce Administrator can configure the Record Matching Criteria between Salesforce and Cvent.

Matching Rules

Review what level of control you would like to give to the App to impact your Salesforce contacts and leads. For example, should the App only update attendees’ information without affecting your Salesforce contacts and lead records? Or should the App update all Salesforce records with the latest data from Cvent and create new Salesforce contacts or leads? Based on the objects you want the App to update, your Salesforce Admin can configure the record-matching settings.

Event Visibility

Your business stakeholder should define the types of events accessible to particular Salesforce users. Then, the Salesforce Administrator can define the Event Filtering criteria, determining which events each category of Salesforce user can see. For example, users who belong to division A should only see events organized by division A, whereas global corporate events should appear to Salesforce users from all divisions.

Permissions

Your business stakeholders should define which workflows they want to expose to specific user profiles. For example, can Sales users invite, register, or nominate leads? Based on this decision, the Salesforce Administrator can assign user permission sets appropriately.

Data Refresh & Purge

Your business stakeholder and Salesforce Administrator should define the frequency at which the App adds Cvent data to Salesforce and the duration each event remains available in Salesforce. This process determines how the App consumes resources for Apex jobs and data storage. Then, the Salesforce Administrator can define the data refresh frequency for attendees and events, as well as the purge criteria for removing logs and old events.

Existing Salesforce Processes and Rules

The Salesforce Administrator should take stock of existing rules and validations, keeping these in mind while configuring the App. Based on your configurations, the App creates and updates Contacts, Leads, Person Accounts, Opportunities, Tasks, Campaigns, and Campaign Members.

Advanced Features

Business stakeholders should define the workflows that impact Salesforce objects such as Tasks, Opportunities, and Campaigns. If the event requires nominations, the business stakeholder should define the criteria for the approvers. Based on your rules, the Salesforce Administrator can configure these features in the app.

What’s Next?

Now that you’ve gotten to know the Cvent Salesforce App, reference General Data Structure article to understand the Cvent Salesforce App data structure and syncing.