PulseTrack Ìtumọ̀ Yorùbá: – Analytics & Conversion Tracking

Àpèjúwe

See which traffic sources bring leads and orders Ìtumọ̀ Yorùbá: – not just pageviews.

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

Key Features

  • Conversion tracking for WordPress Ìtumọ̀ Yorùbá: – form submits, phone clicks, WhatsApp, and email leads
  • Traffic source attribution Ìtumọ̀ Yorùbá: – search, social, AI referrals, UTM campaigns, direct
  • Privacy-first analytics Ìtumọ̀ Yorùbá: – IP anonymization on by default, no third-party data sharing
  • Dashboard Ìtumọ̀ Yorùbá: – sessions, users, leads, lead rate, traffic sources, campaigns, device/browser breakdown; a store view shows orders and order value instead
  • Sessions and users Ìtumọ̀ Yorùbá: – accurate counts using fingerprinting, no inflated data
  • Visitor Logs Ìtumọ̀ Yorùbá: – per-session activity timeline (time, page, event, source, device)
  • Insights Ìtumọ̀ Yorùbá: – automatically scores your most-visited pages and flags priority pages to fix and quick-win opportunities
  • Export reports Ìtumọ̀ Yorùbá: – CSV, JSON, and PDF (browser-print report), covering the same data shown on the Dashboard
  • WooCommerce analytics (optional) Ìtumọ̀ Yorùbá: – 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 Ìtumọ̀ Yorùbá: – registers with the built-in personal data export/erase tools and privacy policy content
  • Guided first-time setup Ìtumọ̀ Yorùbá: – 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 Ìtumọ̀ Yorùbá: – 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.

Àwọn àwòrán ìbòjú

Ìgbéwọlẹ̀

  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.

FAQ

Is this a Google Analytics alternative?

Yes. PulseTrack stores all data on your own WordPress server Ìtumọ̀ Yorùbá: – 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 Ìtumọ̀ Yorùbá: – never a visitorÌtumọ̀ Yorùbá: ’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Ìtumọ̀ Yorùbá: ’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 Ìtumọ̀ Yorùbá: – there is no separate tier or upgrade required to see it.

Does WordPressÌtumọ̀ Yorùbá: ’s built-in privacy export/erase tools work with PulseTrack?

Yes, PulseTrack registers with WordPressÌtumọ̀ Yorùbá: ’s personal data exporter and eraser. In practice, PulseTrackÌtumọ̀ Yorùbá: ’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 Ìtumọ̀ Yorùbá: – 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.

Àwọn àgbéyẹ̀wò

Kò sí àwọn àgbéyẹ̀wò fún plugin yìí.

Àwọn Olùkópa & Olùgbéejáde

“PulseTrack Ìtumọ̀ Yorùbá: – Analytics & Conversion Tracking” jẹ́ ètò ìṣàmúlò orísun ṣíṣí sílẹ̀. Àwọn ènìyàn wọ̀nyí ti ṣe ìkópa sí plugin yìí.

Àwọn Olùkópa

Àkọsílẹ̀ àwọn àyípadà

1.3.0

  • Changed: days in reports are now your siteÌtumọ̀ Yorùbá: ’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.