Connected venue intelligence

Your venue is a sleeping giant.

Start a movement See it run
  1. 01ArrivalLocation ping, network detection
  2. 02EntryTicket scan, credential, network auth
  3. 03HospitalityPremium access, dwell, spend
  4. 04ActivationSponsor zone visit, engagement time
  5. 05TransactionFood, beverage, merchandise
  6. 06ExitDeparture time, return likelihood

Every night, the building is taking notes.

Identity signals

  • Ticketing & credentialing
  • Network authentication
  • App usage & registration
  • CRM & marketing records

Behavioral signals

  • Location & dwell time
  • Entry, exit & movement
  • Zone engagement
  • Queue exposure

Transaction signals

  • Food & beverage
  • Merchandise
  • Premium hospitality
  • Sponsor activation

A signal is worth nothing until it has a name on it.

Step it.

Depth of resolution

It joins the fan record, carrying everything the building watched it do.

The record, as it stands Worked example

  • Device 7F3A
  • Fan zone · 34 min
  • Merchandise zone · visited
  • Saturday GA ticket
  • Network authenticated
  • Merchandise · purchased
  • Weekend attendee
  • $342 across three days
  • 2 premium visits
  • 3 sponsor engagements
  • High premium propensity

Resolving a signal to a person requires that person to authenticate. Device detection on its own identifies nobody, and the layer is built so that it cannot.

Move through a matchday. Watch it notice.

Occupancy is the fill. The bar under a stand is the queue.

Point in the matchday
Gate NGate N58%Concessions 11211212%Queue 2 minMerchandiseMerch30%Premium clubClub20%SponsorSponsor16%Gate SGate S50%Concessions 11811810%Queue 1 minFan zoneFan zone34%
Zone occupancy at Gates open
ZoneOccupancyQueue
Gate north58%n/a
Concessions 11212%2 min
Merchandise30%n/a
Premium club20%n/a
Sponsor activation16%n/a
Gate south50%n/a
Concessions 11810%1 min
Fan zone34%n/a
4,200On site
1,600 resolved to a person
Heaviest zone
Gate north
Longest queue
Concessions 112, 2 min
Fan friction index lower is better
4

Reading

  • Longest queue 2 min, inside tolerance
  • Heaviest zone gate north
  • No threshold crossed

Nothing worth interrupting a fan for

Illustrative. Occupancy and queue depth are authored to behave the way a matchday behaves, not measured in anyone's building.

What it sends, and how it picks who gets it

Signal to revenue, inside the event window.

  1. 01Read signal
  2. 02Qualify audience
  3. 03Choose action
  4. 04Send offer
  5. 05Capture revenue

The building generates the signal either way — but what are you doing about it?

Start a movement