PulseTrack – Analytics & Conversion Tracking

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.

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 this use cookies?

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. You can disable cookies entirely under PulseTrack › Settings › Session Tracking; sessions still work, they are simply not persisted across page loads.

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 privacy-safe aggregated summaries (counts and totals, not individual visitor records) 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. 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 anonymous by design (no 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 intentionally anonymous 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.