All Collections
First party data
Mapping Salesforce tables and columns
Mapping Salesforce tables and columns

Identify which tables you should integrate and which columns you should map from each.

Updated over a week ago

Mutiny integrates with Salesforce to let you take action using your first party data. You can find an overview of the integration here. This article will focus on which tables and columns to map.

Selecting your source table(s) and mapping columns

Mutiny integrates with the 4 most actionable tables for personalization: Contacts, Accounts, Leads, and Opportunities. You can select as many as are relevant to you.

On the next screen, you can map the columns you want to use in Mutiny. Mutiny will only access the tables and columns you explicitly map.

Accounts table

The Accounts table is typically the most actionable source for inbound personalization, and has the highest match rate. The data in this source is at the company or account level, not the individual/contact/lead level. 

To match anonymous visitors to a Salesforce Account record, Mutiny uses the Clearbit returned domain of the visitor to link to that company's record. This link allows you to create segments based on mapped columns or dynamically insert data stored in Salesforce directly on your personalized page. 

On the column mapping screen, you can set the "Company Domain" column to the website field you would like to use as the bridge to connect the Clearbit returned company domain to the company's Salesforce record. 

Mutiny pre-loads suggested mappings, but you can customize these and even add your own.

Contacts and Leads Tables

Contacts and Leads tables 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. 

To use Contact or Leads table data for inbound personalization, you will need to integrate Segment or the Mutiny API to send the user's email. Similarly to how the Clearbit returned domain is the bridge between anonymous traffic and their Salesforce Account data, email address is the bridge between a website visitor and their Salesforce record. 

Be sure to map the "Email" column on the mapping page to use Contact and Lead data for inbound personalization. Mutiny pre-loads suggested mappings, but you can customize these and even add your own.

Opportunities Table

Finally, you may also use your Opportunities table as a source. Mutiny pre-loads suggested mappings, but you can customize these and even add your own.

Mutiny also uses data from the Opportunities table to provide more robust segment recommendations. Mutiny will make recommendations based on close rate and deal size in comparison to website traffic performance. To make this comparison, Mutiny will enrich your Salesforce Opportunity records through Clearbit to provide an apples to apples comparison for each segment.

Don't be a stranger

If you have any questions, we’re here to help! Please feel free to contact us at any time, either through intercom chat or via

Did this answer your question?