WordPress Plugin
Install and configure Pulse Analytics on WordPress without touching code.
The Pulse Analytics plugin installs and configures the tracking script from your WordPress admin. No theme editing required.
Installation
- In your WordPress admin, go to Plugins → Add New.
- Search for Pulse Analytics.
- Install and activate the plugin.
- Click Pulse in the WordPress admin sidebar to configure.
Settings reference
| Setting | Default | Description |
|---|---|---|
| Domain | auto-detected | Your domain as registered in Pulse. Auto-detected from site_url(), but override here if they differ. |
| Track Admins | OFF | Track pageviews from logged-in administrators. Disable to keep dev traffic out of analytics. |
| API URL | https://pulse-api.ciphera.net | Advanced — only change if you are self-hosting the Pulse backend. |
| Script URL | https://js.ciphera.net/script.js | Advanced — only change if you are self-hosting the Pulse backend. |
Both Advanced fields must be an HTTPS URL that resolves to a public address. An entry that fails either check is silently replaced with the default — the settings page shows no error, so confirm the saved value after changing one.
Proxy mode was removed
Versions before 1.4.0 could route the tracking script and analytics requests through your own WordPress server, and this page recommended it. That was wrong twice over, so the feature is gone. Nothing replaces it and nothing needs to: update the plugin and analytics keep working.
It recorded nothing. Your browser attaches an Origin header to every request it makes; a
server forwarding that request on your behalf does not. Pulse requires an Origin or Referer
matching your registered domain and answers 403 when it finds neither, so every forwarded
pageview was rejected before it was recorded. The tracking script has no way to report that, so
the only symptom was a dashboard that never filled up.
And it did not get around ad blockers, which was the entire reason it existed. The filter
lists that block analytics are mostly path rules rather than domain rules — they match a
request path such as /api/v1/… wherever they find it, so they applied to your own domain exactly
as they do to ours. We measured this in August 2026, when a rule written for an unrelated vendor
blocked Pulse's engagement beacon on proxied and direct installs alike. The fix was to move the
beacon to a different path; proxy mode made no difference in either direction.
Note
Nothing to do. If your dashboard was empty while proxy mode was on, data starts arriving again as soon as you update, and anything already recorded is unaffected. The Enable Proxy setting is gone from the settings page, along with the cached script and daily refresh job it used.
Multisite
On WordPress Multisite, the plugin can be network-activated. Each subsite uses its own domain setting, which defaults to the subsite's site_url(). Configure each subsite's domain from its own Pulse menu in the WordPress admin sidebar.