Skip to main content

Integrating Meta Lead Ads with SmartMoving via Zapier

Send Meta lead ads into SmartMoving automatically with Zapier and the Custom Lead Provider webhook, so leads from your Facebook and Instagram forms reach your pipeline without manual entry.

Written by Michelle Carone

Overview

Connecting Meta lead ads to SmartMoving through Zapier means every person who submits your Facebook lead ad form arrives in SmartMoving as a new lead, tagged with a referral source you choose.

  • Meta does not send leads to SmartMoving directly. Zapier watches your Facebook lead ad form and posts each lead to SmartMoving for you.

  • SmartMoving does not have its own app in the Zapier app directory. The connection uses the Webhooks by Zapier action, which posts to the address your Custom Lead Provider setting generates.

  • Leads created this way behave like any other lead in SmartMoving. They appear in your pipeline, count in your reports, and can be filtered by referral source.


Before You Start

Gather the following before you begin the Meta lead ads setup:

  • An admin role in SmartMoving. Enabling Custom Lead Provider requires access to Settings.

  • A paid Zapier plan (Professional or higher). Webhooks by Zapier is a premium app and is not available on the Free plan.

  • A Meta Business account with a published lead ad form.

  • Admin access to the Facebook Page that runs the lead ad form. Zapier asks you to select that Page when you connect the trigger.

  • If your Page restricts lead access, give Zapier CRM access in Meta Business Suite under Business settings → Integrations → Leads Access. Zapier cannot read your leads without it.


Step 1: Enable Custom Lead Provider in SmartMoving

The Custom Lead Provider setting generates the address that Zapier posts your Meta leads to.

  1. Go to Settings → Sales → Lead Providers. The list of lead providers opens.

  2. Find Custom Lead Provider and turn the toggle on. The toggle turns green and a dialog opens with connection instructions.

  3. If your company has more than one branch, choose the branch for these leads under Choose Branch. The URL in the dialog updates to include that branch. Leave it on Primary Branch to send leads to your primary branch.

  4. Click the clipboard icon next to the URL in the dialog. The full posting URL copies to your clipboard. Save it somewhere you can reach during the Zapier steps.

To reopen the dialog later, click View Instructions next to Custom Lead Provider.

The copied URL looks like this:

https://api.smartmoving.com/api/leads/from-provider/v2?providerKey={provider_key}

With a branch chosen, it ends in the branch ID:

https://api.smartmoving.com/api/leads/from-provider/v2?providerKey={provider_key}&branchId={branchId}

💡 SmartTip: One Custom Lead Provider address can serve several lead sources at once. Set the referralSource field in each Zap to tell them apart in reporting.

💡 SmartTip: On the Lead Providers list, Unit Cost records what you pay per lead for reporting, and Forward To emails a copy of every lead to an address you choose.


Step 2: Create the Zap and Set the Meta Trigger

The trigger is the event in Meta that starts the Zap.

  1. Log in to Zapier and create a new Zap. A new Zap opens.

  2. For the Trigger, choose the app Facebook Lead Ads. This is the name of Meta's lead ads app in the Zapier app directory.

  3. Choose the event New Lead. The Zap runs each time someone submits your form.

  4. Connect your Facebook account. Zapier asks for permission to read leads from your Pages. Allow every permission it asks for, including Leads Access.

  5. Select the Page that runs your lead ad. The Page is required.

  6. Select the Form if you want the Zap limited to one form. Leaving the form blank lets the Zap run for every lead form on that Page.

  7. Create a test lead with Meta's Lead Ads Testing Tool: pick your Page and form, click Create lead, then click Test trigger in Zapier. Your form's questions appear as fields for the next step.


Step 3: Add the Webhook Action That Sends the Lead to SmartMoving

This step posts the Meta lead to your SmartMoving Custom Lead Provider address.

  1. Add a step and choose Webhooks by Zapier. The action options open.

  2. For the Action Event, choose POST, then click Continue. The webhook configuration fields appear.

  3. In URL, paste your Custom Lead Provider URL from Step 1.

  4. Set Payload Type to Json. SmartMoving cannot read the default Form payload and returns "Unable to parse payload."

  5. Optional: under Headers, add Content-Type with the value application/json. Json payload already sends this.

  6. Under Data, enter a SmartMoving field name on the left and select the matching Meta lead value on the right. Repeat for every field you want to send.

  7. Leave the other options (Wrap Request In Array, File, Unflatten, Basic Auth) at their defaults.

Webhooks by Zapier settings at a glance

Setting

Value

Action Event

POST

URL

The URL copied from the Custom Lead Provider dialog

Payload Type

Json

Data

The fields from the tables below

Wrap Request In Array, File, Unflatten, Basic Auth

Leave at default / blank

Headers

Optional: Content-Type = application/json

Mapping your Meta form questions

Meta's standard questions arrive in Zapier under names like the ones below. Names depend on your form, so confirm them against your test lead.

Meta form question

Zapier field, for example

SmartMoving field in Data

Full name

Full Name

fullName

First name / Last name

First Name / Last Name

firstName / lastName

Email

Email

email

Phone number

Phone Number

phoneNumber

Street address, City, State, Zip code (current home)

Street Address, City, State, Zip Code

originStreet, originCity, originState, originZip

Custom question: "Where are you moving to?"

Your question text

destinationAddressFull (or destinationZip if you only ask for a ZIP)

Custom question: move date

Your question text

moveDate

Custom question: home size

Your question text

moveSize (answers must match your Move & Room Sizes names exactly) or bedrooms

Consent / opt-in checkbox for texts

Your question text

userOptIn (true or false)

Any other question

Your question text

notes, or a name of its own (it is added to the lead's note)

(fixed value, typed in)

None

referralSource = Facebook

(fixed value, optional)

None

leadCost, serviceType, opportunityType

SmartMoving Field Names for the Data Section

This table lists the fields the SmartMoving Lead API accepts. Enter the name exactly as shown in the left column of the Data section. Field names are not case-sensitive.

SmartMoving field

What to map from the Meta lead

Required

firstName

The person's first name

One name field is required

lastName

The person's last name

One name field is required

fullName

The person's full name in one value

One name field is required. Used first if it has a value.

email

Email address

No

phoneNumber

Phone number

No

extension

Phone extension

No

phoneType

One of Mobile, Home, Office or Other. Left blank or unrecognized, SmartMoving saves the number as Mobile.

No

userOptIn

true or false. Map it from the consent question on your Meta form. If you leave userOptIn out, SmartMoving saves the lead as agreeing to text messages, so send false when the person did not agree.

No

moveDate

Requested move date

No

originAddressFull

The whole origin address in one value

No

originStreet, originCity, originState, originZip

The origin address split into parts

No

destinationAddressFull

The whole destination address in one value

No

destinationStreet, destinationCity, destinationState, destinationZip

The destination address split into parts

No

moveSize

Size of the move. Use the exact name of a Move Size in Settings → Estimates → Move & Room Sizes. A name that does not match creates a new Move Size.

No

bedrooms

Number of bedrooms (added to the lead's note)

No

serviceType

One of Moving, Packing, MovingAndPacking, LoadOnly, UnloadOnly, Commercial, StorageInBound, StorageOutBound, InnerHouse, JunkRemoval or LaborOnly, spelled exactly as shown. A service type you created yourself also works if the name matches.

No

opportunityType

One of Local, Intrastate or Interstate. Leads default to Local when this is left out.

No

notes

Any extra text from the form

No

referralSource

A fixed value such as Facebook. This controls the referral source on the lead.

No

leadCost

What you paid for this lead, as a number such as 25. Overrides the Unit Cost set on the Custom Lead Provider for this lead.

No

branchId

The SmartMoving ID of the branch the lead belongs to. The easiest way to get it is to pick the branch under Choose Branch in the Custom Lead Provider dialog; the copied URL then ends in &branchId= followed by the ID.

No

How SmartMoving reads these fields:

  • At least one name field (fullName, firstName or lastName) must have a value. If you send fullName and the first and last name, fullName is used.

  • Use either the address parts or the full address for each location. If you send both, the full address is used.

  • Any field name that is not in the table is accepted and added to the lead's note. For example, sending originNumberOfFloors with a value of 2 records that detail in the note. If the name matches one of your Custom Information Fields (Settings → Estimates → Custom Information Fields), the value also fills that field.

Tracking Your Meta Ad Performance

The SmartMoving Lead API also accepts UTM values, which let you report on which Meta campaign produced a lead. Map any of these in the Data section:

  • utmSource, utmMedium, utmCampaign

  • utmAdGroup, utmContent, utmKeyword

  • utmCustomTracking

For example, map the campaign name to utmCampaign, the ad set name to utmAdGroup, the ad name to utmContent, and type facebook into utmSource.


Step 4: Test the Zap and Turn It On

  1. Run the test on the Webhooks by Zapier step. Zapier posts the sample lead to SmartMoving and shows the response. A successful test shows a leadId in the response.

  2. Log in to SmartMoving and find the lead in your pipeline. Confirm the name, phone number, email and referral source arrived as you expect.

  3. Turn the Zap on. Meta leads flow into SmartMoving from this point forward.

Note: Change at least one value between test runs. SmartMoving permanently rejects a second copy of an identical payload, so repeating the same sample lead returns an error rather than creating a second lead. A new lead from Meta's Lead Ads Testing Tool is always different, so it avoids this.


Prefer Not to Use Zapier?

You can skip Zapier by sending your Meta ads to your website instead of a Meta instant form. Set the ad's destination to the page with your SmartMoving quote form. Leads then arrive through your website lead form like any other website lead, with no Zapier plan. Customers fill in your form on your site rather than inside Facebook, which usually means fewer but more complete leads.


Key Details

These behaviors apply to every lead sent through the Custom Lead Provider address, including Meta lead ads:

  • SmartMoving has no app in the Zapier app directory. There is no SmartMoving trigger or action to search for. Every lead posts through Webhooks by Zapier.

  • Only a name is required. A lead is created as long as it carries a value in fullName, firstName or lastName. Every other field is optional.

  • Text consent defaults to yes. A lead sent without userOptIn is saved as agreeing to text messages. Send false for anyone who did not consent.

  • Referral source defaults to Custom Lead Provider. When the payload leaves referralSource out, the lead shows "Custom Lead Provider" as its source. The first lead carrying a new referralSource value adds that value to your Referral Source list in Settings → Sales → Referral Sources.

  • Move date accepts five formats: MM/DD/YYYY, MM-DD-YYYY, YYYY/MM/DD, YYYY-MM-DD and YYYYMMDD, and most other common date formats. A value SmartMoving cannot read leaves the move date blank on the lead, and the raw value still appears in the lead's note on a line reading "Move date:".

  • An unrecognized service type does not block the lead. SmartMoving creates the lead and adds "Unsupported service type:" followed by the value to the note.

  • An unrecognized branch ID does not block the lead. SmartMoving creates the lead at your primary branch and adds "Unknown branch ID:" followed by the value to the note.

  • An unmatched move size is added to your settings. A moveSize value that does not match an existing Move Size creates a new one in Settings → Estimates → Move & Room Sizes.

  • Duplicate rejection is permanent. SmartMoving compares the provider key, the branch and the complete set of values sent. An exact repeat is rejected for good, not for a set window.


Best Practices

  • Keep Meta's own lead notification emails turned on as a backup, so a Zap failure does not cost you the lead.

  • Set referralSource to a fixed value such as Facebook in every Meta Zap, so Meta leads separate cleanly from Yelp and website leads in your reports.

  • Map userOptIn from the consent question on your Meta form rather than sending true for everyone or leaving it out, which counts as consent.

  • Change the name or email between test runs, because SmartMoving rejects an exact repeat of a payload it has already accepted.

  • Map origin and destination whenever your Meta form collects them, so estimators have addresses to work from on first contact.


Troubleshooting

  • Zapier shows a 400 error saying "Unable to parse payload."

    • The webhook is not sending JSON. In the Webhooks by Zapier step, set Payload Type to Json and test again.

  • Zapier shows a 400 error saying "At least one name field is required."

    • None of fullName, firstName or lastName has a value. Map the name from your Meta form in the Data section, and check that the test lead has a name.

  • The Facebook Lead Ads trigger finds no leads, or Zapier reports that CRM access was revoked.

    • In Meta Business Suite, open Business settings → Integrations → Leads Access, choose your Page, and give Zapier CRM access. Then create a new test lead and test the trigger again.

  • Zapier shows a 400 error saying the lead has already been submitted.

    • SmartMoving rejects a payload identical to one it already accepted, and that rejection is permanent. The full message reads "This lead has already been submitted. Please contact SmartMoving support." Change at least one value, such as the name or email, and run the test again.

  • The lead reaches SmartMoving but the move date is blank.

    • SmartMoving reads move dates in MM/DD/YYYY, MM-DD-YYYY, YYYY/MM/DD, YYYY-MM-DD and YYYYMMDD. A Meta form that collects the date as free text often sends something else. Open the lead's note and look for the line starting "Move date:" to see the raw value, then add a Zapier Formatter step to convert it before the webhook.

  • Meta leads show a referral source of Custom Lead Provider instead of Facebook.

    • The payload is missing the referralSource field. Add referralSource to the Data section of the Webhooks by Zapier step with a fixed value such as Facebook. Leads already in SmartMoving keep the old source and need updating by hand.

  • Zapier returns an error saying the provider is disabled.

    • The Custom Lead Provider toggle in Settings → Sales → Lead Providers has been turned off. Turn it back on. The provider key stays the same, so the Zap needs no changes.

  • The Zap reports success but no lead appears in SmartMoving.

    • Check that the URL in the webhook step still carries the providerKey value, that Payload Type is set to Json, and that a name field is mapped. A payload with no name is rejected. Also check the pipeline of the branch in your URL; leads with no branch go to your primary branch.

  • Meta leads land at the wrong branch.

    • Leads with no branch in the URL or payload go to your primary branch. To route this Zap somewhere else, pick the branch under Choose Branch in the Custom Lead Provider dialog and paste the new URL into the webhook step, or map the branchId field in the Data section.

  • The lead's note says the service type is not supported.

    • The value sent in serviceType does not match a SmartMoving service type. Use one of Moving, Packing, MovingAndPacking, LoadOnly, UnloadOnly, Commercial, StorageInBound, StorageOutBound, InnerHouse, JunkRemoval or LaborOnly, spelled exactly as shown, or match the name of a service type you created.

Did this answer your question?