CONNECTIONS / Odoo
Odoo + Datahash: invoiced revenue becomes ad signal.
An Opportunity won in Odoo CRM usually becomes a Sales Order and an Invoice in the same suite, so the revenue behind a closed deal is not an estimate. Signals reads that value and the stage that produced it, then routes conversion events and audiences to every platform you buy on.
- ● odoo :: signals live
- > read crm.lead stage=won rows=966
- > read account.move state=posted
- hash sha256(email,phone) scope=crm.lead.read
- route meta · google · tiktok · snap
- ✓ 4 destinations synced · match 80%
The signal Odoo yields, and receives.
Every kind of signal that moves between Odoo and the platforms, through one hashed, deduplicated route.
- Offline conversions
- A Kanban stage move on an Opportunity posts as a conversion event as soon as the record updates, no export job in between.
- Lead conversions
- When a won Opportunity generates an Invoice, that posted value leaves hashed and reconciles against the campaign that sourced the deal.
- Custom audiences
- Partner and Contact records become hashed, scheduled audiences without a CSV leaving the instance.
- Lead generation inbound
- A custom field added to the Lead or Opportunity model keeps flowing once mapped, so a schema change inside Odoo does not break the connection.
Pick your platform. Every use case for it, in one place.
Every way Odoo data moves, grouped by platform and ranked by how many use cases Odoo supports.
Google 5 
Meta 4 
Snap 4 
TikTok 4 
LinkedIn 3 
OpenAI 1 - Offline conversions Google Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Offline conversions Google Store Sales Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions Google Enhanced Conversions for Leads Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences Google Customer Match Contact segments refreshed as hashed, scheduled audiences.
- Lead generation Google Forms Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions Meta Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions Meta Conversions API for CRM Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences Meta Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Lead generation Meta Lead Ads Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions Snapchat Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions Snapchat Leads Conversions API Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences Snapchat Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Lead generation Snapchat Lead Generation Ads Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions TikTok Offline Events API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions TikTok CRM Events API Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Custom audiences TikTok Custom Audience Contact segments refreshed as hashed, scheduled audiences.
- Lead generation TikTok Lead Generation Campaign lead submissions created as records in real time, deduped before creation.
- Offline conversions LinkedIn Offline Conversions API Closed-won revenue and purchase records, matched back to campaigns as offline conversions.
- Lead conversions LinkedIn Leads Conversions API Lead and deal stage changes delivered as conversion events for lead-quality optimization.
- Lead generation LinkedIn Lead Generation Forms Campaign lead submissions created as records in real time, deduped before creation.
From authorization to delivered signal.
-
Connect
Connect Odoo through a scoped API user, whether Odoo Online, Odoo.sh, or a self-hosted Community instance, revocable at any time.
-
Map stages
Match Kanban stage names, custom ones included, to platform events in the visual mapper.
-
Hash and consent
Hashing and consent checks apply before a record leaves Odoo.
-
Deliver
Mapped destinations receive events on delivery, with per-stage match reporting.
Odoo questions, answered.
We self-host Odoo Community. Can Signals still connect?
Yes. Odoo Community, Odoo Online, and Odoo.sh all expose the same API surface, so the connection reads crm.lead and related models the same way regardless of where the instance runs. A self-hosted deployment only needs a reachable endpoint and a scoped API user to get started.
Does closed-won revenue come from the CRM stage or the actual invoice?
Whichever you map it to. Most teams tie the conversion to the posted Invoice generated from a won Opportunity, since that reflects revenue Odoo has actually recorded rather than a stage label, but a stage-based trigger works fine if invoicing lags behind the sale.
Do Odoo's custom modules or fields break the mapping?
No. The visual mapper reads the actual fields present on crm.lead in your instance, custom ones included, so a field added by a module or a customization still appears as an option. Renaming or adding a field later means updating the mapping, not rebuilding the connection.
NEXT STEP
See your Odoo data working in every ad platform.
Ready to enable a use case, or still mapping what Odoo data could do? Our team helps you find the right place to start.
