Easy, cookieless web analytics for Drupal. GDPR compliant statistics with no cookie banner and nothing stored in your own database. Paste your code once and the module puts it on every page.

StatJolt is a hosted service. The module is free and GPL licensed. It sends your page views to statjolt.com, where a free account holds your statistics. See "Additional Requirements" below for exactly what leaves your site.

Features

Cookieless analytics for Drupal

StatJolt is cookieless web analytics for Drupal. It answers the questions you actually ask. Who visited, where they came from, what they read and whether your site was fast enough to keep them.

The statistics are GDPR compliant by design. StatJolt sets no cookies and collects no personal data, so most sites need no consent banner at all.

Nothing lands in your Drupal database. No node counter, no log table, no queue. The module writes one configuration object and nothing else, ever.

You paste your code into one field. The module puts it on every page of your site.

Google Analytics gives you data. StatJolt gives you answers.

Setting up GA4 is a project. You create a property, wire up a data stream, learn what an engagement event is, then add a cookie banner because you now need consent. Weeks later you are still hunting for the number you wanted on day one.

StatJolt skips all of it. One snippet, real numbers, no sampling and no waiting for reports to process.

Why not an analytics module that fills up your Drupal database?

Self hosted analytics modules write a row to your Drupal database on every single page view. On a quiet site you will never notice. On a busy one those tables grow into the millions, your queries slow down, your backups swell and your host starts asking questions.

StatJolt keeps none of it in Drupal. The only thing it ever writes is your own settings, once, when you press Save.

You still own your numbers and your visitors still stay anonymous. The work simply happens somewhere built for it.

Set up in one paste

One field. Paste the whole snippet, or only the script line, or only the number. All three work.
Placed for you. The code goes before the closing body tag on every front end page. There is nothing to configure and no template to edit.
Works with any theme. The module writes into the finished response, so it does not care how your theme is built or which regions it has.
Cache correct. The tracking code carries the settings cache tag, so saving your settings clears the pages that hold it. There is nothing to purge by hand.
Honest status. The settings screen tells you whether StatJolt is genuinely receiving data from this site, not merely that a code is saved.
Counts once. The tracking script goes in from one place only, whatever else you do with the block or the token. You cannot accidentally double count.

What you see

Unique visitors and pageviews, as a trend rather than noise
Where traffic comes from: search, social, direct and UTM campaigns
Which pages people actually read
Devices, browsers and countries
Live visitors, right now, with no report processing delay

The dashboard is built to be read, not studied. Open it and understand your site in under a minute.

More than pageviews

Most analytics tools keep their best features for the priciest tier or expect you to bolt on a second product. StatJolt includes them from the start.

Core Web Vitals. LCP, INP, CLS, FCP and TTFB are tracked beside your traffic, automatically. These are the numbers Google uses to rank you. StatJolt does not only tell you who visited, it tells you whether your site was quick enough to keep them.

User journeys. See the real paths through your site, such as Home to Pricing to Signup, as a flow you can read at a glance.

Funnels, found automatically. Want to know where people give up before checkout or signup? Funnel analysis is locked behind expensive plans almost everywhere else. Here it is included and it recognises many platforms on its own.

JavaScript errors. Broken scripts cost you conversions silently. StatJolt reports the errors your visitors hit, so you find out before your customers tell you.

Privacy by design, not by policy

No cookies. StatJolt does not need them, so it does not use them.
No consent banner required in most countries.
No personal data collected. You get the insight, your visitors keep their privacy.
Raw IP addresses are never written to disk. The visitor identifier is a daily hash and the salt changes every midnight.
Servers are inside the European Union.
Nothing to configure to stay compliant.

Who it is for

Bloggers and publishers who want to know which articles landed, without a course in analytics.
Small business owners who need answers this afternoon, not a certification.
Agencies and freelancers running many sites. One StatJolt account covers all of them and the same snippet works on every one.
Anyone tired of cookie banners who would rather not ask every visitor for consent to count them.

What it costs

The module is free and GPL licensed. The StatJolt service costs nothing for low traffic sites. In exchange it shows a small badge on your site.

About the badge

StatJolt displays a small badge on your site. You control it from your StatJolt account. Move it to another corner or restyle it to suit your design. The badge cannot be switched off, so plan a spot for it before you install.

By default the badge places itself and the module asks you nothing. When you want it somewhere specific, there are two ways:

Block layout. Place the StatJolt badge block in any region, the same way you place any other block.
Inside content. Put {statjolt_badge} in the text and enable the StatJolt badge filter on that text format. Give the filter a high weight, so it runs after the filter that limits allowed HTML.

Pages with neither still get the tracking code, so nothing goes unmeasured.

Who is not counted

Logged in users are skipped, which you can turn off with a single checkbox. Administration routes are never touched, and neither is anything that is not an HTML page response, such as JSON, ajax callbacks, feeds and file downloads.

Post-Installation

Download the module and unpack it into your site's modules folder.
Go to Administration, Configuration, System, StatJolt Analytics.
Paste the code you copied from StatJolt and save.
Open your own site in a private window. The status turns green once your first visitor arrives and you press "Check again".

Additional Requirements

Drupal 10 or 11
A free StatJolt account, for the site ID you paste in
Outbound HTTPS from your server, for the setup check on the settings screen. The module still installs and still tracks without it.

This module connects to StatJolt at https://statjolt.com, the analytics service it is built for. Three separate connections happen.

Visitor statistics. On every front end page view the visitor's browser loads https://statjolt.com/measure/c.min.js and that script sends the page view to https://statjolt.com/measure/counter.php. What is sent: your StatJolt ID, the page path, the page title, the referrer, screen width, browser language, UTM campaign parameters, Core Web Vitals timings and uncaught JavaScript errors. No cookies are set.

Setup check. When you open the module's settings screen, your server calls https://statjolt.com/pluginstatus.php with your StatJolt ID and your site's domain name. StatJolt answers whether the ID exists and whether data is arriving. This happens in the administration area only, at most once every five minutes.

Translations. The module ships nine languages and points the interface translation server at https://statjolt.com/integrations/drupal/build/translations/. Your site downloads them from there when the Interface Translation module is enabled. The same files also travel inside the module, so a site with no outbound access can import them by hand.

Recommended modules/libraries

None. StatJolt works standalone on top of Drupal core, with no other module or libraries required.

Documentation

Full documentation: https://statjolt.com/en/page/drupal-analytics-module

StatJolt Analytics