Module settings
Open the settings via Modules → Module Manager → WEB Vision – Google Tag Manager a GA4 → Configure.
If you run several shops (multistore), the settings are saved for the shop selected in the admin header. Settings saved for “all shops” apply to shops that have no settings of their own.
Setup status
Section titled “Setup status”The panel shows what is still missing (the container ID, enabled events).
Basic settings
Section titled “Basic settings”| Field | Meaning |
|---|---|
| Google Tag Manager container ID | An ID in the form GTM-XXXXXXX. |
| Insert the container into the page | Turn on if the container is not inserted by the theme or another module. If the Cookie banner module inserts it, this module does not insert it a second time. |
| Product identifier | What identifies a product: ID, ID with combination, reference or EAN. It must match the product feed (Google Merchant, Meta). |
Events
Section titled “Events”In the Events section you turn individual events on and off. The list and description is in the chapter Events.
Template for Google Tag Manager
Section titled “Template for Google Tag Manager”In the Template for Google Tag Manager panel you download a ready-made template (optionally with your Measurement ID) and the import procedure. The procedure is also in the chapter Installation.
Advanced
Section titled “Advanced”| Field | Meaning |
|---|---|
| Data layer name | dataLayer by default. Change it only if your container uses another name. |
| Enhanced conversions | On purchase, login and sign-up, sends a hashed e-mail (SHA-256) in user_data. Off by default and sent only with Marketing consent. |
How it works
Section titled “How it works”- Page events (list, product, cart, checkout, purchase, search) are built by the server and the page puts them into the data layer. Products, prices and quantities are never determined by the browser.
- Selecting a product from a list, adding and removing from the cart, selecting shipping and payment are captured by the browser. It takes the product data from the page.
- Login and sign-up are sent on the next page after they finish. Guests are not reported.
- Robots, search engines and background calls are not measured.
- The module has no queue or cron and makes no background calls.
Thank you for your answer.
We are sorry. Tell us what is missing or unclear:Write to support