Docs
OverviewPlatformPlatform APIA2P Messaging API
AI & MCP
Open dashboard
OverviewPlatformPlatform APIA2P Messaging API
AI & MCP
Getting started
  • Overview
  • Start guide
  • Project status
  • Concepts
AI
  • Iris
  • AI writing
  • Connect your AI (MCP)
Channels
    • Countries & coverage
    • Senders & registration
    • Essentials
    • Countries & availability
    • What is RCS
    • Senders & verification
    • Agent profile
    • Best practices
    • Acceptable use
    • SMS fallback
  • WhatsAppSoon
  • Compliance
  • Countries
    • Austria
    • Brazil
    • Canada
    • Colombia
    • France
    • Germany
    • India
    • Indonesia
    • Mexico
    • Netherlands
    • Peru
    • Singapore
    • Spain
      • Authorise the alias
      • Register directly
      • Without a certificate
      • Rejected alias
    • Ukraine
    • United Kingdom
    • United States
    • Other countries
Marketing
  • Campaigns
    • Creating a campaign
    • Targeting
    • Test sends
    • Delivery
    • Compliance
    • Managing campaigns
    • Campaign analytics
  • Flows
    • Building a flow
    • Templates
    • Triggers & entry
    • Sending messages
    • Waits
    • Branches
    • Contact updates
    • Goals & exits
    • Versions & publishing
    • Managing flows
    • Monitoring
    • Analytics
    • Limits
  • Sequences (legacy)
    • Managing sequences
    • Sequence analytics
Data
  • Audience
    • Contacts
    • Audience table
    • Segments
    • Attributes & events
  • Integrations & data sources
    • Managing sources
    • CSV import
    • API & webhooks
    • Event best practices
    • Integrations
      • Shopify
      • Klaviyo
      • WooCommerce
      • PrestaShop
      • Magento
      • HighLevel
      • Hotmart
      • ActiveCampaign
      • Zoom
      • Facebook Leads
      • Google Sheets
      • Google Contacts
      • MailChimp
      • MailerLite
      • Intercom
      • Make
      • Zapier
      • Activepieces
      • n8n
      • Pabbly Connect
      • OptiMonk
      • Paperform
      • StockAgile
      • Typeform
  • Consent
    • How consent works
    • Subscription attributes
    • Shared consent
    • Opt-outs
    • Manage via API
Analytics
  • Audience
  • Messages
  • Sales
  • Reports
Settings
  • Project settings
    • Brand profile
    • Senders
    • Short links
    • Unsubscribe links
    • Test numbers
    • Attribution
    • Project memory
  • Developers & Apps
    • API tokens
    • Third-party apps
    • Data access
    • Connected apps
  • Organization
    • General
    • Legal profiles
    • Team
    • Localization
  • Billing
    • Plans
    • Cost calculator
    • Balance
    • Invoices
    • Pricing
    • Account
    • Theme
    • Security
    • Notifications
    • Language & currency
DashboardSupportinstasent.com

Data · Integrations & data sources

Facebook Leads

Connect Facebook Leads as a data source: authorize with your Meta account, choose the page and lead form to import, how its fields map to Instasent attributes, and how lead consent is handled.

On this page▾
  • How to connect
  • What it syncs
  • Field mapping
  • Consent mapping

Facebook Leads is the native connector for the leads your lead-ad forms collect on Facebook. Once authorized, it brings those leads into Instasent as contacts, so anyone who submits one of your forms lands in your audience without any manual export.

How to connect

Facebook Leads is a native OAuth connector: you authorize Instasent with your Meta account and, once connected, pick which page and lead form to import from. There's no key to create or copy anywhere.

  1. 1

    Add the data source

    In Data sources, select Add data source and choose Facebook Leads from the Integrations section.

  2. 2

    Continue with Facebook

    Select Continue with Facebook to open Meta's authorization window. You can choose which businesses and pages Instasent may access. Instasent will only read your forms and retrieve your leads — read-only access.

  3. 3

    Choose the page and form

    Back in Instasent, select the Facebook page and then the Facebook Leads form to import from. Each data source imports from one form.

  4. 4

    Initial import

    The connector imports the existing leads from that form, then keeps checking for new ones on a periodic sync.

The Facebook Leads connector page: what it brings into Instasent and the contact fields it maps, with Connect Facebook Leads to start.

What it syncs

  • Contacts — the leads submitted through the selected lead form, with the fields the form captured (name, email, phone).

The sync is one-way, from Facebook into Instasent, and runs periodically to pick up new leads. Instasent only reads your forms and their leads; it never edits anything on Facebook. Contacts unify with the rest of your audience by email and phone, the same as any source — see unification.

Field mapping

The lead form's fields map to the matching Instasent attributes — email to _email, phone to _phone_mobile, name fields to their attributes. As with any source you confirm the mapping on setup; see field mapping.

Consent mapping

Map any marketing consent the lead form captured to Instasent's marketing-preference attribute (_accepts_marketing_*) following the consent golden rule:

Lead statusInstasent valueMeaning
Opted in on the formtrueAccepted marketing
No consent capturednullNo preference — never opted in or out
Opted outfalseActively declined marketing

Only an active opt-out becomes false. A lead with no recorded consent maps to no preference (null), never to false. For what these values mean for who receives a campaign, see Consent.

Last updated October 8, 2026

PreviousZoomNextGoogle Sheets
  • How to connect
  • What it syncs
  • Field mapping
  • Consent mapping

© 2026 Instasent

Privacy PolicyTerms & ConditionsCookie PolicyLegal Notice
All systems operational