Google Ads and GA4 tracking for Shopware
Standard self-hosted issues, with the addition that headless Shopware storefronts have the SPA route-change problem on top.
Free30 minutesNo obligation
Shopware + Google · what breaks
What goes wrong on Shopware
- 01
Plugin overlap
The Shopware plugin ecosystem, same as any marketplace.
- 02
Headless storefronts
Route changes that aren't page loads, if you've gone that way.
- 03
Sales channel configuration drift
Multiple channels with separate settings.
- 04
Payment method return variance
Each with its own path.
Shopware + Google · the fix
What changes — Shopware + Google
One conversion per order
From the order-placed event.
Sales channel carried through
So per-channel faults are visible.
Headless storefront events defined
Where applicable.
Shopware + Google · architecture
How the Google destinations behave on Shopware
Self-hosted basics, plus headless considerations.
- 1
transaction_id as the order number
Shopware's own reference.
- 2
Counting set to every
Ecommerce.
- 3
Route-change events if headless
The SPA problem, if that's your architecture.
- 4
Click IDs into order custom fields
Surviving to the order.
- 5
Per-sales-channel reporting
So drift is visible.
Shopware + Google · diagnose
Where Shopware tracking breaks, in diagnostic order
Each check rules out a class of cause, so by the last one there is usually a single explanation standing.
- 01
Check whether the storefront is headless
It changes the front-end diagnosis entirely.
- 02
List plugins touching tracking
Per sales channel.
- 03
Test each payment method's return
Individually.
- 04
Reconcile per sales channel
Not in aggregate.
- 05
Refresh the confirmation
Watch for a second event.
Shopware + Google · prove
The QA evidence — Shopware + Google
Run on Shopware specifically, on a live conversion rather than in preview mode.
Source of truth
your Shopware order records
- Order-placed event confirmed firing once per order.
- Sales channel present on every event.
- Route-change events verified if the storefront is headless.
- Purchase count reconciled per channel for a closed week.
- A refund tested and confirmed reversing.
- Reconciled over a fully closed window, matched per record rather than on totals.
- Re-checked 30 days later, and after any platform update.
Shopware + Google · free audit
What we check in the free audit
- Check whether the storefront is headless
- List plugins touching tracking
- Test each payment method's return
- Reconcile per sales channel
- Refresh the confirmation
Checked against
your Shopware order records
Free30 minutesNo obligation
Shopware + Google · when not to buy
When you don't need this on Shopware
Worth reading before you buy anything, from us or anyone.
- If your numbers reconcile per sales channel, the platform is doing its job.
- Shopware's event system is clean and your developer can wire this without much difficulty.
- If you're not headless, ignore the SPA sections entirely.
- Reconcile per channel before assuming anything is broken.
Shopware + Google · what we deliver
What gets built for Google on Shopware
GA4 ecommerce events in the recommended shape
Correct names, transaction_id present, currency per order, an items array that agrees with the value.
Click identifiers captured and persisted
gclid, gbraid and wbraid — not just the first, because iOS traffic arrives with the others.
Enhanced Conversions from the data layer
Not from CSS selectors, which break on every redesign silently.
Conversion action settings reviewed
Counting, primary status and attribution window — free to change and more consequential than most tag work.
Written guarantee
95%+ tracking accuracy
Measured against your Shopware order records. Miss it and we keep working at no cost.
Pricing
Pick the package that fits your ad spend
Browser-side starter
$400One-time fee · lifetime ownership
Repairs and verifies the browser-side setup you already have, on a live conversion. Honest about its ceiling on this platform.
- Root cause fixed, not worked around
- Verified on a live conversion
- Reconciled against your own records
- Written handover
1st-party server-side
Recommended$800One-time fee · most popular
Money events sent from your own records through a first-party container on your subdomain, so the browser can no longer lose them.
- First-party server container on your own subdomain
- Money events from your records, not the browser
- Deduplicated on a shared event ID at every destination
- First-party cookies beyond Safari's 7-day cap
- 95%+ accuracy and 8+ Meta EMQ, guaranteed in writing
Full 1st-party stack
$1,800One-time fee · lifetime ownership
Every paid channel server-side plus the offline loop, with monitoring so the next break surfaces in days.
- Everything in 1st-party server-side
- Pinterest, Snapchat, Reddit and LinkedIn CAPI
- CRM and offline conversion loop
- Refunds and cancellations corrected wherever each platform allows it
- Monitoring on every destination
FAQ
Shopware + Google questions, answered
Every, for ecommerce.
Only if your storefront is headless. On the standard storefront, no.
Order custom fields, so they survive to the order record.
Yes. Configuration drift between channels is common.
Free · 30 min
Get Google Ads and GA4 right on Shopware
WhatsAppFree30 minutesNo obligation
