Google Ads and GA4 tracking for PrestaShop
Refresh duplication and module overlap, plus per-shop configuration drift on multi-store installs.
Free30 minutesNo obligation
PrestaShop + Google · what breaks
What goes wrong on PrestaShop
- 01
Revisitable order confirmation
The familiar self-hosted duplication source.
- 02
Module overlap
A tracking module plus a theme override.
- 03
Multi-store reference collisions
Two shops numbering from the same start.
- 04
Payment module return variance
Each with its own path back.
PrestaShop + Google · the fix
What changes — PrestaShop + Google
One conversion per order
From the order validation hook.
References namespaced per shop
So deduplication works across the estate.
Module paths resolved
One sender retained.
PrestaShop + Google · architecture
How the Google destinations behave on PrestaShop
Same self-hosted pattern, plus per-shop verification.
- 1
transaction_id as the namespaced reference
Unique across shops.
- 2
Counting set to every
Ecommerce.
- 3
Per-shop reconciliation
An estate average hides a broken shop.
- 4
Click IDs into order meta
Surviving the gateway.
- 5
Currency per shop
Multi-store often means multi-currency.
PrestaShop + Google · diagnose
Where PrestaShop 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 for reference collisions across shops
A silent conversion loss.
- 02
Refresh the confirmation page
Watch for a second event.
- 03
List modules per shop
They differ more than expected.
- 04
Test each payment module's return
Individually.
- 05
Reconcile per shop
Not in aggregate.
PrestaShop + Google · prove
The QA evidence — PrestaShop + Google
Run on PrestaShop specifically, on a live conversion rather than in preview mode.
Source of truth
your PrestaShop order records
- Order reference uniqueness verified across shops.
- Confirmation page refreshed with no additional event.
- Each payment module's return tested.
- Purchase count reconciled per shop for a closed week.
- A credit slip 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.
PrestaShop + Google · free audit
What we check in the free audit
- Check for reference collisions across shops
- Refresh the confirmation page
- List modules per shop
- Test each payment module's return
- Reconcile per shop
Checked against
your PrestaShop order records
Free30 minutesNo obligation
PrestaShop + Google · when not to buy
When you don't need this on PrestaShop
Worth reading before you buy anything, from us or anyone.
- Single-shop PrestaShop with reconciling numbers: the multi-store complexity here doesn't apply.
- The hook work is ordinary PrestaShop development your developer can do.
- Check for reference collisions before treating namespacing as a problem — they may not overlap.
- Reconcile per shop first. It's free and it locates the fault.
PrestaShop + Google · what we deliver
What gets built for Google on PrestaShop
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 PrestaShop 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
PrestaShop + Google questions, answered
Yes. An estate-level number hides which shop is broken.
Every, for ecommerce.
Send currency per order. Multi-store frequently means multi-currency.
Order meta, which survives the gateway round trip.
Free · 30 min
Get Google Ads and GA4 right on PrestaShop
WhatsAppFree30 minutesNo obligation
