Paminga Salesforce Integration Setup

Setting up Paminga's Salesforce integration can take as little as 30 minutes.

• Connect Paminga to Salesforce
• Adjust Integration Settings as needed
• Map fields between Salesforce and Paminga
• Kick off your first full sync (differential syncs will then run automatically)
• Add Paminga iFrames to your Salesforce layouts

Location in Paminga

Hover your user avatar in the upper right corner of Paminga and click on "Integrations".

You'll find many of Paminga's integrations listed alphabetically.

Scroll to Salesforce and click the "Configure" button.

Configure Your Salesforce Integration

Authorization

Begin the Process

Click the "Connect Salesforce Account" button.

Login to Salesforce

If you're not already logged in, Salesforce will prompt you to do so.

Login as Your Salesforce Sync User

Be sure to log in to Salesforce as the User that will be used for sync.

Grant Access to Paminga

Once logged in to Salesforce, you'll be asked to grant access to Paminga.

Note

This screen may reference "Net-Results", our old brand name, rather than Paminga.

Paminga requires permission to:

• Access the identity URL service
  This allows Paminga to login and get required info about the user
• Manage user data via APIs
  This allows Paminga to make the required API calls to sync data
• Perform requests at any time
  This allows Paminga to use "refresh" tokens

Click "Allow". You will be redirected back to Paminga (this may take a few seconds).

Authorization is now complete.

Sync Settings

The Sync Settings screen provides high-level control of certain aspects of your Salesforce Sync.

Salesforce Sync Settings

Below are explantions for all options on the Sync Settings page:

• Salesforce Instance URL: shows the URL of the Salesforce instance connected to your Paminga account
• Salesforce Username: show the username tied to the sync
• Syncs Enabled: enable or disable Paminga's Salesforce sync.
  If disabled, no data will sync to or from your connected Salesforce instance.
  While disabled, Actions in Paminga may queue records for sync to Salesforce (creation of Leads, for example).
  Re-enabling will cause those records to be created/synced.
• Using Salesforce Group/Essentials Edition: Group/Essentials Editions lacks a Campaign object.
  Checking this box causes Paminga to skip syncing to/from Salesforce Campaigns.
• Using Salesforce Person Accounts: Salesforce Person Accounts are commonly used in B2C e-commerce.
  Person Accounts combine fields from both the Account and Contact objects.
  Check this box if you're sure you're using Salesforce Person Accounts.
  If you have any doubts, please contact Paminga support.
• Full Sync & Error Notification Recipient: Optionally, you may choose to have email notifications sent whenever sync errors occur, or when a Full Sync completes
• Sync Only The Lead Score On A Lead Score Change:
  Paminga's Managed Salesforce Package creates custom fields for "Paminga Lead Score" on the Lead and Contact objects. The numeric value of this field is updated automatically when lead scores change.
  • With this box checked: the Lead or Contact record itself will not be updated per current values in Paminga when lead scores change
  • With this box unchecked: Paminga will update the Lead or Contact record itself per current values in Paminga when updating the lead score in Salesforce
• Allow Salesforce to Write Empty Fields to Paminga: Gives Salesforce the ability to "blank out" fields in Paminga when blanked out in Salesforce. An example:
  • The "Job Title" field is mapped from Salesforce to Paminga.
  • Due to sync, the value is the same in both Salesforce and Paminga
  • A Salesforce user "blanks out" or removes the job title in Salesforce (and saves their changes)
  • Do you want the job title field to be "blanked" in Paminga also? If so, check this box.
• Allow Paminga to Write Empty Fields to Salesforce: Same as above, but in the opposite direction.
  Best practice is to leave this box unchecked.
• Sync Email Event Activities to Salesforce: Create activies in Salesforce for email sends, opens, and clicks
• Sync Salesforce Campaign Members to Corresponding Lists in Paminga: When checked, Paminga will create a Marketing List for each of your Salesforce Campaigns and keep members in sync as they are added/removed in Salesforce
• Default Account Name: You may choose to have Paminga create Accounts in Salesforce. When doing so, if your Paminga contact lacks an account name, this default value will be used.
  An example use case is a Paminga contact created via a Form that does not ask for the prospect's company name.
• Default Last Name: Salesforce requires a last name when creating a lead or contact, but maybe you only have the lead's email address.
  In such a case, this default value will be used to fill the "Last Name" field in Salesforce.

"Run a Full Sync" Button

You'll see that the Sync Settings page includes a button to "Run a Full Sync", as well as the date and time the last full sync was run.

Learn about Full Syncs (and Differential Syncs) on the Syncing CRM Data page.

Field Mappings

You control which fields will be synced to Paminga from Salesforce – and vice versa – from within Paminga.

There's no need to involve (or wait for) a Salesforce Admin. Simple checkboxes let you decide which fields to sync.

You'll probably want to setup your Field Mappings before running your first full sync, but you may do so at any time.

Salesforce Sync Actions

Salesforce Sync Actions are an innovation unique to Paminga.

They allow you to trigger actions on Leads and Contacs as they sync to Paminga from Salesforce.

There's no need to create separate workflows (though you can do so if you choose).

On great use use is using sync actions to augment or transform data for hyper-personalization as it syncs to Paminga.

Sync Errors

Sync errors can occur for a variety of reasons.

Paminga provides a searchable table of all sync errors – that may be cleared individually or in bulk – to help you keep data flowing.