Lofty connects to Facebook lead ads through a native integration in its Lead Capture settings. You log in to Facebook, grant every permission requested, and pick one Page. Leads from any Lead Form Ad on that Page then sync into Lofty, and utm parameters on each form control the source, tags, lead type and search criteria that come with them.
Product details here come from Lofty’s Help Center and the Lofty and API Nation articles named below, as of October 2026. Verify them before you build, since Meta and Lofty both change their screens.
What does the native integration do, and what are its limits?
It pulls leads from Facebook Lead Form Ads on one connected Page into Lofty. According to Lofty’s Help Center, you need admin access to the Facebook Page, the ad account and Leads Access. Three limits matter before anything else:
- One Page per Lofty user account. Each team member can connect their own, but one user cannot connect two Pages.
- Lead Form Ads only. It does not cover Lofty landing page forms.
- Search criteria are capped. You can pass up to five listings, five cities and five ZIP codes.
If you run ads from more than one Page, the native route will not cover all of them. That is the main reason to look at Zapier or API Nation, covered below.
Setup steps, in order
- Confirm your Facebook roles first. You need Manage Pages, ad account access and Leads Access. Fixing this after a failed connection wastes more time than checking it now.
- Open Lead Capture in Lofty. Choose Facebook Ads and click Connect.
- Log in to Facebook and grant all permissions. Lofty warns that if you skip any, the integration will not work.
- Select the one Page. All lead forms on that Page sync.
- Add tracking parameters to each lead form. See the table below. Do this before you launch ads, because tags and lead types are set at import.
- Test with Facebook’s Lead Ads testing tool. Select the Page and form, create a test lead, then use Track Status to see errors.
- Check the lead in Lofty. Look at the source, tags, lead type, phone, email and notes.
- Attach follow-up. Make sure the new lead lands in the right smart plan and with the right agent. See smart plans vs manual follow-up.
How do the utm parameters map to Lofty fields?
Each parameter changes what Lofty does with the lead, so a typo changes your data. Lofty’s article says to set source, campaign, content and medium in Meta Business Suite under the form’s Tracking Parameters, and utm_term through the Lead Ads Forms library.
| Parameter | What Lofty does with it | Watch for |
|---|---|---|
| utm_source | Sets the lead source; defaults to Facebook | Used for routing, so keep names consistent |
| utm_campaign | Imported as a tag | Not usable for routing |
| utm_content | Imported as a tag | Not usable for routing |
| utm_medium | Sets lead type: Buyer, Seller, Buyer&Seller or Renter | Typed exactly; anything else becomes Other |
| utm_term | Search criteria: listing IDs, cities, ZIPs | Five per category; cities as “City, ST”; must fall in your MLS |
For utm_term, Lofty gives a template with listing IDs, an area list of cities, and ZIP codes without quotation marks. The listing ID is the Lofty listing ID from your website URL, not an MLS number. Delete unused slots and keep the formatting valid.
Our practical rule: name every form with one convention, such as source for the channel, campaign for the offer, and medium for Buyer or Seller. Then your tags and filters stay readable a year later.
Which form fields does Lofty read?
Lofty supports a defined set. Email and a first or full name are required. Other fields map to lead details:
- Buyer fields: time_frame, fthb (first-time buyer), preQual, sellHouse, hasBuyAgent
- Seller fields: mortgage, buyHouse, hasSaleAgent
- Contact: email, phone_number, first_name or full_name (a full name is split at the space)
- Custom questions: saved as notes on the lead profile
Lofty says time_frame values above 12 import as “Just Looking.” Use the supported field names where you can. Anything custom lands in notes, which are readable but not filterable like a real field.
Zapier or API Nation: when to use them
Use them when the native route does not fit, most often because you advertise from a second Page or want custom mapping. Lofty documents a Zapier route that uses the Facebook Lead Ads New Lead trigger and a Lofty Create Lead action, authorized with the API key from Settings > Integrations. Facebook Lead Ads is a Premium Zapier app, so you need a paid plan.
The Zapier route has limits worth knowing. Only new leads import, the form must be live when you set it up so fields appear, and a full name may need splitting. Lofty also warns that adding a form question for every Lofty field may lower conversion.
API Nation’s knowledge base describes a Facebook Lead Ads to Lofty sync with options to avoid overwriting existing contacts, mark leads private, send an alert or welcome email, and assign an agent. It says leads are added instantly but gives no timing figure. Compare the cost of an extra subscription against the cost of a missed lead, and pick one route per form so a lead is not imported twice.
Special ad categories and what they change
If your ads fall under Meta’s Special Ad Category for housing, targeting is restricted, and Lofty’s article does not discuss this. The ZIP codes in utm_term are CRM data that tell Lofty what the lead is interested in. They are not Meta targeting. We cover the rules in our guide to the Facebook Ads special ad category for real estate. Confirm the category and form restrictions that apply to your ads in Ads Manager.
Troubleshooting list
- Leads missing entirely. Re-check Manage Pages, ad account and Leads Access, then run the Lead Ads testing tool and read Track Status.
- Error 103. Lofty’s article quotes it as “CRM access has been revoked from Lead Access Manager.” Reset Leads Access using Restore Default Access, or add “Lofty Leadgen” to the People list and “Lofty Ads Platform” to Connected CRMs.
- Permissions missing. Remove the Lofty Ads Platform in Facebook, reconnect, and test again.
- Page greyed out or not selectable. You need permission to manage the Page. If it stays greyed after a request, the Page admin still has to approve.
- Wrong lead type. Check the exact spelling in utm_medium.
- Zapier: no form fields. The Facebook form must be live during setup.
- Anything else. Contact Lofty Support, as the article advises.
Zapier reports a similar permission failure as “(#200) user does not have sufficient administrative permission,” so the cause is often the same: nobody with the right Facebook role granted access.
Where we have and have not done this
We have not published a Lofty-specific Facebook ads case study, and we will not invent one. What we can say is that for a BoldTrail client, the Faruqi Team, we built an automation so Facebook seller leads import directly into the CRM and start the email campaign, workflow and follow-ups. The principle is identical, and we describe it in Facebook seller leads into BoldTrail.
When a Lofty account needs the same, the work is the steps above plus the follow-up routine behind them, which is what our Facebook ads management and Lofty virtual assistant services cover. A free consult will scope it.