Connecting to SalesForce

Setting Up Salesforce

Documentation 

Setting up Salesforce 

If you have a Salesforce org, this document will help you set up integration with your Oneclickpolitics service. 

Feature Summary 

Oneclickpolitics will sync your campaigns and signatures over as several different Salesforce native and custom objects: 

The signature's contact info is synced over as a Salesforce Contact using an email field of your choice for deduplication. If you have a Contact with that email address it will be updated; otherwise a new Contact is created. 

Campaigns are sent over as Messages, and Contacts are joined to the Messages they sign with a join record. 

When a signature results in deliveries, we send these as Delivery objects, joined to both the Contact that sent them, and the Message sent. These records will include information about the recipient of the message, and the type of delivery - e.g. email, or fax. 

For more detail on the objects and fields used, see the Custom objects and fields section at the end of this document. 

Two Way Syncs 

We also offer two-way syncs so changes to your Contacts in Salesforce can propagate back to Oneclickpolitics. 

We automatically de-duplicate Contacts sent to Salesforce by their email addresses. Sometimes however, Salesforce Contacts with different emails will show signs of belonging to the same household or advocate. Occasionally someone will sign your campaigns with different email and physical addresses as they change occupations or residences. 

www.oneclickpolitics.com | 202-800-8877 | sales@oneclickpolitics.com 1

Setting Up Salesforce

Documentation 

This is when Salesforce Contact merges can help, either through the lightning interface or a plugin like Duplicate Check. 

https://www.plauti.com/products/duplicate-check?gad=1 

With two-way syncs enabled, your Salesforce merges update Oneclickpolitics. If any new signatures come in from duplicate addresses, they are synced to the merged master Contact. 

For example, if you merge Salesforce Contacts a@test.com and b@test.com into c@test.com, new signatures from the former two emails are synced as signatures from the third. Signatures from emails flagged as duplicates will never re-create unwanted Contacts. 

Please email support@oneclickpolitics.com for more information on two-way syncs. 

1. Installation 

As a first step, install the Oneclickpolitics managed package on your Salesforce org. 

The package install link depends on whether you are using a standard Salesforce org or a sandbox or scratch org. 

For a standard org, the install link is: 

https:/ login.salesforce.com/packaging/installPackage.apexp?p0=04t5i000000EcwK For a sandbox org, the package install link has the subdomain test.salesforce.com: https:/ test.salesforce.com/packaging/installPackage.apexp?p0=04t5i000000EcwK 

2. Connecting 

After you install the package, you’ll need to connect Oneclickpolitics to Salesforce from inside of your Oneclickpolitics dashboard. You only need to complete this step once - once connected, Oneclickpolitics will remember your Salesforce org. 

Login to Oneclickpolitics, and select Settings, and then Salesforce, from the menu on the left. 

www.oneclickpolitics.com | 202-800-8877 | sales@oneclickpolitics.com 2

Setting Up Salesforce

Documentation 

Choose the Connect header. If you haven’t yet connected the two services, you’ll see two buttons here - one for connecting standard Salesforce orgs, and one for sandbox orgs. 

Press the Connect button that applies to your org. 

You’ll be redirected to a Salesforce login to enter your org’s credentials. Salesforce will also list the permissions it needs to grant Oneclickpolitics to allow syncs. Confirm these, and you’ll be redirected back to your Oneclickpolitics dashboard. 

Salesforce and Oneclickpolitics will now be connected, and Oneclickpolitics will remember your Salesforce org. 

3. Configuring Mappings 

We use default fields like “Email,” “MailingStreet,” and “HomePhone” when syncing your signatures to Contacts. If your Salesforce Contacts use nonstandard or custom fields, you can use the Contact Field Mappings header to ensure your Oneclickpolitics syncs use these instead. 

www.oneclickpolitics.com | 202-800-8877 | sales@oneclickpolitics.com 3

Setting Up Salesforce 

Documentation 

Use the dropdowns to map signature fields to certain native Salesforce Contact fields, or supply the name of an existing custom field on your Salesforce Contacts. 

www.oneclickpolitics.com | 202-800-8877 | sales@oneclickpolitics.com 4

Setting Up Salesforce

Documentation 

Click Save after changing these mappings, and then, after saving, press Test Sync to sync over a single Contact record with the relevant mappings applied. 

The test Contact will use the address “test.contact@oneclickpolitics.com” in the appropriate email field. 

Look for this Contact in Salesforce to confirm that it was created or updated in the test sync. This will ensure that your custom field names are all valid and entered correctly. 

4. Prepare for Syncing 

Once you’re satisfied with your Contact mappings, we can start sending over your records in nightly syncs. 

From the Syncs header, you can see if nightly syncs are turned on or off, and use the toggle to turn them on. You can also contact support@oneclickpolitics.com and let us know you're ready to have your syncs turned on. 

We use the Salesforce Bulk API to sync large numbers (“blocks”) of records at once. This works for almost all orgs and will probably work for yours, but for certain orgs that can’t handle this throughput, we can sync in small blocks, or fall back on the Composite API. 

5. Custom Objects and Fields 

For the Contact object, we add three custom fields: 

www.oneclickpolitics.com | 202-800-8877 | sales@oneclickpolitics.com 5

Setting Up Salesforce

Documentation 

OCP__federal_district__c (a text field with the Contact's federal electoral district) OCP__state_district__c (a text field with their state electoral districts) OCP__advocate_id__c (a text field with an external identifier) 

For campaigns, we add the Message custom object, with a Name field for the campaign name. 

We join Messages to the Contacts that sign them via the ContactMessageAssociation join object. 

For message deliveries, we add a Delivery custom object: 

OCP__Delivery__c 

with fields: 

OCP__Contact__c (referencing the Contact record it joins) 

OCP__Message__c (referencing the Message record it joins) 

OCP__Text__c (a rich text area field for the delivered message contents) OCP__Recipient__c (a text field with the recipient's name) 

OCP__Type__c (the type of delivery, e.g. an email or a phone call) 

OCP__Date__c (when the delivery was made) 

OCP__OcpId__c (an external I'd) 

www.oneclickpolitics.com | 202-800-8877 | sales@oneclickpolitics.com 6

NOTE: When connecting to SalesForce for the first time. The connection Info will be blank. There is nothing you need to do there. These fields will populate after you have established a successful connection by selecting “Connect” and under Connect Salesforce - Select Connect. It will take you to your instance of SalesForce to login.