Several tools are available to monitor the proper operation of your Salesforce integration.
Monitoring from the participant record
In the box Third-party application references on a participant's record, you can find their synchronization information with Salesforce.
The Contact or Lead ID associated with the participant
The Campaign Member ID associated with that Contact or Lead
The date and time of the last synchronization with Salesforce
The last error returned by Salesforce's REST API (ideally there is none)
An error can occur during the very first synchronization with Salesforce.
Or later when the participant has already been pushed to Salesforce.
Refer to the article on the Common Salesforce API errors to find a solution.
Force a new synchronization for a participant
If the push of a given participant to Salesforce failed for any reason, you can restart synchronization of that participant's data from their Eventmaker record by clicking the Resend to Salesforce button.
If the synchronization error was due to invalid participant information, updating the participant to correct this information will in any case trigger the synchronization of data to Salesforce. In that case, it is not necessary to manually force resending the data.
Monitoring from the participants list
Display Salesforce synchronization information
Click the View button above the participants list, and in the Standard fields list, select Third-party application references, which you can then order in the list on the right.
Five new columns are then displayed in the list to give you a general idea of the state of the Salesforce integration.
Filter the participants list
You can filter the participants list using the search keyword salesforce_sync_status, which can take the value synced or error.
Using the search salesforce_sync_status:synced, you will find all participants who have been synchronized at least once with Salesforce.
Using the search salesforce_sync_status:error, you will find all participants whose last synchronization with Salesforce failed.
Note the two lists are not exclusive: this means a participant whose last synchronization failed may already have been pushed to Salesforce during a previous synchronization.
Force a new synchronization for a list of participants
If a configuration error, whether on the Eventmaker or Salesforce side, caused a series of API errors when pushing data to the CRM, you can force a new synchronization from the participants list.
To do this, filter the list to find the affected participants, click the More button and select the Trigger an action option. Then click Resend data to Salesforce.
Finally click Resend.
The sending of registration data to Salesforce is always asynchronous and managed via a queue. Depending on platform activity and the number of participants for whom you have retriggered synchronization, this can take a few seconds (most likely for a small number of participants), a few minutes, or even several tens of minutes (most likely for several hundred participants).
Export synchronization information
Using the platform's participant export feature, you can generate a file that will contain the third-party application references, including those for Salesforce.
Import participants with Salesforce references
You can import a guest list from your CRM with their references before they register. Three columns are available :
salesforce_contact_id : Salesforce contact ID
salesforce_lead_id : Salesforce lead ID
salesforce_campaign_member_id : Salesforce campaign member ID
The connector will use this information during the first synchronization with Salesforce just after a participant's registration instead of using the unique key.
Note: you are not required to fill in all these columns during your import.
Monitor automated process runs
In addition to keyword search from the participants list, you can monitor your Salesforce integration from the task history of automated processes. As a reminder, the Automation feature is used to ensure data is pushed to Salesforce and 4 processes are configured.
The history allows you to filter by process, by status, and by a date range.
Suppose there was a batch of Salesforce API errors at some point due to a temporary issue on the CRM; you can filter, select, and then restart the failed tasks.
You will then see the tasks move to Completed.