Salesforce Requirements and Permissions

Primer uses minimal field mapping to connect Primer's third-party data with your Salesforce records, enhancing your CRM advertising efforts.

Primer's integration with Salesforce prioritizes security, ensuring your data is protected. If you have questions about security, our customer support team can offer a clear explanation of how we maintain safety during the integration.

User Permissions

1. "API Enabled" must be checked

2. "Session Security Level Required at Login" must be set to "None".

3. High Assurance on Session security level required at login should be set to "Disabled" at the profile level. Salesforce blocks some API access when this setting is used on user Profiles and this will prevent Primer from accessing your Salesforce instance.

4. Primer will have the same access to objects and fields as the Salesforce user connected to Primer. So if fields are read-only or hidden for that user, that is what Primer will reflect.

   1. For text fields, the fields should be set as 'text' only as opposed to 'text area' fields.

   2. You should give Primer "Read" access to the "Lead," "Contact," "Opportunity," and "Account" objects. Primer does not currently delete any records, and we will never delete or overwrite data.

   3. Additional functionality for bulk import is available with allowing access to "Campaign" objects.

5. Salesforce requires that the user account have the "View Setup and Configuration". Ensure the user account have the "View Setup and Configuration" permission. This permission is set on the Profile of the connected user under the "Administrative Permissions" heading.

6. When connecting, the Salesforce authorization flow will request scopes api and refresh_token.

We recommend using a stand-alone account specifically for Primer (often called a Service Account) so you can see Primer updates in your audit history.

Object Permissions

Object	Minimum Access	In-App Functionality
Lead	Read	Audience Building
Contact	Read	Audience Building
Account	Read	Audience Building
Campaign	Read	Audience Building
Opportunities	Read	Audience Building

Permission Errors

From time to time, you may encounter two common errors with our Salesforce integration. These issues are generally related to the token used to connect Salesforce to Primer.

Quick Fix: Reconnect and Reauthorize Salesforce: If you’re experiencing an error, the simplest solution is to reconnect and reauthorize Salesforce with Primer. This step often resolves token-related issues quickly.

Common Causes of Salesforce Integration Errors

There are several common reasons why token-related issues occur with the Salesforce integration. These include:

1. Expired Token

   • Explanation: Tokens used to connect Salesforce accounts to Primer can expire periodically due to security or session settings.

   • Solution: Reauthorize your Salesforce connection to renew the token.

2. Inactive User Status

   • Explanation: If the person who initially connected Salesforce to Primer has since become an inactive user in Salesforce, this can disrupt the integration.

   • Solution: Ensure the connected user is active in Salesforce, or reconnect with an active user account.

3. Changed Permissions

   • Explanation: If the user’s permissions in Salesforce have been changed (e.g., role updates, restricted access), this may lead to integration errors.

   • Solution: Check and, if necessary, update the user permissions in Salesforce to ensure they meet the requirements for connecting with Primer.

Troubleshooting Guide

Regardless of the specific cause, the resolution steps are generally the same:

1. Reauthorize Salesforce: Disconnect and reconnect Salesforce in Primer to reset the token.

2. Double-Check User Permissions: Ensure the connecting user has sufficient permissions in Salesforce to maintain integration stability.

Following these steps should resolve most issues with the Salesforce integration. If you continue to encounter errors, please contact Primer support for further assistance.