Title: Pulse Analytics
Author: Ciphera
Published: <strong>اپریل 30, 2026</strong>
Last modified: سپتمبر 16, 2026

---

Search plugins

![](https://ps.w.org/pulse-analytics/assets/icon.svg?rev=3519543)

# Pulse Analytics

 By [Ciphera](https://profiles.wordpress.org/ciphera/)

[Download](https://downloads.wordpress.org/plugin/pulse-analytics.1.4.0.zip)

 * [Details](https://ps.wordpress.org/plugins/pulse-analytics/#description)
 * [Reviews](https://ps.wordpress.org/plugins/pulse-analytics/#reviews)
 *  [Installation](https://ps.wordpress.org/plugins/pulse-analytics/#installation)
 * [Development](https://ps.wordpress.org/plugins/pulse-analytics/#developers)

 [Support](https://wordpress.org/support/plugin/pulse-analytics/)

## Description

Pulse Analytics is built by [Ciphera](https://ciphera.net), 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 — under 3 KB tracking script, no impact on page speed
 * 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.

## Screenshots

[⌊Settings page with domain and admin tracking options.⌉⌊Settings page with domain
and admin tracking options.⌉[

Settings page with domain and admin tracking options.

[⌊Pulse menu item in the WordPress admin sidebar.⌉⌊Pulse menu item in the WordPress
admin sidebar.⌉[

Pulse menu item in the WordPress admin sidebar.

## 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](https://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.

### 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](https://ciphera.net), a Belgian privacy-software
company. Sign up and manage your dashboard at [pulse.ciphera.net](https://pulse.ciphera.net).

## Reviews

There are no reviews for this plugin.

## Contributors & Developers

“Pulse Analytics” is open source software. The following people have contributed
to this plugin.

Contributors

 *   [ Ciphera ](https://profiles.wordpress.org/ciphera/)

[Translate “Pulse Analytics” into your language.](https://translate.wordpress.org/projects/wp-plugins/pulse-analytics)

### Interested in development?

[Browse the code](https://plugins.trac.wordpress.org/browser/pulse-analytics/), 
check out the [SVN repository](https://plugins.svn.wordpress.org/pulse-analytics/),
or subscribe to the [development log](https://plugins.trac.wordpress.org/log/pulse-analytics/)
by [RSS](https://plugins.trac.wordpress.org/log/pulse-analytics/?limit=100&mode=stop_on_copy&format=rss).

## Changelog

#### 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

## Meta

 *  Version **1.4.0**
 *  Last updated **1 اونۍ ago**
 *  Active installations **Fewer than 10**
 *  WordPress version ** 5.8 or higher **
 *  Tested up to **6.9.9**
 *  PHP version ** 7.4 or higher **
 *  Language
 * [English (US)](https://wordpress.org/plugins/pulse-analytics/)
 * Tags
 * [analytics](https://ps.wordpress.org/plugins/tags/analytics/)[GDPR](https://ps.wordpress.org/plugins/tags/gdpr/)
   [privacy](https://ps.wordpress.org/plugins/tags/privacy/)[statistics](https://ps.wordpress.org/plugins/tags/statistics/)
   [tracking](https://ps.wordpress.org/plugins/tags/tracking/)
 *  [Advanced View](https://ps.wordpress.org/plugins/pulse-analytics/advanced/)

## Ratings

No reviews have been submitted yet.

[Your review](https://wordpress.org/support/plugin/pulse-analytics/reviews/#new-post)

[See all reviews](https://wordpress.org/support/plugin/pulse-analytics/reviews/)

## Contributors

 *   [ Ciphera ](https://profiles.wordpress.org/ciphera/)

## Support

Got something to say? Need help?

 [View support forum](https://wordpress.org/support/plugin/pulse-analytics/)