How to Map Your CRM to Outreach Commit with Data Sync

Purpose

The purpose of this article is to provide Outreach Commit Admins with information about how to map their CRM to Outreach Commit with Data Sync.

Intended Audience

• Outreach Commit Admins

Data Sync Objects

Outreach Commit builds its model utilizing various fields within your organization’s CRM. The objects shown in the image (e.g., Account, Activity, Contact, etc.) are not CRM objects but rather the names of the objects within the Outreach Commit model.

Each object is configured independently and can be mapped to objects and fields from your CRM. Once all required objects have been made Active by mapping the specified CRM fields to Commit fields, you will be able to begin synchronizing your data by clicking Enable Sync.

This mapping process is explained further in the next section of this article.

• Active: Object has been successfully mapped
• Inactive: Object has not been mapped
• Error: Object has been mapped incorrectly

Objects that have a * next to them are required for the Outreach Commit object to function correctly. Mapping all objects shown opens up functionality for a more extensive list of metrics that can be utilized by the organization.

Salesforce Objects Currently Synced with Outreach Commit

• Account
• Contact
• Event
• Event Relation
• Lead
• Opportunity
• Opportunity Competitor
• Opportunity Contact Role
• Opportunity Field History
• Opportunity History
• Opportunity Line Item
• Opportunity Stage
• Organization
• Record Type
• Task
• Task Relation
• User
• User Role

Mapping Objects to Outreach Commit’s Object

To map your CRM to Outreach Commit’s model, click on one of the objects:

Within each Outreach Commit object, your organization can configure the object by selecting the fields from your CRM that should map to the fields in Outreach Commit.

Manage CRM Objects

For some objects, like Activity, you may want to map multiple CRM objects to a single object in Outreach Commit.

In this case, click Manage CRM Objects and choose the additional object(s) you'd like to map. When you map multiple objects, Outreach Commit will automatically merge records from each CRM object into the single Outreach Commit object.

Outreach Commit's Activity Object is an excellent example of having multiple CRM objects mapped. In this example, both Event and Task are objects bridged within Activity.

Manage Fields

You can also add additional extension fields onto an object in Outreach Commit by clicking Manage Fields and adding a new field to map to specific fields from the CRM. The field name, UI display format, and description can all be defined.

If your organization has custom or additional fields you'd like to display in filters or pipeline views, you can click Add Extension Field to achieve this.

After adding an extension field to Outreach Commit, you will also need to ensure it is mapped to the corresponding CRM field. Once this is completed, it allows Outreach Commit to use it in its index fields.

Write-Back to CRM

Write-back to CRM is enabled and configured during customer onboarding.  When enabled, a new column will appear in the field mapping table. From here, you can select the specific fields that should be bi-directional as well as define which users should have write-back capability turned on for that particular field.

• Owner: This selection ensures only the Opportunity owner can edit the field in Outreach Commit.
• Manager: This selection ensures that only individuals associated to the Outreach Commit team who is one tier above the team of the Opportunity owner can edit this field in Outreach Commit.
• Everyone: This selection means any user that has visibility to this Opportunity in Outreach Commit (the opportunity owner & any managers) can edit this field in Outreach Commit.

Sync Frequency

You can select the frequency at which Salesforce syncs its data to Outreach Commit within Data Sync. As shown below, this range includes as short as every 15 minutes and as long as every 24 hours. The total data refresh interval is defined by this sync interval plus the amount of time it takes for sync to run.

Outreach Commit uses the Salesforce bulk API for this sync. Organizations should note that the bulk API is a shared pool across all of the organization’s Salesforce integrations. If an organization states that it is running out of bulk API calls, then it should lower the sync frequency.

Clicking Sync Now will trigger Outreach Commit to sync immediately. The status of sync can be viewed within Sync Status or by clicking into History.

How to Re-authenticate your CRM

If an organization needs to re-authenticate their CRM connection for whatever reason, they may do so by clicking on the here text shown within the Objects in Outreach description section. A need for re-authentication may occur when the Salesforce admin for an organization leaves and someone new replaces them.

Note: When authenticating with Salesforce, the organization-designated admin must also be a Salesforce designated admin so that the correct users and role permissions can be pulled through the API.

How Does an Organization Know That They Need to Re-authenticate?

A user within the Outreach Commit admin portal will have 2 indications that a re-authentication is needed in order to utilize Outreach Commit.

• Click “View History,” and the latest status will show “Fail”
• Sync Status will show “Fail”