Skip to main content
Connecting Unbounce

Configure your Unbounce landing pages to send leads to SmartMoving

Matt Honeycutt avatar
Written by Matt Honeycutt
Updated over 3 years ago

SmartMoving provides support for direct integration with Unbounce.  No third party tools are necessary to get leads from your Unbounce pages to go directly into the SmartMoving platform.

There are three steps to get your Unbounce landing pages configured:

Step 1:  Retrieve the unbounce API URL and provider key from your SmartMoving account.

The API URL and provider key are unique for each SmartMoving account.  You'll need to navigate to your SmartMoving Settings -> Sales -> Lead Providers.  From here, you'll need to turn on the Unbounce lead source.  Once the lead source is enabled, SmartMoving will prompt you to enter an email address to send the unique API URL and provider key to.

Turn on the Unbounce lead provider in your SmartMoving settings:


Enter the email address of the person / company that will be configuring your Unbounce integration.

Once you have this API URL and unique provider key, proceed to step 2.  The URL will look similar to this example:

https://api.smartmoving.com/api/leads/from-provider/unbounce?providerKey={providerkey} where "providerkey" is your unique key


If you do not wish to have the instructions emailed, you can simply select the "do not send an email" option.  You'll then have the option to view the instructions manually and copy the URL yourself.

Example of manually copying the URL:

Step 2: Define a Webhook, and point it at your SmartMoving Unbounce URL from the previous step

  

Step 3:  Map your form fields to the supported SmartMoving fields:


For a list of form fields that SmartMoving supports please see the supported fields section of the SmartMoving API integration guide.  This guide will provide you with the specific key/value pairs that our platform supports.  

Note that if there are additional fields that you need to send to the platform that are not supported directly, these can be sent in as "custom" fields per the guide instructions.

Did this answer your question?