Thanks to the Wisepops & Salesforce integration, you can synchronize the leads collected by Wisepops as Salesforce Contacts, or Salesforce Person Accounts.
Supported Salesforce editions
REST API access is enabled by default in Enterprise, Performance, Unlimited, and Developer Edition orgs. Professional Edition orgs can add API access as an add-on. For more information, visit Salesforce Help: Add Products and Licenses with the Your Account App or contact a Salesforce account executive. Learn more.
Connect your Salesforce account
Follow these steps to connect your account:
Log in to your Wisepops account
Open or create a popup with a sign-up form
Click your sign-up form
In the left menu, click Sync
Click the Salesforce logo
In the window that opens, log in to your Salesforce account, and click Allow,
You're done!
Sync as Contacts or Person Accounts
Once you've activated the Salesforce sync for a campaign, Wisepops asks you to choose a list. This is the Salesforce destination object.
If you have enabled Person Accounts in your Salesforce org, you can choose Person Accounts instead of Contacts. In this case, each contact synced by Wisepops is also linked to an Account.
How fields are mapped
The following fields are mapped automatically to Salesforce fields:
Email: to Salesforce Email
Phone: to Salesforce Business Phone
First name: to Salesforce First Name
Last name: to Salesforce Last Name
Last name is set by default to -
The contact's last name is required by Salesforce. To synchronize leads without last name, Wisepops defaults it to the hyphen (-).
You can set the mappings of fields in the Wisepops builder. Both Salesforce standard fields and your own custom fields are supported.
Troubleshooting
If you have any issue syncing your leads with Salesforce, you should try to export your collected data. In the generated CSV, a column named "Sync Salesforce" shows the response we received from the Salesforce API.
Here are common sync errors, and how you can fix them.
Cannot deserialize instance of boolean from VALUE_STRING
This happens when the Salesforce field expects a boolean value (true or false). You must provide either true or false, lowercased. Like this:
