Mutiny has a robust integration with Salesforce that allows you to do a number of things, including building personalizations based on your Salesforce data, attributing Mutiny experiences back to your pipeline, and sending Mutiny data back into Salesforce for more robust reporting. This document will give an overview of the integration.

Read data from Salesforce

You can set up your integration to pull in data from your different Salesforce objects. Below, we'll break down how we use the data from each object.

Accounts object

The accounts object is typically the most actionable source for personalization. The data in this source is at the company or account level, not the individual, contact or lead level.

Once you set up your integration and map the fields you want from the accounts object, Mutiny will match anonymous users on your site to Salesforce accounts by matching the domain returned by your IP provider to the domain linked to the company's Salesforce record. This link allows you to create segments based on mapped columns or dynamically insert data stored in Salesforce directly on your personalized pages.

When you map your columns, be sure to map the Company Domain field to the field in Salesforce that contains an account's domain.

Contacts and leads objects

The contacts and leads objects give you access to individual level data, such as name, job function, department, seniority, and title. This data is typically most useful for outbound personalization, allowing you to create 1:1 personalized landing pages for target accounts, prospects, and customers. This granular data will allow you to change your messaging based on role, seniority, and plan type.

Similar to how the accounts object will use the domain as a link between your website visitor and their Salesforce account, individual users can be linked back to their Salesforce contact or lead record using their email. To utilize this data in your experiments, be sure that you've set up your Mutiny identification.

When you map your columns, be sure to map the Email field to the field in Salesforce that contains an individual's email.

Opportunities object

You can use the data in your opportunities object to build more robust segments and personalizations. We'll also use the data from your opportunities object to attribute Mutiny experiences back to revenue and pipeline. You can learn more about attribution here.

Writing data to Salesforce

In addition to reading data from Salesforce, you can write data back to Salesforce to enable more robust reporting. When enabled, Mutiny will sync experience impression data to Salesforce using Campaigns and Campaign Members. Mutiny will create a new Campaign for each Mutiny experience you sync and then add Campaign Members. Mutiny will add campaign members for any Lead or Contact who has seen that experience. For outbound experiences that are based on a company list, Mutiny can add Accounts as campaign members if you have enabled Accounts as campaign members in Salesforce.

Next steps

Now that you understand how Mutiny will use your Salesforce data, head on over to this article to set up your integration.