Conversion tracking for Drupal
Drupal is a content framework first, so conversions come from Drupal Commerce or from webform submissions rather than from Drupal itself. Its caching is aggressive by design — page cache, dynamic page cache and BigPipe — which means a data layer rendered into a cached page carries the wrong values, in the same way Magento's does. The reliable event source is the order state transition.
Free30 minutesNo obligation
Drupal tracking · 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 tracking · the fix
What changes — Drupal tracking
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 tracking · architecture
What Drupal actually lets you do
A framework rather than a product: everything is possible and nothing is assumed.
- 1
Full PHP and a rich event system
Hooks and events for everything.
- 2
Drupal Commerce
Where ecommerce orders live, if you have them.
- 3
Webform
Where lead submissions live.
- 4
Multiple caching layers
Page, dynamic page and BigPipe.
- 5
Module ecosystem
Smaller than WordPress's, same duplication logic.
Drupal tracking · 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 tracking · prove
The QA evidence — Drupal tracking
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 tracking · 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 tracking · 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 tracking · what we deliver
The event map on Drupal
Page view
Browser-side, with caching verified.
Add to cart
Commerce event.
Order placed
Commerce order state transition, server-side.
Webform submission
Webform hook, for lead-generation sites.
Refund
Order state transition.
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 tracking questions, answered
Caching. A per-order value rendered into a cached region carries whatever was cached first.
Drupal Commerce order state transitions for ecommerce, Webform hooks for leads. Not from Drupal itself.
Page cache, dynamic page cache and BigPipe. Any of them can serve stale per-order values.
Yes. Drupal's event system is well documented and this is ordinary work.
Free · 30 min
Get Drupal tracking done properly
WhatsAppFree30 minutesNo obligation
