Monitoring from the participant record

In the References on third-party applications box of a participant's record, you can find their synchronization information with HubSpot.

The Contact ID associated with the participant
The Transaction ID, if any, associated with that Contact
The date and time of the last synchronization with HubSpot
The last error returned by HubSpot's REST API (ideally there isn't one)

An error can occur during the very first synchronization with HubSpot, or after an update when the participant is already present in HubSpot.

Force a new synchronization for a participant

If a participant's upload to HubSpot failed for any reason, you can retry data synchronization from their Eventmaker record by clicking the Synchronize to HubSpot button.

⚠️ If the synchronization error was due to invalid participant information, updating the participant to correct that information will in any case trigger data synchronization to HubSpot. In that case, there is no need to manually force resending the data.

Monitoring from the participants list

Display HubSpot synchronization information

Click the Display button above the participants list, and in the Standard fields list, select References on third-party applications, which you can then order in the list on the right.

Four new columns are now displayed in the list to give you a general idea of the state of the HubSpot integration.

Filter the participants list

You can filter the participants list using the search keyword hubspot_sync_status which can take the value either synced or error.

Using the search hubspot_sync_status:synced, you'll find all participants who have been synchronized at least once in HubSpot.

Using the search hubspot_sync_status:error, you'll find all participants whose last synchronization with HubSpot failed.

⚠️ Note the two lists are not exclusive: this means that a participant whose last synchronization failed may already have been uploaded to HubSpot during a previous synchronization.

Force a new synchronization for a list of participants

If a configuration error, whether on the Eventmaker side or on HubSpot's side, caused a series of API errors when uploading 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 Synchronize participants to HubSpot.

And finally click Synchronize.

⚠️ Sending registration data to HubSpot is always asynchronous and is managed via a queue. Depending on platform activity and the number of participants for whom you 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 functionality, you can generate a file that will contain references on third-party applications, notably those for HubSpot

Import participants with HubSpot references

Even before registration, you can import a list of guests from your CRM with their references. Two columns are available :

hubspot_contact_id : HubSpot contact ID
hubspot_deal_id : HubSpot transaction ID

The connector will use this information during the first synchronization with HubSpot - immediately after a participant registers - instead of performing reconciliation based on the email address.

You are not required to provide both columns when importing

Monitor automated processes

In addition to keyword search from the participants list, you can monitor your HubSpot integration from the execution history of automated processes. As a reminder, the Automation feature is used to ensure data upload to HubSpot and 4 processes are configured.

The history allows you to filter by process, by status, and by a date range.

Suppose there was a burst of errors with the HubSpot API at some point caused by a temporary CRM issue; you can filter, select, and then retry the tasks that are in error.