Joomla analytics plugin

The StatJolt Joomla analytics plugin adds your tracking code to every page of your site.

The statistics are cookieless. So you don't need a cookie banner, because there is no personal data. Nothing is written to your Joomla database either. So your table sizes stay unchanged. That helps if you have heavy traffic, or if you take backups often.

Install it in four steps

1. Download the package. Keep the zip file as it is. Do not unpack it.
2. In your Joomla administrator open System, then Install, then Extensions. Drop the zip on the Upload Package File tab. The plugin arrives switched on so there is nothing to enable.
3. Open System, then Plugins and search for StatJolt. Open your StatJolt account, press the copy button under your code, then paste it into the field and save.
4. Open your site in a private window. The status turns green once your first visitor arrives and you press Check again.

After you install it, Joomla notifies you on its own when a new version arrives.

What the status colours mean

• Green. Data is arriving. Nothing to do.
• Amber, waiting for your first visitor. The code is in place but nobody has loaded a page yet. Open your site in a private window.
• Amber, no visit seen from your domain. The code is saved but StatJolt has not received anything from this address. Clear your cache!
• Red, the ID does not exist. The number you pasted belongs to no StatJolt account. Copy your code again.
• Red, the domain is switched off. You marked this domain as not yours in your StatJolt account. Turn it back on in your site list.
• Grey. StatJolt could not be reached just now. Try again in a minute.

Which Joomla versions it works on

Joomla 4, Joomla 5 and Joomla 6. The plugin is written against the modern extension API and it will keep working on Joomla 7.

The plugin ships with its interface in nine languages: English, Hungarian, German, Spanish, French, Portuguese, Italian, Dutch and Polish.

Where the code goes

Nothing to configure. The plugin writes the code into the finished page, immediately before the closing body tag, on every front end page.

That matters more on Joomla than it sounds. Extensions that inject through a template position only fire where that position exists and where the menu assignment matches so tracking quietly disappears on some pages. This plugin does not care how your template is built or which positions it has. It edits the page after your template has finished with it.

You cannot break it by pasting twice either. StatJolt runs once per page so double counting is not possible.

Where the badge goes

StatJolt shows a small badge on your site. You choose its position in your StatJolt account, not in the plugin.

If your badge floats, it pins itself to a corner of the screen and the plugin asks you nothing. It puts the code at the bottom of the page, where it interferes with nothing.

If your badge sits in the page flow, put the {statjolt_badge} token wherever you want it. It works in any article and in a Custom module so you can drop the badge into a footer position and have it sit inside your layout.

Pages without the token still get the tracking code at the bottom. Nothing goes unmeasured.

Caching

The code the plugin adds is the same for every visitor.

After you save your ID, the plugin clears the Joomla cache for you. If you also run a CDN or a server side cache in front of Joomla, clear that one yourself.

Who is not counted

Logged in users are skipped. You can turn that off with a single switch if you want to see your own visits.

The administrator area is never touched. Neither are feeds, JSON and raw responses or the component only views Joomla uses for print and modal windows. Those are not pages a visitor reads so counting them would only distort your numbers.

What the plugin stores

Your settings and nothing else. They live in the single row Joomla already keeps for every installed extension.

There are no custom tables and no per visit writes. That is exactly the point. Many analytics extensions log to your own database, so every page view turns into a database write. All of that ends up in your backups too, and it can slow your website down.

Raw IP addresses never reach disk on the StatJolt side either. The visitor identifier is a hash that is regenerated with a new salt every midnight so yesterday's visitor cannot be matched to today's. The full detail is in the privacy policy.

If you are coming from Google Analytics

You do not need to keep both running. StatJolt replaces the page view, source, page and device reporting you were using GA4 for. It adds Core Web Vitals, funnels and user journeys that GA4 either buries or does not have. There is a fuller comparison in the GA4 alternative guide.

StatJolt sets no cookies and collects no personal data so most sites need no consent banner at all. The legal side is in Google Analytics and the GDPR.

Running WordPress, Drupal or Webflow somewhere too? There is a StatJolt WordPress plugin, a Drupal module and a Webflow guide as well. The same account and the same snippet cover every site you own.