Skip to Content
Getting StartedWelcome

Welcome to Appneck Plugin Analytics

What is this, in plain English?

You’ve built a WordPress plugin. Once it’s out in the world, you’re mostly blind to how it’s doing — you don’t know how many sites have it active, which versions people run, what PHP/WordPress versions they’re on, why people leave, or which features actually get used.

Appneck Plugin Analytics answers those questions. You add a small PHP package — the SDK (Software Development Kit, a ready-made toolbox of code) — to your plugin. From then on, your plugin privately reports simple, non-personal signals back to Appneck, which turns them into dashboards you can read.

The three things you’ll set up

  1. An Organization — your company’s workspace inside Appneck.
  2. A Product — one specific plugin of yours (e.g. “WpEvently”). Each Product gets its own key + secret.
  3. The SDK — the package you add to your plugin, bootstrapped with that key + secret, which does the actual reporting.

Is this safe / private for my users?

Yes, by design:

  • Nothing is collected until the site owner consents. The SDK shows a consent prompt automatically and won’t send telemetry until they accept.
  • What’s collected is technical, not personal — PHP version, plugin version, feature-usage counts. Never customer names, emails, or site content.

A note on how the SDK is actually called

Throughout these docs you’ll use the real SDK entry point:

$sdk = \Appneck\Sdk\Sdk::bootstrap( /* key, secret, url, file */ );

bootstrap() returns an object ($sdk) that you keep and call methods on. There is no Appneck::init() — if you see that anywhere, it’s outdated.

Next: Quick Start →