Telemetry SDK
Know exactly how your plugin lives in the wild.
Nine signals across versions, environments and why people leave — reported by the sites that opt in, from inside your own plugin.
Benefits
What you actually learn
Beyond active-install estimates, down to the install level.
Version & environment
Stop guessing which stacks you have to support. Every opted-in install reports its full environment, so raising a minimum requirement becomes a decision instead of a gamble.
- Plugin version usageWhich version of your plugin real installs are running, so you know when legacy support can go.
- WordPress version usageThe real core-version spread across your installed base — not a directory guess.
- PHP version usageSee the actual PHP landscape before you bump a minimum and break sites.
- Server software mixApache, Nginx, LiteSpeed — know which stacks your plugin has to behave on.
Why people leave
The uninstall is the most honest moment in your plugin’s life, and the directory throws it away. We capture it — before it becomes a one-star review.
- Deactivation reasonsA preset reason plus open text, collected the moment someone deactivates.
- Sites reportingA live count of opted-in installations sending data, independent of install buckets.
Your own instrumentation
Beyond the standard signals, measure the features you actually care about — in the languages and network setups your users really run, and never without permission.
- Custom feature eventsOpt in named events for the features you want usage data on — nothing else.
- Multisite & locale mixUnderstand where and how your plugin is used, across languages and network installs.
- Consent-first by designNothing is sent until the site owner explicitly opts in, and feedback never blocks uninstall.
Why it matters
Decisions you can finally make with evidence
Drop legacy support with confidence
Stop guessing whether anyone still runs PHP 7.2. See the real share before you raise your minimum requirement and field the angry tickets.
Catch a bad release in hours
A version that stops reporting, or a spike in "it stopped working after an update" deactivations, tells you a release went wrong long before the reviews do.
Build what people actually use
Custom feature events show which parts of your plugin get touched — and which ones you can retire instead of maintaining forever.
Turn churn into a roadmap
Deactivation reasons, sorted by frequency, are the cheapest product research you will ever get.
Setup
Live in an afternoon
Enable a project
Turn on telemetry for your plugin from its dashboard and get a public key.
Drop in the SDK
A few lines of PHP, no dependencies. Consent handling is built in.
Site owners opt in
The SDK asks explicit permission before it ever sends a byte.
See real data
Version adoption, environment mix, and deactivation reasons, updated daily.
Two collection points
Where the data actually comes from
Two lightweight touchpoints inside your plugin — both opt-in, both dismissible.
1 · Admin notice
The opt-in prompt
A single dismissible admin notice asks the site owner to share environment data. Decline and nothing is ever sent — the notice does not reappear.
- WordPress version
- 6.8.1
- Server software
- nginx/1.24.0
- PHP version
- 8.2.14
- Your plugin version
- 6.4.1
- Other active plugins
- 12 detected
2 · Deactivation popup
The exit interview
When someone deactivates, a short popup asks why — a preset reason plus an open text box. It’s skippable, and it never delays the deactivation.
- I only needed it temporarily
- I found a better plugin
- It stopped working after an update
- It slowed down my site
- I couldn’t get it to work
- Other — tell us more
You decide how much is collected
Toggle each data point on or off per project — collect only the plugin version, or the full environment picture. Site owners see exactly what your notice requests before they agree, and you can narrow the scope any time without shipping a plugin update.
Advanced dashboard
One dashboard for every environment signal
- Version adoption charts — plugin, WordPress, and PHP versions over time
- Deactivation-reason breakdown with free-text voluntary feedback
- Reporting-installations trend, independent of directory estimates
- Multisite and locale distribution
- Custom event funnel for the features you instrument
- CSV export and per-project data deletion
Built consent-first
Nothing moves without explicit, site-owner opt-in.
We collect (opt-in only)
- Anonymous install ID
- Site address — with deactivation feedback only, never in the anonymous stream
- Your plugin’s version
- WordPress core version
- PHP version
- Server software (Apache / Nginx)
- Other active plugins on the site
- Locale & multisite flag
- Opted-in custom feature events
- Voluntary deactivation feedback
We never collect
- Admin or customer email addresses
- IP addresses
- Customer or order data
- Passwords or credentials
- Raw server logs
- Frontend visitor behavior
Metering
You see the meter before it bites
Telemetry is metered by reporting installations and by events, and your usage against those limits is on the dashboard from the first day — nothing is ever silently rejected because a number moved while you were not looking.
See pricingTelemetry FAQ
Is telemetry required to use PluginTracker?
No. It is opt-in twice over — you decide whether to ship the SDK at all, and each of your users decides whether to send anything. Everything else on PluginTracker works without it.
Does the SDK slow down my plugin or the sites running it?
No. Events are batched and sent asynchronously over HTTPS, and the SDK never blocks page rendering or plugin activation.
What if a site owner doesn’t opt in?
Nothing is sent. The SDK checks for explicit opt-in before every request, and the deactivation survey is dismissible and never delays uninstall.
Can I revoke access later?
Yes. Rotate or revoke your project key any time — revocation blocks new ingestion immediately, and your existing data stays until you delete it.
How long is data kept?
Raw events are retained for 90 days. Aggregated daily metrics are kept until you delete the project or your account.