Salesforce Access & Field Creation

This article outlines the access Postal requires as well as any custom fields that need to be created to ensure your Salesforce Integration runs smoothly.

Object Access & Reasoning

Postal requires access to various Salesforce Objects. Here is a breakdown of the reasoning and exact fields.

Object	Access	Reason	Fields
Lead	Read/Write	We read leads to load in the lead's profile data. We update custom fields on the lead to help with ROI reporting.	ID OwnerID CreatedDate LastName FirstName Title Email Company Street City State PostalCode Country MobilePhone Phone
Contact	Read/Write	We read contacts to load the contact's profile data. We update custom fields on the contact to help with ROI reporting.	ID OwnerID AccountID CreatedDate LastName FirstName Title Email MailingStreet MailingCity MailingState MailingPostalCode MailingCountry MobilePhone Phone
Account	Read/Write	We read accounts so we can associate the account name with your contacts in Postal. We update custom fields on the account to help with ROI reporting.	ID OwnerID ParentID Name Website CreatedDate
User	Read/Write	Assign Contact ownership based on Salesforce and sync Users to Postal.	ID IsActive LastName FirstName Email Username FederationIdentifier FullPhotoURL
Task	Create	We create tasks when actions occur in Postal. Note: the picklist value Postal* must be created for the Type field.*	WhoId OwnerId Type Subject Description ActivityDate Priority Status Reminder Set
Campaign	Read	Our UI needs to load a list of campaigns so we can allow a user to select which campaign to map an item to.
Campaign Member	Read/Write	We need to be able to associate and update campaign member statuses when items are sent
Opportunity	Read	We read opportunities to help report on ROI and for trigger filters
Event	Read	We read events to allow triggering off the event object

Note! The picklist value Postal must be created for the Type field.

Good to know!

You can avoid common sending issues by checking to see that the API Integration user is able to access all of the above objects and fields. See the Field Level Security Permissions article from Salesforce.

Custom Field Creation

Postal will automatically create the following fields when installing the Salesforce Managed Package:

Object	Access	Reasoning	Fields
Account	Read/Write	Surface the total spend associated with your accounts	Total_Postal_Spend__c
Contact	Read/Write	Surface various data points to the Contact.	Postal_Cost__c Postal_Cost_Per_Touch__c Postal_Created__c Postal_Touches_Count__c
Lead	Read/Write	Surface various data points to the Lead.	Postal_Cost__c Postal_Cost_Per_Touch__c Postal_Created__c Postal_Touches_Count__c
Task	Read/Write	Surface various data points to the Task.	Postal_Name__c Postal_Total_Cost__c

Definitions

Postal Touches = count of items sent
Lead Cost/Contact Cost = total cost of items sent to that lead/contact
Cost Per Touch = average cost of items sent to that lead/contact

Best Practice! Organize your layouts to keep all the Postal fields together in one section.

Manual Field Creation

Postal ABM requires custom fields to be created. Please see our Syncing Postal Account Data to Salesforce article for more information.

Explore the Postal + Salesforce integration using our Salesforce Integration Hub article!

Salesforce Access & Field Creation

Object Access & Reasoning

Good to know!

Custom Field Creation

Manual Field Creation

Was this article helpful?

<%= previousTitle %>

<%= nextTitle %>