This is the most common Shopware GA4 tracking problem. The live store uses a staging or test GA4 Measurement ID. All real customer data goes to the wrong property. Your live GA4 dashboard shows nothing. Your staging property fills with real orders.

It happens after a site migration. The staging ID is copied to production and no one checks. Or the GA4 plugin has a test ID set from development.

• ✦Find your Measurement ID in GA4. Go toAdmin → Data Streams → your stream. Copy the Measurement ID. It starts withG-. This is the ID your live Shopware store must use.
• ✦Check the ID in Shopware. If you use a plugin, go to the plugin settings and compare the ID. If you use GTM, open your GTM workspace. Find the GA4 Configuration tag. Check the Measurement ID field.
• ✦Test the fix. Open GA4 DebugView. Visit your live store. A page view event should appear within 5 seconds. If it does, the property ID is now correct. Place a test order to confirm the purchase event also fires.

Shopware GA4 tracking plugins push events to the data layer on their own. GTM also reads the data layer and sends events to GA4. If both are active for the same events, every purchase, page view, and add-to-cart fires twice. Your Shopware analytics data shows double revenue and double sales.

This Shopware GA4 tracking issue is hard to spot in GA4 itself. The numbers just look high. But DebugView shows the same event twice within milliseconds. That is the tell.

• ✦Open GA4 DebugView. Add an item to your cart. Look at the event stream. If you seeadd_to_cartappear twice in quick succession, you have duplicate tracking. The same applies topurchaseevents on the thank-you page.
• ✦Decide which method you want to keep — plugin or GTM. If you keep the plugin, disable the GA4 Configuration tag in GTM or remove it from the GTM container. If you keep GTM, disable the GA4 events in the plugin settings.
• ✦Do not just “pause” one method. Delete or fully disable it. Paused GTM tags can be re-published by accident. Paused plugin settings can reset after a plugin update. Make a clean choice and remove the other fully.
• ✦After fixing, check GA4 DebugView again. Each event should now appear exactly once. Also check GA4 Realtime reports the next day. Revenue should drop to roughly half of what it showed before. That is the correct number.

This Shopware Google Analytics fix is one of the most requested. GA4 shows page views and add-to-cart events. But the purchase event never fires. Revenue in GA4 stays at zero. The orders exist in Shopware. They just never reach GA4.

The purchase event must fire on the order confirm page. In Shopware, this is the page after checkout.order.placed. If your GTM tag fires on the wrong page, the data layer is empty. The order data has not loaded yet.

• ✦Go to your Shopware store. Place a test order. After checkout, land on the thank-you page. Open Chrome DevTools. Go to the Console tab. Runwindow.dataLayer.filter(e => e.event === 'purchase'). If the result is an empty array, the purchase event is not in the data layer.
• ✦If using a plugin, check the plugin settings. Look for an option labelled “send purchase event on order confirm” or “fire on /checkout/finish”. Make sure it is enabled. Some plugins default to sending on order creation — not on the confirm page.
• ✦If using GTM, check the trigger for your purchase tag. It should fire on a page view where the URL contains/checkout/finish. A trigger that fires on all pages or on a custom event may never match the correct page.
• ✦Also check for a dataLayer clear event. Some plugins push{ event: 'gtm.dom' }before the purchase event. This can wipe the ecommerce object from the data layer. Add an explicitdataLayer.push({ ecommerce: null })before your purchase push to reset it cleanly.

Cookie consent tools block GA4 until a user accepts. This is correct for GDPR. But many setups go too far. They block GA4 entirely — even for users who accept. The tag never loads. So even willing users are not tracked.

The result: your Shopware analytics data shows far fewer sessions than your server logs. The gap is your consent block rate. Sessions, revenue, and sales all appear lower than reality.

• ✦Check the consent trigger in GTM. Open GTM. Find your GA4 Configuration tag. Look at the firing trigger. It should fire on “Consent Initialisation” or after the user accepts analytics cookies. A trigger that fires on “All Pages” may be blocked by your consent tool before it runs.
• ✦Use GTM’s built-in consent mode. Setanalytics_storageas a required consent type. GTM then handles the blocking on its own. Your Shopware GTM setup does not need a custom consent trigger — the consent mode handles it.
• ✦Test consent behaviour. Open your store in a private window. Dismiss the consent banner without accepting. Open GA4 DebugView. No events should appear. Then reload, accept all cookies, and browse. Events should now appear. If they do not appear after acceptance, the consent trigger is blocking everything.
• ✦Consider GA4 Consent Mode v2. Since March 2024, Google requires Consent Mode v2 for EU users. Without it, GA4 cannot model sales for users who decline. This is separate from whether your tag fires — it affects how GA4 fills in the data gaps.

Shopware supports multiple currencies. But the data layer often sends the wrong one. The currency field in the purchase event may be missing or hardcoded to a default. GA4 then shows zero revenue for orders in other currencies — or combines them wrongly.

This Shopware analytics data problem is common in multi-currency stores. The setup works for the default currency. But orders in EUR, GBP, or USD all appear with a wrong or missing value.

• ✦Open the browser DevTools console on the thank-you page. Runwindow.dataLayer.filter(e => e.event === 'purchase'). Check thecurrencyfield. It should match the currency the customer used — not a hardcoded value.
• ✦Check thevaluefield too. It should be a number — not a string. Some plugins pushvalue: "49.99"as a string. GA4 ignores string values. Revenue appears as zero. The fix is to wrap the value inparseFloat()before pushing to the data layer.
• ✦If using a Shopware GTM plugin, update it to the latest version. Most GA4 data layer plugins added proper currency mapping in late 2023. An older plugin version may not readshopwareContext.currency.isoCodecorrectly.

GA4 uses a fixed set of standard e-commerce event names. These are: view_item, add_to_cart, begin_checkout, purchase, and a few others. If your Shopware GTM or plugin sends events with different names, GA4 does not recognise them as e-commerce events. They appear as custom events with no revenue data.

Some older plugins used UA event names. For example, transaction is a UA name. In GA4 it must be purchase.

• ✦Open GA4. Go toReports → Engagement → Events. Look for any event names that do not match the standard GA4 list above. Each custom name is a custom event. GA4 does not link it to e-commerce reports.
• ✦Update your Shopware GTM data layer to use the correct GA4 event names. If you use a plugin, check the plugin changelog. Most updated their event names in 2022 or 2023. Install the latest version and test each event in DebugView.
• ✦Check theitemsarray on each event. GA4 requires anitemsarray on purchase events. Each item must haveitem_id,item_name,price, andquantity. Missing fields cause GA4 to show partial or no product data in reports.