ModuleFest
Sign in

Demo usage insights

Last updated September 21, 2026

On the public demo only, Pet Central can report how visitors explore it back to the ModuleFest Hub, so the hub’s Usage screen shows who is here now, which features they open, and logins by day of week. This is telemetry for the shop-window demo — it is never active on a real customer install, which sends nothing.

A short name + email + consent box on the demo login is the linchpin: it lets the hub show the real person instead of “Demo User”. Each screen a visitor opens is sent as its feature key (dashboard, clients, bookings, groomer / walker / sitter, and so on), so the Usage heatmap lines up with what each licence tier and service unlocks. Nothing sensitive is collected, and details are pruned after about 90 days.

1
Visitor opens the demoThey enter a name, email and tick the consent box.
2
Session is identifiedThe hub attributes this session to that person.
3
They click aroundEach feature they open is recorded as a screen view.
4
You review on the hubModuleFest Hub → Usage shows who’s here, most-used screens and logins by weekday.

Example

Before a busy week of demo traffic you glance at ModuleFest Hub → Usage: three prospects are exploring right now, the Walker and Sitter areas are the most-opened, and logins cluster on weekday evenings — so you know where interest really is.

FAQ

Does this run on my customers’ sites?
No. Telemetry is only ever on when a site is put into demo mode (PC_DEMO_MODE). Every real install is completely silent and sends nothing.

What is collected?
Only the name and email a visitor types at the demo gate, the screens they open, and rough location/time — used to show activity on the hub and pruned after about 90 days. It isn’t added to any marketing list.

Which hub version do I need?
ModuleFest Hub 1.0.0 or later, which adds the Usage screen and the ingest endpoint. The demo links to the hub automatically on activation.

The Usage screen is empty — what should I check?
First confirm the demo is linked to the hub and running v0.84.0+. Usage is sent non-blocking, so a failed send never surfaces on the demo itself — to see what is happening, switch on diagnostics: add define( ‘PC_STATS_DEBUG’, true ) to wp-config.php (or the pc_stats_debug filter), reload a demo admin screen, then read wp-content/debug.log. You will see either “K2S stats: flush -> HTTP 200 (N events)” on success, the exact reason it was skipped (site not linked, or nothing buffered this request), or the hub’s error code and message if it rejected the payload. Turn the flag off again when done.

It was working, now the hub rejects everything with 401
That means this site’s hub token was invalidated — for example the hub rotated it. Pet Central heals this itself: on a 401 it re-links once via the product key to rotate a fresh token and retries. The usage-stats flush recovers on its own within a few minutes on a busy demo — no action needed. To fix it instantly, open Pet Central → Support and click Link now. (If the re-link itself fails, the product key or the hub-side product record is the thing to check.)