Skip to main content
All CollectionsLeads
Capturing Leads in Salesforce
Capturing Leads in Salesforce

Leads can be pushed to SalesForce

Bryan Nye avatar
Written by Bryan Nye
Updated over a week ago

To enable this feature, reference the following settings under the Lead Generation tab of the Interface Builder. In legacy interfaces, these options are found under Contact Form Settings.

First set Enable SalesForce Leads to "Yes", then add your Salesforce-provided Organization ID (OID).

To obtain your SalesForce OID, log into SalesForce and go to Setup > Administer > Company Profile > Company Information.

Leads submitted via the store locator interface will now appear within SalesForce as Leads, as shown here:

To customize the fields that appear in MetaLocator, provide a SalesForce URL Template similar to the following{last_name}&first_name={first_name}&email={from}&description={message}&00No0000002vITY={custom1}

The template should be a single line, with no line breaks. It should always begin with:

MetaLocator will insert the OID automatically from the setting above.

The query string should be a series of pairs which set the SalesForce field name to the property value from the Lead object.

Using the Interface Builder template editor, you can also insert your own custom fields into the form by adding a custom field, and modifying the HTML to create a hidden form field which can be set to any dynamic data element from the template objects.

In the below example, we create a template with a hidden variable set to the location name.

This will be "posted" with the form and can be used in the Salesforce URL Template as:


Where 00No0000002vITY is the SalesForce Field ID where you want to store the location name.

Using custom1, custom2 and so forth (up to custom40) ensures the values are also saved in the MetaLocator lead database. You can prevent storage in MetaLocator by using an organizationally namespaced field such as my_custom1, or whatever unique field value is appropriate which also doesn't overlap with the MetaLocator field object names.

Did this answer your question?