Terrabit Google Tag Manager
by Terrabit https://www.terrabit.ro , Dorin Hongu https://www.terrabit.ro$ 609.37
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
eCommerce (website_sale)
• Discuss (mail) • Invoicing (account) • Inventory (stock) • Website (website) |
| Community Apps Dependencies | Show |
| Lines of code | 457 |
| Technical Name |
terrabit_google_tag |
| License | OPL-1 |
| Website | https://www.terrabit.ro |
| Versions | 17.0 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
eCommerce (website_sale)
• Discuss (mail) • Invoicing (account) • Inventory (stock) • Website (website) |
| Community Apps Dependencies | Show |
| Lines of code | 457 |
| Technical Name |
terrabit_google_tag |
| License | OPL-1 |
| Website | https://www.terrabit.ro |
| Versions | 17.0 18.0 19.0 |
Terrabit Google Tag Manager
Terrabit Google Tag Manager
Module for integrating Google Tag Manager (GTM) with the Odoo 19 e-commerce website.
How It Works
In Odoo 19 the legacy websiteSaleTracking public widget is gone, so tracking is now event-based. This module registers a frontend ``Interaction`` (mirroring terrabit_facebook_pixel) that listens to:
- the core website_sale DOM events view_item_event and add_to_cart_event;
- the normalized events emitted by ``terrabit_website_sale_tracking_base``: terrabit_tracking:begin_checkout, :add_payment_info, :search, :contact, :form_submit.
and forwards each of them to ``window.dataLayer``, making them available to Google Tag Manager. The purchase event is pushed on page load by reading the order tracking info present in the confirmation page DOM.
Events keep the same flat shape as in version 18 (window.dataLayer.push({ event, ...payload })) so existing GTM container triggers keep working after the upgrade.
Configuration
Go to Website → Configuration → Settings and enable Google Tag Manager.
| Field | Description |
|---|---|
| Tracking ID | GTM container ID (e.g. GTM-ABCDEFG) |
| Conversion Code | Google Ads conversion label (e.g. AW-123456789/ABCDEFG) — optional |
The GTM snippet is injected into <head> on every page when a Tracking ID is configured. The tracking_item_id_type (product variant / template / SKU) and “exclude delivery” options are shared with the other pixels through terrabit_website_sale_tracking_base.
Events Forwarded to dataLayer
All events are pushed in the format:
window.dataLayer.push({ event: "<event_name>", ...payload });
| Event | Trigger | Key fields |
|---|---|---|
| view_item | product detail page loaded (view_item_event) | currency, value, items[] |
| add_to_cart | product added to the cart (add_to_cart_event) | currency, value, items[] |
| begin_checkout | “Process Checkout” clicked | — |
| add_payment_info | payment submitted | payment_type |
| search | shop search submitted | search_term |
| contact | phone link clicked | — |
| generate_lead | website form submitted | — |
| purchase | order confirmation page loaded | transaction_id, currency, value, shipping, tax, items[] |
Each items[] entry carries item_id, item_name, item_brand, item_category, price and quantity. The item_id honors the configured tracking_item_id_type.
Note: If a Conversion Code is configured, a conversion event is also pushed alongside purchase with send_to set to the conversion label.
Templates
| Template | Description |
|---|---|
| google_tag_manager | Injects the GTM <script> into <head> and a <noscript> fallback before #wrapwrap |
| confirmation | Injects a div with data-google_conversion_code on the confirmation page (used for the conversion event) |
| product | Injects a hidden <span itemprop="category"> on the product page so the category is available to tracking |
Documentation
- https://developers.google.com/tag-manager/quickstart
- https://developers.google.com/tag-platform/gtagjs/reference/events
- https://developers.google.com/analytics/devguides/collection/ga4/reference/events
Table of contents
Bug Tracker
Bugs are tracked on Terrabit Issues. In case of trouble, please check there if your issue has already been reported.
Do not contact contributors directly about support or help with technical issues.
Credits
Authors
- Terrabit
- Dorin Hongu
Maintainers
Current maintainer:
This module is part of the terrabit-solutions/bitshop project on GitHub.
You are welcome to contribute.
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