Google Ads and GA4 tracking for Drupal
Cached values are the recurring Google fault here, exactly as on Magento: identical transaction IDs across different orders is a cache signature, not a tag bug.
Free30 minutesNo obligation
Drupal + Google · what breaks
What goes wrong on Drupal
- 01
Aggressive caching
Page cache, dynamic page cache and BigPipe can each serve stale values.
- 02
Conversions come from Commerce or Webform
Not from Drupal itself.
- 03
Module overlap
Two modules sending the same event.
- 04
Complex configuration
Drupal's flexibility means undocumented setups are common.
Drupal + Google · the fix
What changes — Drupal + Google
Money events from order state transitions
Immune to caching.
Form submissions bound to Webform hooks
Not to navigation.
Caching accounted for
Rather than blamed on the tag.
Drupal + Google · architecture
How the Google destinations behave on Drupal
Check for cached values before anything else.
- 1
Compare two orders' payloads
Identical values means cache.
- 2
transaction_id from the order
Not from a cached page.
- 3
Counting per conversion type
Every for Commerce, one for Webform leads.
- 4
Click IDs into order or submission data
Server-side available.
- 5
Enhanced Conversions from the order
Not the DOM.
Drupal + Google · diagnose
Where Drupal 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
Compare two orders' data layer values
Identical means cache.
- 02
Identify which caching layers are active
Page, dynamic page, BigPipe.
- 03
List tracking-adjacent modules
The Drupal inventory step.
- 04
Check whether conversions come from Commerce or Webform
Different hooks entirely.
- 05
Reconcile against Commerce orders
For a closed week.
Drupal + Google · prove
The QA evidence — Drupal + Google
Run on Drupal specifically, on a live conversion rather than in preview mode.
Source of truth
your Drupal Commerce order records
- Two different orders confirmed carrying different values.
- Order state transition confirmed firing once per order.
- Webform submissions confirmed bound to the hook, not a navigation.
- Purchase count reconciled against Commerce for a closed week.
- A refund state transition 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.
Drupal + Google · free audit
What we check in the free audit
- Compare two orders' data layer values
- Identify which caching layers are active
- List tracking-adjacent modules
- Check whether conversions come from Commerce or Webform
- Reconcile against Commerce orders
Checked against
your Drupal Commerce order records
Free30 minutesNo obligation
Drupal + Google · when not to buy
When you don't need this on Drupal
Worth reading before you buy anything, from us or anyone.
- If two consecutive orders produce different, correct payloads and your counts reconcile, the caching problem isn't affecting you.
- This is standard Drupal development your team can do — the event system is well documented.
- If you're a content-only Drupal site with no Commerce, this is really a Webform tracking question and simpler than the page suggests.
- Reconcile before assuming. Drupal setups are often more correct than they look.
Drupal + Google · what we deliver
What gets built for Google on Drupal
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 Drupal Commerce 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
Drupal + Google questions, answered
Place two orders and compare the payloads. Identical values across different orders is conclusive.
Every for Commerce orders, one for Webform leads.
The order, server-side. Never a cached page.
From the order record, yes. From a cached DOM, unreliably.
Free · 30 min
Get Google Ads and GA4 right on Drupal
WhatsAppFree30 minutesNo obligation
