How can we help you?

For the integration to work you will need the API key from Salesforce CRM that can be accessed only by Salesforce Enterprise users or above. Note that the Salesforce CRM free trial does not have access to "Web Services API", needed for the integration.

Our integration also requires a Salesforce license or a Salesforce Integration license, but not a Salesforce Platform license.

Note that for the Salesforce Integration license the proper permissions must be granted. You can see the differences here: https://d.pr/3dFkf1. To check what license your account has, go to Setup > Company Profile > Company Information > User Licenses:

If you do not have this license, you will be able to connect the Salesforce account to your Instapage workspace, but you will encounter an error when trying to integrate any page.

NOTE: Our direct Salesforce integration doesn’t work with Salesforce sandbox accounts.

While in the Landing Pages list, click on the name of the desired page and select Integrations -> Form Integrations:

If you have already connected your Salesforce account to Instapage, you will see it here and you can select it. Otherwise, you will see the message below, and you can go to the main Integrations Dashboard to connect.

Select the workspace you want, Settings, then click Integrations. Click on Continue To Salesforce, as connecting the integration requires confirmation from within their app.

Sign in and connect the account. This step is done once per workspace. When you have connected the account, come back to the slideout menu for the page you want to integrate with Salesforce and continue with the steps below.

Our direct integration is using the API of Salesforce and in order to correctly connect your Salesforce account, you need to be the Salesforce account owner or a team member/user with API permissions.

Please note that our integration will read only the fields from the "Leads" object in Salesforce. You will not be able to send data to fields from other objects (such as "Contacts"). 

Create the setup to receive leads from Instapage to your Salesforce account by going to Setup - Build - Customise - Leads - Fields - Lead Fields.

Scroll down the page and at Lead Custom Fields and Management, click on New.

This will take you to Step 1: "Choose the field type". 

Press Next, and you will be taken to Step 2: "Enter the details".

For custom fields that you created in the "Leads" object in Salesforce manually, make sure that Step 3: "Establish Field Level Security" has the System Administrator option checked as visible.

Step 4: "New custom field" will allow you to click Save & New to create more custom fields or click Save if you are done.

NOTE: Only one account can be connected at a time, even if you have the option of adding more accounts to the list. 

In the next step, you can choose the campaign you want to use. You can also choose if you want leads to be updated or duplicated in case that the same contact signs up more than once.

Then you need to map your Instapage fields to the Salesforce fields and click Continue;

Field mapping is the most important step in the setup process. To ensure your leads are successfully accepted by Salesforce, you must adhere to the following mapping logic:

• Map All Required Fields: Every field marked with an asterisk (*) must be mapped. If a required field is missing, the integration will fail. The 'email' field is strictly required for every submission.
• Internal Value Matching: If a Salesforce field has predefined "internal values" (dropdowns, checkboxes, or radio buttons), your Instapage field must use the exact same options/values, including exact upper and lowercase, spacing, and characters.
• Type Consistency: We strongly recommend that fields on both sides (Instapage and Salesforce) share the same data type (e.g., Text to Text, Number to Number). There are exceptions, so make sure you respect the field values and type limits, then test the integration to see if it works.
• Field Incompatibility: Instapage multi-selection checkboxes are incompatible with Salesforce Multi-select Picklists because Instapage separates values with commas, while Salesforce requires semicolons.
• Required/Optional Fields: Salesforce Last Name and Company fields are optional by default, but if you include them in one form on your page, they automatically become required for all other forms on that same page. To avoid integration errors, if these fields are present on one form, you must also include and map them on every other form on that page
• The [None] Option: Selecting [None] for an Instapage field means that the specific data will not be sent to Salesforce.
• Auto-Generate Functionality: Using Auto-Generate will automatically create a new text field within your Zoho list properties to house that specific data.
• Custom Fields Limitation: We support a limit of 100 custom fields. If you have more than 100 custom fields, your integration/field might not work. You can either delete the extra fields or use predefined ones in this case.

If you went through all the steps, click on FINISH, and you should see a confirmation message.

Then click on CLOSE.

In order for the changes to save on the page, you still need to update the experience. So after clicking on CLOSE, head back to the first page slide-out to UPDATE the page experience.

Note: While we try to keep all of our instructional articles that involve third-party services up to date, sometimes they make changes to their platform of which we are not aware, and, as a consequence, the user interface may differ from the provided screenshots.

NOTE: Salesforce CRM allows 5 connections per application. This means that with Instapage you will be able to connect the same Salesforce account to 5 workspaces. If you connect it to the 6th workspace the oldest connection will be revoked.
This does not refer to how many pages you can integrate with the same Salesforce account, which is unlimited.
In case you want more than 5 connections with Instapage (the same Salesforce account connected to more than 5 workspaces) you can contact Salesforce support and try to increase your per-app connection limit. To see more about this topic, you can refer to Salesforce's official documentation here: https://d.pr/fCoxf7 

NOTE: Our in-app integration with Salesforce uses the Sforce-Auto-Assign: TRUE Assignment Rule Header. Because of this, the active assignment rules are used.
If you would like to control the value for Sforce-Auto-Assign please let us know. We do not have a way of enabling this currently, but we will log a feature request with our Product Team on your behalf.
As a workaround, you can look into one of the alternatives described in this article: https://d.pr/6evO8O to replace the in-app Salesforce integration.