Description
OpenRevenue is a simpler, privacy-friendly alternative to Google Analytics with realtime insights, performance metrics, funnels and shareable public stats.
This plugin connects your WordPress site to your OpenRevenue account. Enter the Project ID from your OpenRevenue dashboard, save, and the lightweight tracking script is automatically added to every page — no theme editing required.
Features
- One-field setup — just paste your Project ID and save.
- Lightweight, deferred tracking script that does not slow your site down.
- Storage-free by default: no cookies and nothing stored in the visitor’s browser.
- Optional visitor storage setting: keep a visitor ID only after consent from your cookie banner, or always.
- Optionally exclude logged-in staff (administrators, editors, authors, contributors) so your own visits do not inflate your stats.
- “Verify connection” button to confirm the tracker can be reached from your site.
- Clean, privacy-focused analytics without the bloat of traditional tools.
You will need an OpenRevenue account and a project. Create one for free at https://www.openrevenue.com.
External services
This plugin relies on OpenRevenue, a third-party analytics service, to collect and display your site’s analytics. Your site will not send any data to OpenRevenue until you enter a Project ID and save the settings.
1. Loading the tracker script (front end)
Once a Project ID is saved, the plugin loads the OpenRevenue tracking script (https://api.openrevenue.com/tracker.js) on your site’s public pages. When a visitor loads a page, the script sends analytics data to https://api.openrevenue.com/api/track, including: page URL and referrer, browser, operating system, device type, approximate country/region/city (derived from IP at the time of the request and not stored as a raw IP), an anonymous visitor/session identifier, time on page, and basic performance (web vitals) metrics. The script sets no cookies and stores nothing in the visitor’s browser. To count unique visitors, OpenRevenue makes a daily identifier on its servers from a secret salt that is deleted every day, the site’s project ID, a shortened IP address and the browser’s user agent; raw IP addresses are not stored. Mention OpenRevenue in your privacy policy.
If you change the “Visitor storage” setting, the script can also keep a randomly generated visitor ID in the visitor’s browser (a first-party cookie and local storage) so returning visitors are recognised across days. With “Store a visitor ID after consent”, this only happens after your cookie banner calls window.openrevenue.consent(true); with “Always store a visitor ID”, it happens on every visit. Depending on your jurisdiction you may need the visitor’s consent for these options.
2. Verifying the connection (admin only)
When you click the “Verify connection” button on the plugin settings page, your site makes a single server-side request to https://api.openrevenue.com/tracker.js to confirm the tracker is reachable. No personal data is sent in this request.
By using this plugin you are sending data to OpenRevenue. Please review:
- OpenRevenue website: https://www.openrevenue.com
- Privacy policy: https://www.openrevenue.com/privacy
- Terms of service: https://www.openrevenue.com/terms
Installation
- Upload the
openrevenuefolder to the/wp-content/plugins/directory, or install the plugin through the WordPress plugins screen directly. - Activate the plugin through the “Plugins” screen in WordPress.
- Click OpenRevenue in the left-hand admin menu.
- Paste your Project ID from your OpenRevenue dashboard (https://www.openrevenue.com/dashboard) and click Save Settings.
- (Optional) Click Verify connection to confirm the tracker is reachable.
- Visit your site in a logged-out browser, then open Realtime in your OpenRevenue dashboard to see traffic.
FAQ
Do I need an OpenRevenue account?
Yes. This plugin connects an existing OpenRevenue project to your WordPress site. You can create an account and a project at https://www.openrevenue.com.
Where do I find my Project ID?
Open your OpenRevenue dashboard, select the project you want to track, and copy its Project ID (the same value used in the data-site attribute of the tracking snippet).
My own visits are showing up in the stats.
Enable the “Exclude staff” option on the settings page (on by default). It stops the tracker from loading for logged-in users who can edit content.
Do I need a cookie banner for OpenRevenue?
With the default “Don’t store anything” setting, the tracker sets no cookies and stores nothing in the visitor’s browser, so in most setups OpenRevenue needs no cookie banner. You still need to mention OpenRevenue in your privacy policy. This is not legal advice.
How do I recognise returning visitors with my cookie banner?
Set “Visitor storage” to “Store a visitor ID after consent”. Then make your cookie banner call window.openrevenue.consent(true) when the visitor accepts analytics cookies, and window.openrevenue.consent(false) when they decline or withdraw consent. Until consent(true) is called, nothing is stored. See https://docs.openrevenue.com/advanced/cookies-and-consent.
Does this work with caching plugins?
Yes. The tracker is a standard deferred script tag added to the page, so it is compatible with full-page caching.
Can I point the tracker at a custom/self-hosted domain?
Yes, developers can change the script URL with the openrevenue_script_src filter.
Screenshots
Changelog
1.1.1
- The documentation links on the settings page now go straight to docs.openrevenue.com.
1.1.0
- New “Visitor storage” setting for the tracker’s
data-persistattribute: don’t store anything (default), store a visitor ID after consent from your cookie banner, or always store a visitor ID. - The tracker is now storage-free by default: no cookies or local storage. Choose “Always store a visitor ID” to keep the previous behaviour.
1.0.1
- Initial public release of the OpenRevenue WordPress plugin.
- Paste your Project ID to load the tracker from
https://api.openrevenue.com/tracker.js. - Exclude logged-in staff from tracking (on by default).
- Verify connection from the settings screen.
- Top-level admin menu with connection-status badge and settings UI.


