Performance-marketing teams pour budget into Meta Lead Ads, then lose the race that actually matters: speed-to-lead. Without an integration, someone exports CSVs from Meta Ads Manager, or Zapier drops rows into a spreadsheet, and by the time a lead reaches ERPNext CRM it is hours old and stripped of the campaign context you paid for. ERPNext core has no native Facebook/Instagram Lead Ads connector, no place to store the Meta leadgen_id or ad/campaign IDs, and no webhook endpoint wired to the Graph API — so attribution and follow-up both suffer.

ECOSIRE builds a proper Frappe app (its own module, versioned in a git repo) that closes this gap. We stand up a whitelisted webhook endpoint on your ERPNext site that subscribes to Meta's leadgen webhook topic, verifies the X-Hub-Signature-256 payload, and on each event calls the Graph API to retrieve the full field-data for that leadgen_id. A configurable Meta Lead Ads Settings DocType holds your Page tokens, App secret, and a child-table field map that translates each Meta form question into a target Lead (or custom CRM) DocType field — so full_name, email, phone_number, and any custom questions land in the right place without code changes when you add a new form.

Technically, the capture runs through hooks.py doc events and server scripts: an inbound lead is de-duplicated, tagged with source and campaign attribution (ad ID, adset, campaign name, form ID), and pushed through your existing ERPNext assignment logic. Auto-assignment rules — round-robin, territory, or lead-owner — are implemented as server-side logic honoring Frappe permissions and role profiles, so reps only see what they should. A scheduler event provides a reconciliation sweep that re-pulls any leads Meta retried or that arrived during downtime, and every capture is logged for audit. Optional client scripts surface the Meta context (campaign, ad creative, form) directly on the Lead form for reps.

Because this is build-to-order, nothing is a black box. After a short scoping call we confirm your exact forms, field maps, assignment rules, and multi-page setup, then build against your ERPNext v15 or v16 site. Typical delivery is one working week from confirmed scope. We hand over installable source, run UAT on a staging bench with a rollback plan, install to production, train your team, and stay on for a post-go-live support window. You own the git repository at the end.