| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
CRM (crm)
• Discuss (mail) • Calendar (calendar) • Contacts (contacts) |
| Lines of code | 4196 |
| Technical Name |
meta_lead_ads |
| License | OPL-1 |
| Versions | 18.0 19.0 |
Meta Lead Ads, straight into Odoo CRM
Facebook and Instagram leads arrive in Odoo CRM in real time, with the campaign, ad set, ad and form that produced them. No CSV exports, no middleware.
This module connects Meta Lead Ads to your CRM through a verified webhook for real-time delivery and a scheduled backfill that re-checks every form, so a missed webhook never costs you a lead. Both paths run through a single ingestion service, so each lead is created once â never duplicated, even when Meta re-sends an event.
Highlights
Real-time, with a safety net. A signature-verified webhook captures leads the moment they're submitted; a backfill cron re-sweeps each form on a schedule. Exactly-once creation is enforced by a database constraint, not a best-effort check.
Attribution you can act on. Campaign, ad set, ad, form and page â names and IDs â are recorded on every lead and mapped to Odoo UTM, so you can see which ad produced which opportunity.
Careful with credentials. The App Secret and access tokens are restricted to administrators. The webhook checks Meta's signature over the raw request body before parsing anything, and nothing secret is ever written to the logs.
How it works
1.Connect your Meta app
Under Settings → Meta Lead Ads, the Connect wizard takes your App ID, App Secret and access token, validates them, and discovers your Pages and lead forms. Accounts, field mappings, sync logs and lead naming all live in one place.
2.Check the connection
Each account shows its token validity, granted scopes, whether leads_retrieval is in place, and whether Odoo's scheduler is running your jobs â with Test Connection and Check Scheduler buttons so you can confirm it yourself.
3.Read every lead in context
Leads come in as ordinary crm.lead records you can qualify and convert. A Meta Attribution section records the platform, campaign, ad set, ad, form and page, plus the originating Meta Lead ID.
4.Map the questions you care about
Custom form questions are stored on every lead. Map a question to an existing CRM field, or promote an answer into a new field from the lead itself â the answers you collect are never discarded.
5.See what's converting
A read-only dashboard shows leads over time, lead-to-opportunity and win rates, a breakdown by campaign, and a ranking of your best performers, with health indicators for the webhook, scheduler and token.
6.Keep an audit trail
Every attempt â webhook, cron or manual â is logged with its status, trigger and the dedup key that matched. If something fails, select the row and retry; the same ingestion service re-fetches it from Meta.
Details
Captured on every lead
- Contact name, email and phone (with normalized-phone dedup)
- Platform â Facebook or Instagram
- Campaign, ad set and ad â names and IDs
- Lead form and Page â names, IDs and linked records
- Meta Lead ID and the originating account
- All custom form answers, stored in full
How it stays correct
- Exactly-once creation via a database UNIQUE constraint
- Two-layer dedup: Meta Lead ID, then email and phone
- HMAC-SHA256 verification on the raw webhook body
- Tokens and App Secret restricted to administrators
- Get-or-create UTM mapping â no duplicate UTM records
- Token-health alerts and a scheduler self-check
Requirements
- Odoo 18.0 (Community or Enterprise)
- Depends only on the standard
crm,utmandmailmodules - No extra Python packages â uses the bundled
requestslibrary - A Meta Business app with a System User (or Page) token
- A publicly reachable HTTPS URL for the webhook
Before going live, Meta requires App Review with Advanced Access for leads_retrieval (plus pages_show_list, pages_manage_metadata and pages_read_engagement) and Business Verification. An app in Development Mode returns test leads only, so it's worth starting the review early.
CoreSys Builders. © 2026, all rights reserved. Licensed under the Odoo Proprietary License v1.0 (OPL-1); redistribution and resale are not permitted. Questions and feature requests are welcome.
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module