Conversion tracking for Joomla
Joomla, like Drupal, is a CMS rather than a commerce platform, so the conversion lives in whichever extension handles it — VirtueMart, HikaShop, a forms extension. The first question on any Joomla engagement is which extension owns the transaction, because that determines every subsequent answer. Joomla itself contributes template access, a plugin system and a caching layer.
Free30 minutesNo obligation
Joomla tracking · what breaks
What goes wrong on Joomla
- 01
The conversion lives in an extension
Not in Joomla. Which one decides everything.
- 02
Extension overlap
A tracking extension plus a template modification.
- 03
Caching
Joomla's cache can serve stale per-order values.
- 04
Older installs with undocumented modifications
Common on long-lived Joomla sites.
Joomla tracking · the fix
What changes — Joomla tracking
The transaction owner identified
The first and most important step.
Money events from that extension's hook
Server-side.
Extension paths resolved
One sender retained.
Joomla tracking · architecture
What Joomla actually lets you do
Full PHP access, and a conversion that belongs to an extension rather than the platform.
- 1
Full template and PHP access
Nothing is off limits.
- 2
Plugin and extension system
Where the transaction actually lives.
- 3
Joomla caching
Can serve stale per-order values.
- 4
Commerce extensions
VirtueMart, HikaShop and others, each with their own events.
- 5
Direct database access
For reconciliation.
Joomla tracking · diagnose
Where Joomla 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
Identify which extension owns the transaction
The question that decides everything.
- 02
Refresh the confirmation page
Watch for a second event.
- 03
List extensions touching tracking
Then check the template.
- 04
Check whether caching is active on confirmations
A stale page is a real fault.
- 05
Reconcile against the extension's records
For a closed week.
Joomla tracking · prove
The QA evidence — Joomla tracking
Run on Joomla specifically, on a live conversion rather than in preview mode.
Source of truth
your Joomla extension's order or submission records
- The transaction-owning extension identified and documented.
- Order event confirmed firing once per order.
- Confirmation page refreshed with no additional event.
- Counts reconciled against the extension's records for a closed week.
- A refund tested and confirmed reversing where supported.
- Reconciled over a fully closed window, matched per record rather than on totals.
- Re-checked 30 days later, and after any platform update.
Joomla tracking · free audit
What we check in the free audit
- Identify which extension owns the transaction
- Refresh the confirmation page
- List extensions touching tracking
- Check whether caching is active on confirmations
- Reconcile against the extension's records
Checked against
your Joomla extension's order or submission records
Free30 minutesNo obligation
Joomla tracking · when not to buy
When you don't need this on Joomla
Worth reading before you buy anything, from us or anyone.
- If your counts already reconcile against your commerce extension, nothing here needs doing.
- Identifying the transaction owner takes five minutes and changes the whole answer. Do that before anything else.
- This is ordinary PHP work on a platform you host — your developer can do it.
- Older Joomla installs are often more correct than they look. Reconcile before rebuilding.
Joomla tracking · what we deliver
The event map on Joomla
Page view
Browser-side, caching verified.
Add to cart
Commerce extension event, where applicable.
Order placed
The commerce extension's order event, server-side.
Form submission
The forms extension's submission hook.
Refund
Extension order state change.
Written guarantee
95%+ tracking accuracy
Measured against your Joomla extension's order or submission 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
Joomla tracking questions, answered
Whichever extension handles the transaction — VirtueMart, HikaShop, a forms extension. Joomla itself doesn't issue orders.
Identify which extension owns the transaction. Everything else follows from that answer.
It can serve stale per-order values on confirmation pages, same as any caching CMS.
Yes. It's self-hosted PHP and the extension exposes its own events.
Free · 30 min
Get Joomla tracking done properly
WhatsAppFree30 minutesNo obligation
