PulseTrack – Analytics & Conversion Tracking

By pulsetrack

0+ active installationsVersion 1.5.1

Privacy-first WordPress analytics for lead and conversion tracking. Lightweight, local-first - no third-party scripts.

Description

See which traffic sources bring leads and orders – not just pageviews.

PulseTrack is a lightweight, privacy-first WordPress analytics plugin and Google Analytics alternative built for marketers who care about results – all data stays on your own server, with no third-party scripts. Every feature in this plugin is included and unlocked – nothing is locked, trialed, or time-limited.

Key Features

  • Conversion tracking for WordPress – form submits, phone clicks, WhatsApp, and email leads
  • Traffic source attribution – search, social, AI referrals, UTM campaigns, direct
  • Privacy-first analytics – IP anonymization on by default, no third-party data sharing
  • Dashboard – sessions, users, leads, lead rate, traffic sources, campaigns, device/browser breakdown; a store view shows orders and order value instead
  • Sessions and users – accurate counts using fingerprinting, no inflated data
  • Visitor Logs – per-session activity timeline (time, page, event, source, device)
  • Insights – automatically scores your most-visited pages and flags priority pages to fix and quick-win opportunities
  • Export reports – CSV, JSON, and PDF (browser-print report), covering the same data shown on the Dashboard
  • WooCommerce analytics (optional) – add-to-cart and order tracking with orders, order value and order rate; counts orders that are processing or completed when the confirmation page is first shown, in your store currency; requires no configuration
  • WordPress privacy tooling integration – registers with the built-in personal data export/erase tools and privacy policy content
  • Guided first-time setup – a short onboarding screen on first activation

Who Is This For?

  • WordPress site owners who want actionable conversion data without Google Analytics
  • Marketers tracking lead sources and campaigns
  • Agencies needing a privacy-conscious analytics dashboard for clients
  • WooCommerce stores tracking orders alongside marketing performance

Why Not Google Analytics?

  • The frontend tracking script does not load third-party scripts
  • Analytics tracking data is not sent to external analytics services
  • No complexity – focused on leads and conversions, not vanity metrics
  • All data stays on your own WordPress server

Use Cases

  • Track leads from SEO traffic
  • See which campaigns bring leads inside WordPress
  • See which pages orders start from
  • Use as a privacy-first alternative to Google Analytics

Built with performance, privacy, and accuracy in mind.

Installation

  1. Upload the plugin files to /wp-content/plugins/pulsetrack, or install directly through the WordPress Plugins screen.
  2. Activate the plugin through the ‘Plugins’ screen.
  3. You will be guided through a short first-time setup screen. You can also skip it and configure everything later under PulseTrack › Settings.
  4. Visitor consent: by default PulseTrack records a visitor only after they give Statistics consent in your consent banner. If Complianz or CookieYes is active, PulseTrack follows it automatically; there is nothing to set up. Other consent banners work through the free WP Consent API plugin when they support it. If no consent banner is detected, the setup screen shown after activation (and the PulseTrack Dashboard) asks one question: wait for a consent banner, or record without one because you have determined that consent is not required for this tracking. PulseTrack records nothing until you answer, and never treats a missing banner as permission. You can change the answer under PulseTrack › Settings › Privacy › Visitor Consent.

FAQ

Is this a Google Analytics alternative?

Yes. PulseTrack stores all data on your own WordPress server – no third-party scripts, no data sent to Google. It focuses on conversion tracking and lead attribution rather than raw traffic volume.

Is this a Pro plugin, or does it have locked features?

No. Every feature described here is included and fully unlocked, and this plugin needs no license. A separate, optional paid add-on for long-term history and reporting exists; it is a different plugin and is never required.

What data is collected, and is IP anonymization on by default?

PulseTrack records page views, the referring URL, browser/device technical metadata, and (for WooCommerce stores) product and order totals – never a visitor’s name, email address, or billing/shipping details. IP anonymization is enabled by default (the last two octets of IPv4 addresses, or the last 64 bits of IPv6 addresses, are masked before the address is ever stored), and can be reviewed at any time under PulseTrack › Settings › Privacy. To count unique and returning visitors PulseTrack also stores a pseudonymous visitor fingerprint: a keyed hash of the full IP address and the browser user agent, calculated on your server with a secret key of your site. The fingerprint is personal data in many jurisdictions; the suggested privacy policy text (Settings › Privacy in WordPress) describes it.

Which visitor IP address does PulseTrack use behind a proxy or CDN?

PulseTrack uses the address of the connection to your server. It reads a forwarded address only when that connection comes from a private network address (a reverse proxy or load balancer on your host) or from Cloudflare’s published network ranges, so a visitor cannot choose the address PulseTrack records by sending their own forwarding header. If your site sits behind another proxy or CDN with public addresses, add its ranges with the pulsetrack_trusted_proxies filter.

Does PulseTrack send data to any external service?

No analytics tracking data is sent to any external service. PulseTrack stores analytics data in your own WordPress database.

Two optional admin actions can send information by email, and only when an administrator clicks them: Send Feedback and Send Debug Log. Both disclose exactly what will be sent before you send it. No automatic or scheduled email is ever sent by PulseTrack.

Does PulseTrack respect cookie and consent banners?

Yes, automatically. PulseTrack follows Complianz and CookieYes on its own, and any other consent banner that supports the WP Consent API (the WordPress standard) when the free WP Consent API plugin is active. Before a visitor gives Statistics consent PulseTrack creates no identifier, writes nothing to the browser and stores nothing, including WooCommerce cart and purchase events. When consent is given, the page the visitor is viewing is recorded and tracking continues; nothing from before consent is recorded. When consent is withdrawn, tracking stops at once, unsent events are discarded and PulseTrack’s browser storage and cookie are removed. Consent for other categories (marketing, preferences) does not enable PulseTrack. Without one of these PulseTrack records nothing until you answer one question on its setup screen or Dashboard; it never assumes consent, or that consent is unnecessary, because no banner is installed, and it cannot determine your legal obligations for you. If you answer that consent is not required and a consent banner PulseTrack can follow is or becomes active, PulseTrack follows that banner and tells you on the Dashboard, where you can confirm either behavior; this applies from the first request after an update, without anyone opening the admin area. In “Not required on this site” mode PulseTrack still respects a visitor’s recorded rejection of Statistics in a banner it follows. A consent banner plugin that PulseTrack recognizes but cannot read (for example Cookiebot, Cookie Notice, GDPR Cookie Compliance, Real Cookie Banner, iubenda, Borlabs Cookie or the legacy CookieYes banner without the WP Consent API plugin) is never treated as “no banner”: PulseTrack records nothing, names the plugin on the Dashboard, and an earlier “not required” answer given without that banner is not applied. You can connect the banner through the WP Consent API plugin, or explicitly choose on the Dashboard to record without following it, which means PulseTrack will not respect choices made in that banner. A consent banner PulseTrack does not recognize at all cannot be detected. When two consent banners PulseTrack can read are active, a rejection recorded in either one is respected. Showing a banner is not consent: PulseTrack waits for the visitor’s recorded choice. PulseTrack does not provide legal advice; you remain responsible for your consent configuration.

Does this use cookies?

Only after the visitor gives Statistics consent (unless you chose “Not required on this site”), session tracking uses your browser’s local storage, mirrored into a first-party cookie of the same name so that server-side events (such as a WooCommerce purchase) can be linked to the same browsing session. It also keeps the time of the last page view and a short-lived lock in local storage, and the visit’s traffic source in session storage (the suggested privacy policy text lists each key). You can disable cookies under PulseTrack › Settings › Session Tracking; then no cookie and no session identifier are kept in the browser, page views are not linked across page loads, and only the traffic source stays in session storage until the tab is closed. Visitor consent still applies in both cases.

How long is data kept?

Raw visitor logs (individual page views and events) are kept for up to 30 days by default. You can shorten this to 14 or 7 days under PulseTrack › Settings › Privacy; 30 days is always the maximum for raw logs. This raw-log window is separate from Dashboard and Insights analytics: PulseTrack keeps daily summaries for 90 days, so the Dashboard and Insights 60-day and 90-day views stay exact even after the underlying raw logs have been pruned. Most summaries are counts and totals, but the visitor summary keeps one entry per pseudonymous visitor fingerprint and day, so unique visitors can be counted exactly; it is deleted after 90 days like the rest. The date on which a fingerprint was first seen is kept to tell new from returning visitors and is deleted once no visit with that fingerprint has been kept for 90 days. This is included and unlocked for every install – there is no separate tier or upgrade required to see it.

Does WordPress’s built-in privacy export/erase tools work with PulseTrack?

Yes, PulseTrack registers with WordPress’s personal data exporter and eraser. In practice, PulseTrack’s analytics records are pseudonymous (no name, email address or user-account link is stored), so a privacy export/erase request will typically only find matching records for a logged-in user whose login session IP happens to match a stored, non-anonymized record – this is a limitation of applying an identity-based request to pseudonymous data, not a bug.

Does it slow down my site?

No. The tracking script is lightweight, batches requests, and loads asynchronously.

What happens when I uninstall the plugin?

By default, deactivating or deleting PulseTrack leaves all of its data in place. If you want PulseTrack to remove its own data (analytics records, settings, and its database tables) when it is deleted, enable “Delete Data on Uninstall” under PulseTrack › Settings › Advanced first. This only takes effect when the plugin is deleted from the Plugins screen, never on ordinary deactivation. One small counter and date (no analytics data) is kept so that add-ons can tell that data was removed.

Screenshots

Changelog

1.5.1

  • Added: when no consent banner is detected, the setup screen shown after activation and the PulseTrack Dashboard ask one question (wait for a consent banner, or record without one because you have determined that consent is not required for this tracking) instead of leaving the choice in Settings. PulseTrack still records nothing until you answer.
  • Added: a notice on the WordPress Dashboard and Plugins screens while that question is unanswered and nothing is being recorded.
  • Changed: “Not required on this site” now applies to the situation it was chosen in. If a consent banner PulseTrack can follow is active and the choice was not confirmed with that banner present (this includes every choice made in 1.5.0 or earlier), PulseTrack follows the banner: it records only visitors who accept Statistics, and shows this on the Dashboard, where one click confirms either behavior. This takes effect on the first request after the update. Sites without a consent banner are not affected.
  • Changed: a recognized consent banner plugin that PulseTrack cannot read is no longer treated as “no banner”. PulseTrack records nothing, explains how to connect the banner, and requires an explicit acknowledgement on the Dashboard before it records without following that banner.
  • Changed: when two readable consent banners are active, a Statistics rejection recorded in either one is respected.
  • Changed: the Dashboard status line states whether visits are being recorded, for which visitors, or why not.
  • Changed: when the server refuses an event because consent is missing (for example on a page cached before a consent banner was activated), the tracker stops for that page and removes PulseTrack identifiers from the browser.
  • Existing settings are kept on update. No database change.

1.5.0

  • Added: PulseTrack follows Complianz and CookieYes automatically, without the WP Consent API plugin and without any PulseTrack setting. It records a visitor only after Statistics (CookieYes: Analytics) consent is recorded in the banner, and stops when consent is withdrawn. Other banners keep working through the WP Consent API.
  • Changed: in “Not required on this site” mode, a visitor’s recorded rejection of Statistics in a banner PulseTrack follows is now respected, in the browser and on the server. The automatic default of CookieYes before a visitor makes any choice is not treated as a rejection.
  • Fixed: one page reached through differently encoded addresses (for example Hebrew or other non-Latin addresses from your own menus, from search engines or typed by visitors) is now counted as one page instead of several. Page addresses are stored in one standard percent-encoded form.
  • Changed: the Dashboard, Insights and Visitor Logs show non-Latin page addresses as readable text and with the trailing slash your permalink settings use; links open the page’s canonical address.
  • Fixed: on sites with plain permalinks, pages such as ?p=123, ?page_id=5 or ?cat=3 were all counted as the homepage. Pages are now told apart by the WordPress query variables that identify them, including those of custom post types, taxonomies and language plugins. Campaign and click parameters (utm_*, gclid, fbclid and similar), sorting and other unknown parameters still do not create separate pages. Search results count as one page (?s) on every site, without the search term. Visits recorded before the update stay where they were counted; they cannot be split afterwards.
  • Fixed: a page whose address was recorded before the update in another encoding keeps its existing row when it is visited again, so its history is not split by the update.
  • Privacy: the pulsetrack_visitor marker is no longer stored in the browser; no report used it. A value left by an older version is removed on the next visit.
  • Fixed: the Visitor Logs address filter finds pages typed in Hebrew or other scripts and pasted encoded addresses. Excluded paths entered in Hebrew or as an encoded address work, and an excluded path ending in a slash now matches its page. Before, a pasted encoded excluded path could be saved in a form that excluded every page.
  • Privacy fix: a request to export or erase personal data now also finds PulseTrack records of a signed-in user whose visits reach the site through Cloudflare or another trusted proxy, when IP anonymisation is turned off.
  • Changed: the Dashboard and Settings explain in plain language what PulseTrack is waiting for when nothing can be recorded yet.
  • Security fix: forwarded IP headers (X-Forwarded-For, X-Real-IP, CF-Connecting-IP) are used only when the request comes through a private-network proxy or Cloudflare, so visitors can no longer choose the IP address and fingerprint PulseTrack records. Rate limiting now counts each visitor separately behind such proxies instead of counting the proxy as one visitor. Other proxies can be added with the pulsetrack_trusted_proxies filter.
  • Privacy fix: the first-seen dates used to tell new from returning visitors are now deleted once no visit with that fingerprint has been kept for 90 days. Before, they were kept indefinitely.
  • Privacy fix: the suggested privacy policy text now describes the visitor fingerprint, every PulseTrack browser storage key and the 90-day summaries. The readme no longer describes the 90-day summaries as containing no individual visitor records.
  • No database change. Existing data and settings are kept. Where a page was already recorded under two encodings before the update, both rows are kept until they leave the retention period and are shown as readable text.
  • PulseTrack Pro users: update PulseTrack Pro to 1.0.1 or newer first. Pro 1.0.0 compares page history by exact address and would show such pages, and plain-permalink pages, as new and declining pages for one comparison period.

1.4.1

  • Privacy fix: a page saved by a page cache or CDN before the update to 1.4 no longer lets the tracker store PulseTrack identifiers in the browser before consent. The tracker now waits for Statistics consent on such pages and removes PulseTrack identifiers left by an older tracker. The server already refused to record these visits.
  • After updating, clear your page cache and CDN cache. A tracker file that a CDN still caches from an older version cannot be changed by a plugin update. On sites set to “Not required on this site”, pages cached before 1.4 record nothing until the cache is cleared.

1.4.0

  • Privacy fix: PulseTrack now waits for visitor consent. It follows the WP Consent API and records a visitor only after Statistics consent is recorded by your consent banner. Before that it creates no identifier, writes nothing to the browser and stores nothing, in the browser and on the server, including WooCommerce cart and purchase events.
  • Added: consent withdrawal stops tracking immediately, discards unsent events and removes PulseTrack’s browser storage and cookie. Works with page caching.
  • Added: Settings › Privacy › Visitor Consent, with the current status, and a Dashboard notice when no consent integration is active.
  • Changed: on sites without WP Consent API, PulseTrack records nothing until you install it with a consent banner plugin or choose “Not required on this site”. Existing data is kept.

1.3.0

  • Changed: days in reports are now your site’s local days (the timezone set in WordPress), including exports. Earlier data keeps its original UTC days. The developer interface is now version 2 and describes this through AggregateReader::semantics().
  • Fixed: after an update from an older release, missing or mismatched database tables are repaired automatically. Mismatched tables are renamed, never deleted, and tracking reports failures honestly instead of answering OK.
  • Fixed: quick leads that happen within seconds of a page view are now included in time to lead.
  • Fixed: visits to pages served from a page cache for more than about a day are tracked again. Pages for visitors who are not logged in no longer carry a WordPress security token that expires inside the cache.
  • Fixed: a slow server response can no longer store the same visit twice. Events that could not be sent because of a network error are sent once more with the next batch.
  • Changed: bounce rate counts a session with a single page view and no lead. Session duration is labelled as active session duration.
  • Changed: WooCommerce orders count once, only when processing or completed. Orders in another currency are counted but not added to order value. Orders without a PulseTrack cookie no longer create a direct session.
  • Changed: traffic sources use one set of types (organic, paid, social, direct, referral, email, AI, unknown) on every screen and export.
  • Added: choose a store or lead-generation view in Settings. Dashboard, exports and PDF use the same columns.
  • Added: clear notices when the database or tracking needs attention, and an Unavailable state instead of zeros when a report cannot be read.

1.2.0

  • Added: the read-only developer interface now also reports when all data was last deleted (AggregateReader::resetState()), so add-ons that keep their own summaries can honor “Delete All Data” even if they were inactive at the time. It exposes a counter and a date only, and sends nothing off your site.
  • No change to what is tracked, the admin screens, or data retention settings.

1.1.0

  • Fixed: when background processing fell far behind, the daily cleanup could remove raw data that the analytics summaries still needed, which could lower the 60/90-day figures for up to three affected dates. Raw data is now kept until every summary that depends on it is final.
  • Added: a read-only developer interface for finalized daily summaries (the PulseTrack\API\AggregateReader class, the pulsetrack_aggregate_date_finalized and pulsetrack_all_data_deleted actions, and the PULSETRACK_API_VERSION constant). It exposes aggregate counts only, never visitor-level data, and sends nothing off your site.
  • No change to what is tracked, the admin screens, or data retention settings.

1.0.1

  • Added WordPress.org directory branding assets (plugin icon and banner).
  • Updated directory Tags and description copy for accuracy and discoverability. No functional or behavior changes.

1.0.0

  • Initial release.