Salesforce Requirements and Permissions

Within Primer's Salesforce integration, the fusion of Primer's third-party data with your Salesforce records is conducted with a strong focus on security. This approach ensures that your data remains protected throughout the process. We require only a minimal mapping of fields which are used to join Primer's data to your Salesforce records. These records empower you to enrich your data for more targeted ad audiences and efficient CRM data management. To address potential security concerns, Primer adopts a meticulous strategy, storing a secure copy of the mapped fields records from Salesforce only to optimize the speed of enrichment and sync performance. If you have any inquiries or concerns regarding security, our CS team is equipped to provide a detailed overview of our approach, emphasizing how Primer minimizes security risks throughout the integration process.

The Primer Service Account will need at least the below permissions to connect to your Salesforce successfully.

Pre-requisites

• 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. Primer primarily uses the Salesforce Bulk API to sync data to Salesforce in the most API quota-efficient way possible.

• Ensure the account is API Enabled with the Session Security Level Required at Login set to "None."

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," and "Account" objects. Primer does not currently delete any records, and we will never delete or overwrite data unless you explicitly ask.

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

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.

Object Permissions

Object	Minimum Access	Functionality
Lead	Read	Base application
Contact	Read	Base application
Account	Read	Base application
Campaign	Read	Campaign Bulk Import
Opportunities	Read	Conversion Reporting