📈 Demo usage insights

When a site is running in demo mode, Pavilion sends anonymous, non-blocking usage insights back to the Keen2Support hub so you can see who is trying your public demo and which features they explore. It appears on the hub under Keen2Support → Usage. This is for the live marketing demo only — it never runs on a real club’s installation.

What the hub shows you

• Who’s here now — for visitors who opt in, their name and email (given at the demo login); the screen they are on, how long they have been there, and a rough location. Visitors who don’t tick the opt-in box still appear, but anonymously — their screen activity is shown without a name or email.
• Logins by day of week — a simple bar per weekday, so you can see when interest peaks.
• Most-used screens and a full per-visitor trail of the screens they opened.

How it works

The demo login asks each visitor for their name and email, with a short consent line, before entering the sandbox. Pavilion reuses the same connection it already uses for support tickets to send that, plus the feature each visitor opens and a lightweight “still here” beat while they read a page. Everything is sent in the background on shutdown, so the demo never waits on the hub and pages are never delayed.

Turning it on

There is nothing to switch on. Usage insights are automatic on any site running in demo mode (define( 'PVL_DEMO_MODE', true );) once that site is linked to the hub — which happens by itself on the first admin visit. A normal club install sends nothing.

Requires Keen2Support v0.84.0+ on the hub (the version that adds the Usage screen and the stats endpoint).

Common questions

Does a real club installation send usage data?

No. Usage insights only turn on when the site is running in demo mode (PVL_DEMO_MODE). A live club install never phones home usage — only its own support tickets, which is unchanged.

What exactly is collected?

The name and email the visitor types at the demo gate, the Pavilion screens they open, and their login day/time. The hub also records IP for a rough location. Nothing else, and never anything a visitor edits inside the sandbox.

How long is it kept?

The hub prunes all usage stats after a retention window (90 days by default). You can adjust that on the hub side.

What if a visitor does not give a name/email?

Then Pavilion does not identify them — they simply appear as an anonymous short id until (and unless) they complete the gate. The demo still works exactly as before.

Will this slow the demo down?

No. Every send is non-blocking and happens after the page has finished, so a slow or unreachable hub never affects the visitor’s experience.