Parking lot analytics in real time, by channel, with attribution

Almost every operator we've onboarded started by complaining about visibility. Their previous platform shipped a quarterly PDF. Their meter vendor sent a monthly spreadsheet that didn't reconcile to the bank. Their permit system lived in a separate tool. Their AI-agent integrations — when they had any — produced no data they could see.

Real-time analytics is the foundation that makes every other Park Graph capability useful. Dynamic pricing without real-time occupancy is guesswork. AI-agent discoverability without per-agent attribution is invisible. Forecasting without historical data is fantasy. The dashboard is the place where every Park Graph signal becomes legible.

The dashboard preview above is a snapshot of the real interface. Tiles include revenue (gross + net + per-channel), occupancy (current + 24-hour spark + 7-day forecast), session count, AI-agent activity, refund rate, and lot health. Operators can pin custom tiles and rearrange the layout. The same view is available on mobile for on-the-go checks.

Park Graph models every paid session as belonging to one of five channels: transient QR scans (the default — driver arrives, scans, pays); reservations (driver booked in advance); permits (recurring monthly billing); validations (a third party — restaurant, hotel, hospital — comped or discounted the session); AI-agent bookings (an agent reserved on the driver's behalf).

Channel attribution lets operators see where revenue is concentrated, where pricing power lives, and where to invest in driver experience. A lot that is 80% transient and 20% AI-agent is a different business than a lot that is 60% permit and 30% reservation, even at the same gross revenue.

1. 1

   Sign up

   ~2 min

   Free Starter plan.

2. 2

   Create the lot, start collecting payments

   ~15 min

   Standard onboarding.

3. 3

   Open the dashboard

   ~0 min

   Real-time tiles populate as sessions come in.

4. 4

   Configure rollups + tags

   ~10 min

   Multi-lot operators tag lots by region or manager for grouped reporting.

5. 5

   Connect webhooks (optional)

   ~30 min

   Pipe events into your warehouse with the OpenAPI-typed payload.

6. 6

   Schedule the executive PDF

   ~5 min

   Weekly or monthly auto-emailed snapshot.

Most legacy parking platforms ship a monthly PDF — sometimes weekly, occasionally quarterly — that arrives long after any decision could have been informed by it. The PDF is hard to compare year-over-year, impossible to drill into, and disconnected from the bank statement that shows whether the operator was actually paid the right amount. Park Graph exists in part to retire that workflow.

The replacement is simple in principle: every event the platform sees becomes a row in a queryable table within seconds, and every row is reachable from the dashboard, the API, and the warehouse export at the same time. CFOs read the dashboard during the board meeting; analysts pull the API into Looker before the board meeting; and the controller reconciles the bank export against the daily payout file the morning after. No one waits on a PDF.

Operators on Park Graph analytics report a measurable shift in pricing cadence within the first quarter of switching. Rate reviews move from quarterly to monthly, surge rules get tuned weekly, and abandoned-payment investigations move from anecdote to a tracked funnel. The data was always there; what changes is the speed at which the operator can act on it.