How is Account Engagement Connected to Salesforce Core?
How is Account Engagement Connected to Salesforce Core?
Standard Out-of-the-Box Connector
If you are not familiar with the Salesforce connector for Account Engagement, I highly recommend you read this guide first, as much of the information you need on this topic is there. This section will give you a brief overview.
If you are not familiar with the Salesforce connector for Account Engagement, I highly recommend you read this guide first, as much of the information you need on this topic is there. This section will give you a brief overview.
Syncing objects: From Account Engagement objects, record sync to Salesforce objects via the connector. Prospects are the best example of this; when syncing to Salesforce, data will end up on the associated lead/contact record (related with the CRM record ID).
- Deletion behavior is important to note here. If the prospect’s associated lead/contact record is deleted from Salesforce, the corresponding prospect record is automatically deleted.
Shared objects: Eliminates the need for users to create the same record twice, in two different places (i.e. in Salesforce then in Account Engagement). Campaigns are the best example of this.
Field sync behavior: For syncing objects, what happens if there’s a disparity between the data in a specific field? You can determine which value wins (either the Salesforce record or Account Engagement record) per field – the options are the Salesforce value, the Account Engagement value, or the most recently updated record. There are a couple of key point to note:
- Although “Most recently updated” is a popular option, it can produce unexpected results. It boils down to one fact – the master is the most recently updated record, not the most recently updated field. In other words, when any change is made to the record, not just on your target field.
- Some fields’ behavior differs from the norm. Consider the behavior of the email, and opted-out fields.
Custom Object Sync
With the higher Account Engagement editions, you can opt to sync more Salesforce objects to use in segmentation and automation on the Account Engagement side. This guide goes into the full detail on the behavior and limitations of custom object sync – but here are the key points:
- To sync additional Salesforce objects, a relationship to contacts, accounts, or leads in the CRM data model must exist (you need at least one lookup field).
- Four custom objects can be created in Account Engagement (if you need more, your object schema and sync volume will need to be looked at by a Salesforce Product Engineer).
- If your Salesforce data model doesn’t accommodate the desired custom object sync, there are workarounds to inject data into an object that can sync (whether that’s the standard syncing options, or to an object where the appropriate lookup exists to then leverage custom object sync). This, obviously, comes with risks that flows throw errors, and surmounting technical debt could be a consequence.
Asset Sync
Assets sync from Account Engagement to their related Salesforce campaign record. Note that the asset sync queue is separate from the prospect sync queue, and could sync less frequently.
Assets sync from Account Engagement to their related Salesforce campaign record. Note that the asset sync queue is separate from the prospect sync queue, and could sync less frequently.
When discussing the connector, there are also the topics of the sharing model (i.e. business units and user permissions) and the user interface – we’ll come back to these later.