Overview

This guide walks you through the process of syncing respondents from your Cvent surveys to Salesforce, including the number of Apex jobs involved and how to verify the status of the attendee data sync. The setup of the respondent data refresh frequency and troubleshooting any issues that might occur during the sync process is also covered.

Sync Respondent Data

Respondent data sync consists of many Apex jobs. The number of jobs and the number of batches within these jobs depend on the App feature usage and the amount of data syncing from Cvent.

1. Go to Cvent Admin and click the Sync Respondent Data button. This syncs the respondents from your Cvent surveys that tie to the configuration you have selected on connecting the App to Cvent. Complete the first sync before setting up respondent data refresh frequency as pending sync prevents the automatic one from starting.

2. To verify the status of the attendee data sync, you can go to Setup > Apex Jobs and see the status of the following jobs.

   • CreateQuestionsBatch: This syncs event survey questions from Cvent for the tags selected in the program. This job will recurse itself in case of big data volume to be synced from Cvent, so you might see more than one occurrence of this job during the sync.

   • CreateRespondentTempsBatch: This syncs data from Cvent to the Respondent Temp Record object. This job will recurse itself in case of big data volume to be synced from Cvent, so you might see more than one occurrence of this job during the sync.

   • RecordMatchingBatch: This processes the Respondent Temp Records created or updated on the second step, and performs record matching to find the matched Salesforce contact, lead, or person account (if enabled).

     • In case of Attendee/Respondent-based Record Matching approach is chosen, it also creates and updates attendee records. Refer to matching approaches for more details.

   • CreateRespondentsBatch: This creates or updates the Survey Respondent records linked to the Cvent Survey Program and Salesforce contact, lead, or person account. Only takes place in case of Contact-based Record Matching approach is chosen. Refer to this article for more details about matching approaches.

   • CreateAnswersBatch: This syncs answers from Cvent to Survey Answer object for respondents processed in the previous steps. This job will recurse itself in case of big data volume to be synced from Cvent, so you might see more than one occurrence of this job during the sync.

   • SurveyProgramDataTransferBatch: This launches the data transfer flow for survey programs. This job will recurse itself, so you might see more than one occurrence of this job during the sync.

3. Once the sync is completed, the last sync date for respondents is replaced with the start date of that sync. Thus, the next sync process will only include the updates which happened after the previous sync.

   • Last sync date is not updated in case of the entire sync failed.

If respondents aren’t getting created, refer to the troubleshooting guide to identify and fix the problem.