Pulse Analytics

By Ciphera

0+ active installationsVersion 1.4.3

Privacy-first web analytics for your WordPress site. No cookies, fully GDPR compliant.

Description

Pulse Analytics is built by Ciphera, a Belgian privacy-software company. Pulse is a lightweight, privacy-first analytics platform that gives you valuable insights about your website visitors without compromising their privacy.

Features:

  • No cookies — fully GDPR, CCPA, and PECR compliant out of the box
  • Lightweight: the tracking script is about 3 KB
  • Simple setup — just enter your domain and you’re tracking

Privacy by design:

Pulse uses a server-side daily-rotating hash for session identification. No cookies, no localStorage, no client-side identifiers. Your visitors’ privacy is respected by default.

Installation

  1. Upload the pulse-analytics folder to /wp-content/plugins/
  2. Activate the plugin through the Plugins menu
  3. Click Pulse in the WordPress admin sidebar
  4. Enter your domain (as registered in your Pulse dashboard)
  5. Done — analytics will start flowing immediately

FAQ

Do I need a Pulse account?

Yes. Sign up at pulse.ciphera.net to create your dashboard and register your domain.

What happened to proxy mode?

It was removed in 1.4.0. It could not work: Pulse rejects a request forwarded by your server, because such a request carries no Origin or Referer header, so a site running proxy mode recorded nothing at all. It also never got around ad blockers, which was the reason it existed — the filter rules that block analytics match on the request path and ignore the domain, so they applied to your own domain exactly as they do to ours. Nothing replaces it, and nothing needs to: the tracking script loads from our CDN and reports directly.

I changed the Script URL to my own copy of the script. What else do I need?

Put script.interactions.js beside it. The script loads it from the same place when clicks, copies and form submits are switched on in your site’s settings in Pulse. The plugin itself needs nothing else.

Does this plugin use cookies?

No. Pulse does not use cookies, localStorage, or any client-side storage for tracking.

Is this GDPR compliant?

Yes. Pulse is designed to be GDPR compliant without requiring cookie consent banners.

Who builds Pulse Analytics?

Pulse Analytics is built by Ciphera, a Belgian privacy-software company. Sign up and manage your dashboard at pulse.ciphera.net.

Screenshots

Changelog

1.4.3

  • The readme gives the tracking script’s size as about 3 KB.
  • New FAQ entry: if you point the Script URL at your own copy of the script, put script.interactions.js beside it.
  • Scroll depth, outbound links, file downloads, and clicks, copies and form submits are switched on or off in your site’s settings in Pulse (Settings > General). The plugin has no setting for them, so there is nothing to do.

1.4.2

  • Saving the settings page shows “Settings saved.” at the top. Before, a save gave no sign that it worked.
  • The hint under API URL and Script URL now says to leave them as they are. It used to mention self-hosting, which Pulse does not offer.
  • The plugin is tested with WordPress 7.1.
  • There is nothing to do.

1.4.1

  • The default domain drops a leading “www.”. When your WordPress address starts with www., the plugin reported every visit as www.example.com, while the Pulse dashboard registers sites as example.com, so a site registered that way recorded nothing. The plugin now reports example.com. Pulse also accepts either form now, so a site registered with or without www. keeps recording.
  • Saving the settings page no longer turns the default domain into a setting of your own. The Domain field stays empty unless you type a domain, and shows the default as a hint, so the default keeps following your site.
  • Nothing to do. A domain you typed yourself is kept exactly as you typed it.

1.4.0

  • Removed proxy mode. It never worked, and it could not be made to work from inside a plugin: Pulse rejects a request forwarded by your server, so a site running it recorded nothing at all. 1.3.0 switched it off; this release takes the setting, the route and the cached script away, and clears what they left behind.
  • Nothing to do, and nothing lost. Sites that were already on 1.3.0 see no change in what is collected. Sites coming from 1.2.0 or earlier start collecting again.
  • The settings page is now three fields: domain, admin tracking, and the two advanced URLs for self-hosted instances.

1.3.0

  • Proxy mode is now off by default, and is switched off on upgrade for any site that still has it on. Leaving it on cost you every pageview: Pulse rejects a request forwarded by your server, and the tracking script reports nothing when that happens, so the dashboard stayed empty with no error shown anywhere.
  • Corrected what the plugin claims about proxy mode. It never got around ad blockers. The filter lists that block analytics match on the request path and ignore the domain, so routing through your own domain changes nothing for them.
  • No action needed. If your dashboard was empty while proxy mode was on, data starts arriving again as soon as the update lands. Nothing that was already recorded changes.

1.2.0

  • Proxy mode forwards the new engagement endpoint. The tracking script now sends time-on-page and scroll depth to /api/v1/engagement instead of /api/v1/metrics, because a widely used ad-blocker filter list blocks the old path by name — on any domain, including your own, so proxy mode did not get around it.
  • The old endpoint keeps working. Proxy mode refreshes its cached copy of the tracking script once a day, so both paths stay available while that catches up.
  • Update the plugin before your cached script refreshes. On 1.1.0 and earlier, proxy mode has no route for the new endpoint, and engagement data stops arriving once the newer script is cached. Pageviews are unaffected either way.

1.1.0

  • Removed frustration tracking (rage clicks and dead clicks). Pulse now ships a single tracking script.
  • The setting is gone and the add-on script is no longer enqueued.
  • Proxy mode now deletes any previously self-hosted copy of the add-on script from wp-content on its next daily refresh — no manual cleanup needed.

1.0.1

  • Readme: brand and company links.

1.0.0

  • Initial release
  • Script injection with domain configuration
  • Proxy mode with randomized endpoints
  • Frustration tracking support (optional)
  • Admin tracking toggle
  • Self-hosted instance support