Google Tag Manager on PrestaShop works when two things are true: the container loads on every page, including the order confirmation page, and a data layer sends the ecommerce values GTM needs. The module you installed is only a helper. If its events do not fire, or if left-over GA4 code tracks the same actions, your reports will be wrong no matter how the tags look in GTM.
This guide is a checklist, not a module review. You will follow one verification path: container present, data layer correct, trigger fires, tag sends, then the GA4 report matches. At each stop we say what to look at and what the usual cause of a missing value is, so a non-developer can find the broken step before paying an integrator.
The path in 6 steps
The steps of this page, in order.
-
01 Confirm the container Check that the GTM snippet is on every page, including order confirmation.
-
02 Read the data layer Verify product, cart, and purchase values are present and correct.
-
03 Find duplicates Look for two tags tracking the same action, one from a module and one from GTM.
-
04 Test events Fire each ecommerce event and confirm it in GTM Preview and GA4 DebugView.
-
05 Check consent Confirm your cookie module and Consent Mode agree on what may fire.
-
06 Fix in order Work container, data layer, trigger, tag, report, and stop at the first failure.
01 / 12
Is Google Tag Manager actually loading on every page?
Start here: if the container is missing or duplicated, nothing further will be reliable.
The GTM container is the snippet you paste into PrestaShop; it loads all your tags at once. It must sit in the page head after the opening tag on every page, not just the home page, per Google Tag Manager developer documentation. In the module route, enable the GTM module and paste your container ID; in the manual route, add the snippet to your theme header file.
The order confirmation page is the classic blind spot: many PrestaShop themes render it with a different template, so verify it separately. Open the page source on a product page, a category page, and the order confirmation page. Search for your container ID to confirm it appears once, not twice.
-
Step 1: Check the home page
Open your store's home page, right-click, and view page source. Search for 'GTM-' or your container ID. It should appear once, in the head section, right after the opening head tag.
-
Step 2: Check a product page
Repeat the same check on a product page. If the container is missing or duplicated, the issue is likely in the theme header file or a conflicting module.
-
Step 3: Check a category page
Verify a category page as well, since some themes use different templates that may omit the GTM snippet. The container ID should appear exactly once.
-
Step 4: Check the order confirmation page
Place a test order (use a payment method like 'check' or a sandbox mode) and view the source of the order confirmation page. This page often uses a separate template, so confirm the container ID is present once.
-
Step 5: Confirm no duplicates
If the container ID appears more than once on any page, disable one source: either the GTM module or the manual snippet in the theme. Duplicates cause double counting and unreliable data.
02 / 12
What needs to be ready before I start testing?
A short list you should settle first, so the test results mean something.
First, decide whether Google Tag Manager is injected by a module or by code added to your theme. Using both at once is the most common cause of duplicate tags and unpredictable results, so pick one path and disable the other.
Then confirm you can edit that path: module settings or the theme files under /themes/your-theme/, including header.tpl and footer.tpl. Know who last changed them before you touch anything.
Single injection path
One method only: module or manual theme code. Both together duplicate the container and break event matching.
Edit access confirmed
Check you can open module settings or theme files, and that you know the last editor, so rollback is possible if testing breaks the page.
GTM container ID recorded
Note the exact ID (GTM-XXXXXX) so you can search for it in the theme and module settings to spot a second copy.
Google Tag Assistant ready
Install the Tag Assistant Companion extension in Chrome and open it on your test store before you click anything.
GA4 DebugView open
In GA4, go to Admin > DebugView on the same browser session. Events will only appear there if debug_mode is active or the extension is connected.
03 / 12
What should PrestaShop's data layer contain?
The data layer is what turns GTM from a page counter into a sales tracker.
A data layer is a JavaScript object that passes values such as product name, price, and order total to GTM. For product and cart events, it needs at least item name, item ID, price, and quantity. For a purchase, it adds order ID, total, tax, and shipping (source: GA4 ecommerce developer documentation).
Most PrestaShop GTM modules supply standard events like page view, category view, product detail view, and add to cart, though each vendor's exact list should be confirmed on its official page. If the data layer is empty, inspect it in the browser console on a product page before blaming GTM.
Product view
Fires when a shopper opens a product page. This tells you which items attract attention and lets you build audiences around them.
- Item name
- String, the product title
- Item ID
- String or number, the unique product identifier
- Price
- Number, the unit price shown to the user
- Quantity
- Number, usually 1 on a detail view
Key pointCheck that item ID matches the product ID in PrestaShop, not the combination ID.
Cart
Fires on add to cart and subsequent cart updates. It captures what people intend to buy before they reach checkout.
- Item name
- String, the product title
- Item ID
- String or number, the unique product identifier
- Price
- Number, the unit price at the moment of adding
- Quantity
- Number, how many units were added
Key pointAdd a test product, then open the console and confirm the values update without a page reload.
Purchase
Fires on the order confirmation page. This is the event your ad platforms and GA4 use to report revenue and conversions.
- Order ID
- String or number, unique per transaction
- Total
- Number, the order value including tax and shipping
- Tax
- Number, the tax amount included in the total
- Shipping
- Number, the shipping cost charged
Key pointPlace a test order and verify order ID and total match the confirmation screen.
Going further
Read the data layer
Method
How to read a PrestaShop data layer without being a developer
You do not need to write code to see whether PrestaShop is feeding values into the data layer.
Open your store in a browser such as Chrome or Firefox. Right-click anywhere on a product page and choose Inspect, then switch to the Console tab. Type window.dataLayer and press Enter. You will see an array. If it is empty or missing, the container code is not pushing ecommerce data. If it contains objects, expand them and look for ecommerce-related keys such as item_name, item_id, price, or quantity.
The console shows raw values, not a formatted report. If the array contains a page view event but no product object, the module is loading GTM without mapping PrestaShop product variables. That tells you where to look before changing any tag configuration.
- Console shows window.dataLayerType window.dataLayer in the browser console on a product page. The result should be an array; a "not defined" answer means the container snippet never loaded.
- Array contains ecommerce objectsExpand the most recent entries and look for item_name, item_id, price, and quantity.
- Values match the pageThe item_name and price should correspond to the product displayed.
- Purchase event appears on confirmation pageAfter a test order, check for a purchase event with order_id, value, tax, and shipping.
04 / 12
Module or manual code: which one is breaking the other?
Two integration routes exist, and mixing them is the most common cause of broken tracking.
Mix the two routes and the symptoms are easy to recognize: the same purchase fires twice in GA4, value switches between two different sets of numbers, or GTM Preview lists tags you never built. Those tags usually come from a module that injects its own container or its own events alongside your theme code.
Once you commit to one route, strip the other. Delete leftover GTM snippets, hooks, and module-injected tags from your theme, then confirm in Preview that each event fires exactly once. A user report flags this as a frequent conflict; confirm details on the vendor's official pages.
Module route
- Handles container placement and often standard ecommerce events for you
- Fewer theme edits and faster to set up
- You depend on the module's event set and update cycle
- Harder to see exactly which tag produced a value
Merchants who want standard tracking live quickly and accept the vendor's defaults.
Manual insertion
- Full control over the container, data layer, and every event
- No hidden tags beyond what you wrote
- You build and maintain each event yourself
- Theme changes or upgrades can wipe your snippet
Teams or freelancers who need custom events and can maintain the code.
Running both
- No real advantage once testing starts
- Duplicate events and conflicting values
- Preview shows tags you did not build
Nobody: pick one route and remove the other before you spend on ads.
05 / 12
PrestaShop GTM module: how it works and who it is for
A PrestaShop GTM module installs the container for you and pushes store data into the data layer, with no theme edits needed.
The module loads the container and pushes order, product, and cart values into the data layer itself. It suits merchants who want GTM live without touching theme files, though it adds a dependency you must keep updated.
PrestaShop GTM Module
A PrestaShop addon that inserts your Google Tag Manager container and pushes store data into the data layer through configuration screens.
- How it loads the container
- Injects the GTM snippet on every front-office page from the module, so no theme edit is needed.
- Data layer coverage
- Typically pushes page type, product ID, price, cart contents, and order totals, depending on the module. Check the vendor's documentation for the exact event names.
- Setup effort
- Install, enter your container ID, enable the events you need. A few hours for a standard shop if the module documents its data layer.
- Maintenance
- Theme or PrestaShop updates sometimes change the markup the module reads, so re-test after each upgrade.
- Cost
- Varies widely by vendor and plan. Treat any figure as an order of magnitude and check the vendor's pricing page for the current rate.
- No theme file edits, so a PrestaShop upgrade is less likely to wipe the tracking code.
- Configuration and event toggles sit in the back office, which non-developers can manage.
- Consistent data layer format across shops using the same module.
- You depend on the vendor for updates when PrestaShop or a theme changes.
- The data layer structure is fixed: adding a custom event usually means extra code anyway.
- Poorly built modules can slow the page or duplicate events already sent by another addon.
- Cost and support quality differ a lot between vendors, so the module is not automatically cheaper than manual insertion.
The right fit if your team has no front-end developer and you want GTM events running this week. If you need full control over event names and payloads, manual theme insertion gives you that and avoids a recurring fee.
06 / 12
Manual theme insertion: how it works and who it is for
Manual theme insertion means pasting the GTM container snippet directly into your PrestaShop theme files, which gives you full control but no module interface.
You edit your theme's head.tpl to place the container script in the <head> section and add the noscript fallback right after the opening <body> tag. This keeps the code template-native, so it survives as long as you do not switch themes.
The trade-off is maintenance: theme updates can overwrite your edits, and you handle consent logic and data layer variables yourself. It suits teams with developer access who want no module dependency.
Manual theme insertion
A method where you paste the GTM container snippet directly into PrestaShop theme template files instead of installing a module.
- Where the code goes
- Container script in head.tpl head tag, noscript tag after the opening body tag in the theme template
- Skill required
- Comfort editing .tpl files, FTP or file manager access
- Module dependency
- None
- Consent handling
- You wire the GTM consent mode to your banner yourself
- Update risk
- Theme upgrades or switches can overwrite or lose your snippet
- No third-party module to install, update, or license
- Full control over exactly where and how the snippet loads
- Works on any PrestaShop version without waiting for module compatibility
- Requires developer access and template file editing
- Theme updates can overwrite your changes
- You build the data layer and consent integration yourself
The right choice for teams with a developer on hand who want a module-free setup and are comfortable maintaining the code through theme changes.
07 / 12
PrestaShop GA4 module running alongside GTM: how it works and who it is for
A native GA4 module and GTM can coexist, but only if you disable the module's own tracking so the two don't fire the same hits.
Modules sold in the PrestaShop Addons marketplace usually inject GA4 through PrestaShop's own controller hooks, which places them outside GTM's control. When the container also sends ecommerce events, the same purchase or view item call leaves the browser twice.
PrestaShop GA4 module running alongside GTM
A module that injects Google Analytics 4 tracking directly into PrestaShop, without routing the data through Google Tag Manager.
- How it works
- Installs GA4 tags via PrestaShop hooks, separate from the GTM container
- Typical role
- Fast GA4 reporting for merchants who never plan to add other marketing tags
- Overlap risk
- Both the module and GTM can return the same pageview or ecommerce event
- Consent
- The module's own consent handling may bypass your banner's GTM triggers
- Maintenance
- Depends on the module developer, not on your GTM container updates
- GA4 setup takes minutes, no tag configuration in GTM
- Works even if the theme's GTM snippet is incomplete or missing
- Add-on support covers PrestaShop version updates
- Ecommerce parameters are fixed by the module and hard to extend
- Duplicate pageviews and purchase events are a common side effect of running both
- Consent logic often lives in the module, not in GTM, so it escapes your tag audit
A fit for small stores that want GA4 reporting only; skip it if you already run a full GTM container, or disable its analytics tracking and keep the module for other features.
08 / 12
Why is my ecommerce data counted twice?
Duplication usually means a PrestaShop GA4 module and a GTM tag both send the same event.
Two tags sending the same event is the usual cause. Run GA4 DebugView while you buy a test product: if add_to_cart or purchase shows twice, you have a conflict.
Then open GTM Preview and note which tag fired each event. Disable the one you do not want, but keep the module until you confirm GTM covers every event.
Run a full test purchase
Use a real product and complete checkout. Duplicates only show on events that fire, not on previews.
Check GA4 DebugView
Open Admin > DebugView and look for the same event name twice in the last 30 minutes. Each duplicate is a tag sending it.
Trace the source in GTM Preview
In Preview, click each event and see which tag fired. A GA4 Configuration tag or ecommerce tag may run alongside your module.
Review module settings
In your PrestaShop GA4 module, look for an option that sends events to GA4. If enabled, it duplicates GTM.
Disable only one sender
Turn off the module's tracking or pause the GTM tag, then retest. Confirm GTM alone still sends the same events before you remove the module.
Going further
Why events double
Special case
How triple-counting happens in PrestaShop
Triple-counting happens when a module, an old GA4 snippet, and a GTM tag all send the same purchase event.
A PrestaShop GA4 module can inject its own gtag.js snippet and send events. An old manual GA4 snippet left in your theme adds a second sender. Your GTM container then fires a third. All three reach GA4, so one purchase becomes three.
This is common after a migration: you install GTM but leave the module and old code in place. GA4 DebugView will show three identical purchase events, and each has a different source in its parameters.
To stop it, disable or uninstall the module and remove the old snippet. Keep only GTM. Test again with one purchase and confirm the event count is one.
- Module GA4 tagCheck your PrestaShop module settings for an option like 'Enable GA4 tracking' and turn it off.
- Old GA4 snippetSearch your theme files for 'gtag' or 'G-' and remove any hardcoded snippet.
- GTM tagsIn GTM, keep only one GA4 Configuration tag and one ecommerce tag per event.
- RetestAfter changes, use GA4 DebugView to confirm each event appears once.
09 / 12
How do I test ecommerce events in GTM and GA4?
Run one real order from your own device and watch it appear step by step.
Open GTM Preview, enter your store URL, and connect the session to your own browser. Then walk the funnel in order: product view, add to cart, checkout, purchase. Each step should push a data layer event before the page finishes loading.
Switch to GA4 DebugView, a GA4 section that lists events from your own device in real time, and confirm each event fires once, with the right product IDs and order value. If a step never appears in Preview, the container did not load on that page: Tag Assistant confirms this fastest.
-
Open GTM Preview
Enter your store URL and connect the session. Keep the Preview panel open in the same browser you will order from.
-
Walk product view and add to cart
Load a product page, then add an item. In Preview, check that a view_item and an add_to_cart event arrive with the correct item ID, price, and currency.
-
Continue to checkout
Proceed through the cart and checkout steps. Each funnel page should show a begin_checkout event; a missing event here usually means the container did not load on that template.
-
Complete the purchase
Place a real order with a payment method you control. On the confirmation page, verify a purchase event carrying the order ID, tax, shipping, and total.
-
Check GA4 DebugView
Open DebugView in GA4 and watch events from your device appear live. Confirm each event appears exactly once with the expected parameters.
-
Use Tag Assistant as backup
If an event never shows in Preview, run Tag Assistant on that exact URL. It reports whether the GTM container loaded at all, which separates a missing tag from a missing container.
10 / 12
What does my consent banner have to do with GTM?
If your cookie module blocks tags and Consent Mode is not set up, your data drops without an error.
Consent Mode is the layer that tells Google tags whether a visitor accepted cookies before they fire. Your PrestaShop cookie module can also block GTM itself, so with consent refused the tags never run and you see fewer events by design, not a bug.
Load order matters: whichever script runs first wins. If the cookie module loads before the GTM container, it can stop every tag from starting. Test one state at a time.
Consent states and what GTM Preview should show
| Visitor consent state | What should fire | What you see in GTM Preview |
|---|---|---|
| Consent accepted | Full tags (page view, purchase, add to cart) | Tags listed as Fired |
| Consent refused | Only Consent Mode pings, no cookies | Tags absent or Blocked |
| Consent not asked yet | Nothing, until the banner resolves | No tags in the timeline |
Illustrative states: exact behavior depends on your cookie module and Consent Mode setup. Verify in GTM Preview.
11 / 12
In what order do I fix missing data?
Work container, data layer, trigger, tag, then GA4 report, and stop at the first failure.
Work in one direction: container first. If Google Tag Manager is not on the page, no data layer, trigger or tag can help. Open the page source and search for the container ID; if it is missing, stop and fix that before anything else.
When the container loads but DebugView shows empty values, fix the data layer next. Only then debug the trigger, then the tag. If a value is correct in DebugView but absent in GA4, wait for the report's processing window before changing code.
1. Container present?
Search the page source for your GTM container ID. If absent, nothing below matters.
2. Data layer correct?
Check that key ecommerce values (items, value, currency) are populated. Empty values send nothing useful.
3. Trigger firing?
Use GTM Preview to confirm the trigger fires on the right action. A correct trigger with empty data still sends nothing.
4. Tag sending?
Confirm the tag fires and sends the expected parameters. Check the network tab for the GA4 request.
5. GA4 report showing?
If DebugView is correct but reports are empty, wait for processing before editing anything.
12 / 12










