Most teams running Odoo can see orders and quotations, but the journey that leads to them is a black box. Odoo core gives you a website.visitor record with a last-connection timestamp and a rough page-visited log, plus link-tracker UTMs — but it stops well short of session-level analytics. It doesn't reconstruct ordered click paths, it doesn't attribute product-view interest back to product.template/product.product, it doesn't surface scroll depth or add-to-cart-then-abandon signals, and it gives sales and marketing no first-party dataset they can slice inside Odoo. Bolting on an external analytics pixel moves that data off-platform, breaks under consent tooling, and never joins back to your CRM leads or eCommerce orders. That gap is exactly what we build for.

ECOSIRE builds a first-party Website Visitor Tracking module that lives inside your own database. We add new models — typically x_visitor_session and x_visitor_event — related back to Odoo's own website.visitor, res.partner, and the eCommerce sale/cart models, so every page view, product view, search, cart change, and checkout step is recorded as a structured event with referrer, UTM, device, and dwell time. Capture runs through a lightweight first-party controller (http.Controller) that writes events server-side under a dedicated technical user via sudo(), so ad-blockers and privacy browsers don't silently drop your data the way a third-party tag would. A QWeb template injects a small, consent-aware beacon into your website layout; compute fields with @api.depends roll raw events up into session duration, page count, and an interest score you can act on.

On the reporting side we ship Odoo-native views: list, kanban and a graph/pivot analytics view over the event models, saved filters for "viewed but never bought" and "abandoned at payment," plus a QWeb PDF summary for weekly review. Automated actions (base.automation) can flag a hot session, create or update a CRM crm.lead, or notify a salesperson via mail.activity when a known partner returns and hits a high-intent page. Everything is permissioned properly through ir.model.access.csv and record rules so multi-company and salesperson-scoped visibility behave correctly, and the event stream is readable over the standard XML-RPC/JSON-RPC API if you want to pipe it into an external warehouse. The module is built and tested for Odoo 17.0, 18.0 and 19.0, on both Community and Enterprise (Enterprise adds tighter links to the native dashboards and studio-style customization if you have it).

Because this is build-to-order, nothing ships until we agree on scope. After a short scoping call we confirm exactly which events, which eCommerce touchpoints, and which CRM/automation hooks you need, then build against your Odoo version and edition, test on a staging copy of your database, and install to production with a rollback plan. Typical delivery is 2–4 weeks from confirmed scope. Pricing starts from $249 (indicative, single-company base scope); multi-company rollouts, deeper eCommerce/checkout instrumentation, consent-manager integration, and historical data migration increase the quoted scope. You get a fixed quote after the scoping call — never a surprise.