Lead Distro AILead Distro AI
DocsIntegrationsMeta Ads Integration

Meta Ads Integration

Connect Lead Distro AI with Meta Ads: sync ad spend to campaigns, track conversions via the Conversions API, connect Facebook and Instagram lead forms, and attribute revenue to traffic sources.

Last updated:

Overview

Connect your Meta (Facebook/Instagram) ad accounts to automatically sync ad spend, track conversions via the Conversions API (CAPI), and ingest leads directly from Facebook Lead Forms.

Ad Spend Tracking

  • Go to Settings → Integrations → Meta Ads and click Connect.
  • Authenticate with Facebook and select your ad accounts.
  • Map your Meta campaigns/ad sets to Lead Distro AI campaigns and suppliers.
  • Spend syncs automatically every day — costs are attributed to the correct campaigns.

Conversions API (CAPI)

Send server-side conversion events back to Meta when lead outcomes change. This improves ad optimization by telling Meta which leads converted.

  • Go to Settings → Integrations, find the Meta Conversions API card, and click Add Integration. Enter your Meta Pixel ID and Conversions API access token.
  • Link the pixel to the sources that should use it. In the Manage window, use the Sources column. A pixel that is not linked to a source never sends anything.
  • Open the Event Mapping tab and click Add Event. Pick which moment sends an event to Meta: Lead Ingested, Lead Accepted, Lead Converted, or Lead Rejected. Then choose the Meta event it sends and click Save Mappings. Nothing is sent for a moment you have not mapped.
  • Events are sent automatically and include hashed PII for matching.

Lead Converted and Lead Rejected are sent when a lead's outcome changes to Converted or Not Qualified. That happens when you set the Outcome on the lead's row in the Leads list, when your buyer sets it in the Partner Portal, or when their system reports it through the postback webhook. Setting the outcome back to Pending sends nothing. Changing outcomes with the bulk Edit button does not send an event, so set them one lead at a time.

Facebook Lead Forms

Connect Facebook Pages to automatically ingest leads from Lead Form ads. Leads flow directly into your campaigns without any external automation tool.

Meta integration requires a Meta Business account with active ad accounts. The OAuth flow requests ads_read and leads_retrieval permissions.

Frequently Asked Questions

What does the Meta Ads integration do?
Three things. (1) Ad Spend Sync pulls actual Meta ad spend daily and attributes cost to the right Lead Distro AI campaigns and suppliers (powers the Variable cost mode). (2) Conversions API (CAPI) sends server-side conversion events back to Meta at the moments you choose (lead ingested, accepted, converted, or rejected), improving Meta's ad optimization. (3) Lead Form ingestion pulls leads directly from Facebook Lead Form ads into Lead Distro AI campaigns without needing Zapier or a custom webhook.
How does the Conversions API (CAPI) help my ad performance?
Meta's ad-optimization algorithm learns from conversion signals. iOS 14+ broke client-side pixel tracking for most users, so server-side CAPI is now the dominant signal. By sending real lead outcomes (accepted, converted, rejected) back to Meta with hashed PII for matching, you give Meta the lead-quality data it needs to find more converting users.
What Meta permissions does Lead Distro AI request?
Two OAuth scopes: ads_read (read ad account spend and campaign data) and leads_retrieval (pull leads from connected Lead Form ads). No write permissions are requested — Lead Distro AI cannot create, edit, or pause your Meta campaigns. Authentication happens via standard Meta Business OAuth; revoke at any time from Settings → Integrations → Meta or directly from Meta Business Settings.
Can I have multiple Meta pixels — one per supplier or client?
Yes. Per-supplier Meta pixel wiring lets you isolate CAPI events per traffic source. Supplier A's leads fire conversions on Pixel A, Supplier B's leads fire on Pixel B. This is critical when running attribution for multiple ad accounts or agency clients on the same Lead Distro AI infrastructure — each client sees their own clean attribution in their own Ads Manager.
How fast does Meta spend sync after a lead is ingested?
Spend sync runs every 6 hours on a cron schedule. So leads ingested at 10am show their cost attribution after the next 12pm sync. Real-time cost attribution isn't possible — Meta's reporting API has its own delay before today's spend appears. For real-time profit dashboards, the platform uses the most recently synced spend snapshot and trues up as fresh data arrives.
What happens if my Facebook Lead Form ad pulls in leads I don't want?
Use campaign Inbound Filters to reject unwanted leads before distribution. Filters run on every ingested lead — Lead Form, API, or CSV import — and check field values against rules you configure. Common filters: state allowlists, required custom field values, phone/email format validation. Rejected leads appear in the dashboard with status REJECTED and the specific filter that caught them, so you can iterate on filter rules without losing visibility.
Can I see and retry failed CAPI events?
Yes. There are two places to look. In the Leads list, click Columns and tick CAPI Event. Each lead then shows Sent or Not sent, and hovering it tells you why. A lead that was not sent has a retry button right there. For the full history, open Settings → Integrations → Meta Conversions API → Manage and go to the Event Logs tab, which lists recent events with the Meta response for each one. Common reasons an event is not sent: no event mapping for that moment, the pixel is not linked to the lead's source, or an expired access token. Retries are manual, so fix the cause and then click retry.

Related Articles

Integration Patterns
Lead Distro AI integrations: Zapier, Make, Google Sheets, Slack, HubSpot, Salesforce, Clio, and custom webhooks. Connect your lead distribution pipeline to every tool in your agency stack.
HubSpot Integration
Send Lead Distro AI leads directly into HubSpot as Contacts or Deals using a HubSpot Workflow webhook. Step-by-step setup, field mapping, troubleshooting, and FAQs.
Salesforce Integration
Push Lead Distro AI leads into Salesforce as Lead records using Web-to-Lead or Flow with an authenticated webhook. Setup paths, daily volume limits, and troubleshooting for enterprise lead distribution.
Clio Integration
Connect Lead Distro AI to Clio for personal injury and law firm lead intake. Clio Grow inbound webhook setup, Clio Manage API, MVA-specific custom field mapping, and FAQs.

If you have any questions, send us an email at support@leaddistro.ai

Automation BasicsAppointments Overview