Dashboard

DEMO DATA
Working prototype: analytics use generated historical data so you can test the interface. Venue changes are saved in your browser. The deployment package includes a Cloudflare D1 schema and Ticket Tailor sync Worker scaffold for live data.

How is PoK performing?

A commercial overview of ticket revenue, attendance, venue performance and audience behaviour.

Revenue & ticket trend

Monthly performance across historical events

Sales by region

Share of total ticket revenue

Top venues

Ranked using a blended PoK Venue Score

Acquisition

Demo referral attribution

Events

Compare sell-through, sales velocity, revenue and attendance event by event.

DateEventVenueTopicSoldSell-throughChecked inRevenueLast 7d

Venues

This becomes your master venue database. Add a venue once and the public map plus analytics can use the same record.

Sales hotspots

See where customers are coming from by outward postcode. Larger circles represent more buyers.

Top buyer postcodes

Aggregated outward codes only

Speakers & topics

Understand which speakers and subject areas consistently generate demand.

Speaker performance

Average sales and revenue per event
SpeakerEventsAvg soldAvg revenueAvg attendance

Topic demand

Average tickets sold per event

Audience

A privacy-conscious customer view. The live version can hash email addresses for repeat-customer analysis and retain only aggregated postcodes for geography.

Estimated repeat rate
31%
Demo metric
Avg events / customer
1.46
Demo metric
Top outward postcode
SW18
438 buyers
Newsletter attributed
0
Demo referral data

Recommended privacy model

Store a one-way hash of customer email for repeat-purchase analysis, not readable email addresses in the reporting layer. Keep outward postcode such as SW18 rather than full postal addresses for hotspot reporting. Raw Ticket Tailor data can be kept out of the dashboard database unless operationally required.

Questions this can answer

Which areas are growing? How far do customers travel? Which venues pull the most local audiences? Do newsletters bring back existing customers? Which topics bring in first-time attendees? Which venues have the strongest repeat attendance?

Settings & integration

The production version will sync Ticket Tailor into Cloudflare D1 and expose only safe reporting endpoints to the dashboard.

Ticket Tailor

Status: Not connected in prototype. The Worker scaffold uses Basic Auth with an API key stored as a Cloudflare secret.

wrangler secret put TICKET_TAILOR_API_KEY

Cloudflare D1

Database tables are included for venues, events, orders, ticket facts, postcode aggregates, speakers and topics.

wrangler d1 execute pok-analytics --file=schema.sql --remote

Sync design

Initial backfill fetches historical events, orders, issued tickets and check-ins. Afterwards you can run scheduled incremental syncs and add Ticket Tailor webhooks.

Admin security

This local HTML prototype has no login. Before going live, protect the admin route with Cloudflare Access or another authentication layer. The public venue map remains public.