This article will walk you through setting up your Salesforce integration. Before getting started, we recommend checking out the integration overview article here to understand how Mutiny uses your Salesforce data.

Setting up your integration user

Note: The user selected for the integration must have a standard Salesforce user license and not an Integration user license.

Before we get started on the integration, you'll want to set up an integration user in Salesforce. You'll need to connect an org-level Salesforce user to Mutiny, which is the primary connection for Salesforce API calls and syncing data between Mutiny and Salesforce. All data pulls and pushes between Mutiny and Salesforce are made using this account.

We strongly recommend creating a dedicated, Mutiny-only Integration User with a fine-grained permission set. This enables more robust reporting because it ensures all record changes by Mutiny are properly attributed to Mutiny.

You may prefer to connect a Shared Integration User or use an existing Individual User. Here’s more about each:

Setup	Pros	Cons
Dedicated, Mutiny-only Integration User	This is best practice and our recommended option. The user is granted precise permissions and all updates made within Salesforce are clearly attributable to Mutiny.	This requires use of a dedicated Salesforce User license, which may require time to set up at your company.
Shared Integration User with other connected apps	This might be a better choice if you already use an Integration User with other connected apps. You don’t need to provision a new user.	Mutiny must share the permissions and limits of the Shared Integration User. If this user’s access is shut down, all connected apps will be impacted.
Existing Individual User with system admin permissions	This is typically the fastest and most affordable option because you use an Individual User that already exists in your Salesforce. There’s no need to create anything new.	If the user leaves the company, the connection will break. Mutiny is given full system access and edits made within Salesforce are attributed to the Individual User.

Permissions

You'll want to ensure that the Salesforce user you have set up has the following permissions. If you're unsure where to set these permissions, you should contact your Salesforce administrator or see this Salesforce help article+

User Configuration:

User should be set to a Marketing User
User should have offline access enabled
Refresh Token permissions should be enabled

Permissions for ingestion of data from Salesforce to Mutiny:

Account: READ
Contact: READ
Lead: READ
Opportunity: READ
- Include Opportunity History and Opportunity Field History

User: READ (For Account Ownership matching)
Campaign: READ (For list building)
Campaign Member: READ (For list building)

For pushing experience data from Mutiny to SFDC:

Campaign: READ, WRITE
CampaignMember: READ, WRITE

For writing Microsite links from Mutiny to SFDC:

Account: WRITE
Contact: WRITE
Lead: WRITE
Opportunity: WRITE

Field level security:

If you utilize field level security, ensure that the user has READ access to any fields you want to pull into Mutiny.

To inspect multi-currency setup (used in revenue reporting):

multiCurrency field on Org (through org-connect): READ
CurrencyType: READ

Setting up the integration in Mutiny

Once you've set up your integration user, you can head over to Mutiny to authorize the integration. You'll first want to connect to Salesforce, and then install our reporting package to help with our process of writing data back to Salesforce campaigns.

Connect to Salesforce

Navigate to https://app.mutinyhq.com/integrations and click on the Salesforce card. Then, select "Connect to Salesforce" in the top right.
From there, you'll be taken to a page where you can login to Salesforce. Be sure to login using the user you set up earlier.
Select the objects you'd like to pull into Mutiny. We recommend selecting all of four of the objects. You can learn more about what Mutiny does with this data here.
Now you'll want to map the columns that you want to bring into Mutiny. Mutiny maps a number of columns by default, but you can always add in more. You'll also have the option to revisit this mapping later on if you choose to add or remove data.

Install the reporting package

In order to sync your data from Mutiny to Salesforce, the permission to create and update campaigns and campaign members needs to be granted and a variety of custom fields for Mutiny data needs to be created within Salesforce. In order to automate the process of granting this permission and creating these fields, you can download and install the Mutiny Reporting Package.

Navigate to https://app.mutinyhq.com/integrations and click on the Salesforce card. At the top of that page, click on the "Download Mutiny Reporting Package" button.
After downloading the package, you will be redirected to Salesforce to log in and install the package. It is advised to select "Install for All Users" or "Install for Specific Profiles..."; if selecting the latter please be sure the package is installed for all profiles of users who will want to view Mutiny data. Some users may not have permissions to install the package. If this is the case, please contact your Salesforce admin for assistance. You can learn more about installing packages to Salesforce here.
After installing the package, you'll want to confirm the installation. Within Salesforce, navigate to Setup > Apps > Packaging > Installed Packages and confirm that the "Mutiny Salesforce Integration" is installed. You can also navigate back to https://app.mutinyhq.com/integrations to confirm that all fields are marked with a green checkbox under the "Reporting State" dropdown.
You'll now want to ensure that any user that wants to build reports with the Mutiny data has permission to do so. Ensure that those users have the "Mutiny Admin" permission set under their user permissions.

Next steps

Now that you've set up your integration, you'll need to setup your campaign sync settings. If you didn't do so in this process, you'll also want to make sure you're mapping the columns that Mutiny should be ingesting.

Setting up your Salesforce integration