Google Ads & Lead Form Extensions Connector

This is a build-to-order module, not an instant download. After purchase, ECOSIRE runs a short scoping call to confirm your Google Ads account structure, Lead Form assets, pipeline stages and assignment rules, then builds, installs and validates the integration on your Odoo instance. Typical lead time is 2–4 weeks depending on the number of accounts, custom fields and assignment logic. You receive a working, tested integration wired to your production environment — not a self-service ZIP.

Every build ships with a defined post-go-live support window covering bug fixes, configuration adjustments and help keeping the module compatible as you update Odoo. If Google changes its Lead Form webhook payload or Ads API, we assist with the required updates. Because we hand over the full source code, your own team (or ECOSIRE on a support retainer) can maintain and extend it. Extended support and enhancement retainers are available.

The module is built for Odoo 17, 18 and 19, and runs on both Community and Enterprise. The core CRM, mail and cron functionality it depends on exists in Community, so you do not need Enterprise. We build against the specific major version(s) you order and account for API differences between them.

Yes — offline conversion uploads and cost sync use the official Google Ads API, which requires a developer token and OAuth2 credentials on your Google Ads account. Real-time lead capture uses Google's Lead Form webhook, which needs a webhook URL and key configured on your lead-form assets. ECOSIRE guides you through obtaining and configuring all of these during setup; credentials are stored encrypted server-side in Odoo, never exposed in the UI.

When a prospect submits a Google Lead Form, the ad platform posts the submission (including the GCLID and campaign/UTM data) to a secured Odoo webhook, which creates a crm.lead with all attribution fields populated. As that lead advances to a stage you designate as a conversion, a scheduled action uploads the stored GCLID and a conversion value back to Google Ads. Meanwhile daily cost sync pulls spend per campaign into Odoo, so pivot views and the QWeb report show spend, cost-per-lead and won revenue side by side — a true closed loop.

Yes. The module supports connecting multiple Google Ads accounts and mapping their campaigns to different Odoo sales teams. Assignment rules — by campaign, territory, product interest or round-robin — are implemented with automated/server actions and configured to match your structure during the build, and record rules ensure each team sees only its own leads.

No. The webhook layer verifies each payload against your Google-supplied key, and de-duplication logic links or merges repeat submissions from the same GCLID or email rather than creating duplicate opportunities. A failed-delivery and retry log captures anything that doesn't process cleanly so nothing is lost and nothing junk-floods your CRM.