🏢 GameView Armada Enterprise

One chain. Every screen.
One console.

A management tier that sits above your stores. Write a schedule once and it lands on every screen in the group — each one on that store's own local clock. Put DIRECTV® on every screen over satellite, so the picture never depends on the broadband link that just failed. Then sell the whole estate as one buy, and measure it store by store.

Corporate above franchisee accounts Every store on its own clock Audience counted, not modelled
BP-00

The chain

Chain console one login, every store Gulf Coast Fuel 4 stores · 8 screens Midway Convenience 3 stores · 6 screens Company Owned 3 stores · 6 screens 10 STORES · 20 SCREENS · ONE SCHEDULE, ONE REPORT
Chain scope Ownership Store
1
schedule written — fanned out to every store in the group, in each one's local time
2
networks per screen, on purpose: a private link to the receiver, Wi‑Fi to the cloud
0
subnets to plan — every StreamBridge™ is 192.168.1.10, in every store
1:1
coupon code to store, per creative — so a scan tells you which store it came from
Centralized management

Write it once. It lands everywhere.

Most chains run their screens the way they ran them before they were a chain — one manager, one store, one afternoon. Enterprise puts a tier above the accounts you already have, so corporate reaches every store without taking anything away from the people who run them.

🗓️

Chain scheduling, on local clocks

Set the Sunday board for 11:00 and it plays at 11:00 in Tampa and 11:00 in Denver. Every store carries its own timezone, and a store missing one is flagged before anything is written — not discovered three weeks later when its evenings were running on the wrong day.

👥

Groups with real privileges

Group stores by owner, region or format, and give each person view, schedule, control, report or manage on that group alone. A store manager who has not been placed in a group keeps their own store exactly as they had it — the feature restricts, it never quietly locks people out.

📊

Roll-up that names the gaps

What played, where, and what didn't. A store that reported nothing appears as not reported rather than as a zero, because a chain-wide average quietly padded with ninety silent stores is worse than no number.

gameviewmanager.com/account_manager
Chain
Ad Buys
Locations
Schedule
Reports

Chain schedule — Sunday board

Applies to Gulf Coast Fuel · 4 stores · 8 screens

PreflightStoresHistory
8
Screens
280
Screen-days
4
Timezones
Store #1934 — Bay Pines
America/New_York · 11:00 local
Ready
Store #1937 — Cherry Creek
America/Denver · 11:00 local
Ready
Store #1940 — Kapolei
⚠ No timezone set — would run on a fallback clock
Fix first
Apply to 4 stores Review

Preflight runs before anything is written. Chain-scale failures are invisible one store at a time.

Why DIRECTV®, at scale

The game arrives from the sky.
Not from your ISP.

Every streaming source in your store shares one pipe with the POS, the card reader, the cameras and the guest Wi‑Fi. Satellite doesn't. The picture on the wall takes a path that has nothing to do with the circuit your other vendors are fighting over.

It matters most on the day something breaks. When the link drops, a chain on streaming goes black in every store at once. On Armada, the receiver keeps feeding the screen — you lose the ability to change it from the cloud, not the picture itself. Control comes back when the link does.

Separate paths

Programming over satellite, control over Wi‑Fi. A failure in one is not a failure in the other.

One shared gateway

We have watched a dozen restaurants across seven states drop off in the same second — one SD‑WAN gateway, not a dozen outages.

Commercial lineup

The out-of-market and regional sports packages a public venue is actually licensed to show, on every screen in the chain.

Known hardware

Receivers whose control path we already model per unit — H25, HR54, C61 — so a channel change is a command, not a guess.

Mini blueprints

The same install, in every store.

A four or five screen build is the c-store standard, and it is deliberately the dullest possible wiring: each TV gets its own DIRECTV® receiver plugged straight into its own StreamBridge™, and Wi‑Fi carries control and artwork to all of them. No head-end rack, no matrix, no site survey — and no two stores wired differently.

BP-01

The store — five screens, point to point

typical c-store build
GameView cloud one console Store Wi-Fi FIVE SCREENS · FIVE RECEIVERS · NO SHARED LAN DIRECTV® receiver · .100 StreamBridge™ 192.168.1.10 TV 1 DIRECTV® receiver · .100 StreamBridge™ 192.168.1.10 TV 2 DIRECTV® receiver · .100 StreamBridge™ 192.168.1.10 TV 3 DIRECTV® receiver · .100 StreamBridge™ 192.168.1.10 TV 4 DIRECTV® receiver · .100 StreamBridge™ 192.168.1.10 TV 5
HDMI — picture LAN — receiver control Wi‑Fi — cloud, schedule, artwork Screen 5 dashed — a four-screen store is this drawing, minus one row
StreamBridge NIC
192.168.1.10 / 24
Receiver
192.168.1.100
Cloud path
Wi-Fi · venue DHCP
Per-site IP planning
none

The two addresses are identical in every store and on every box — that is the normalization. An installer never has to think about a subnet, and a receiver's identity is the pair (box serial, ip), not the address, so ten receivers on ten boxes never collapse into one.

BP-02

One screen, in detail

Store Wi-Fi → GameView cloud DIRECTV® Receiver H25 · HR54 · C61 192.168.1.100 HDMI · picture LAN · control StreamBridge™ by GameView 192.168.1.10 wired NIC · every box HDMI TV ONE PAIR PER SCREEN
HDMI LAN Wi‑Fi

Two networks, on purpose. The receiver link is private to this box — it is not a route to anywhere — and the cloud arrives separately over Wi‑Fi. Neither one can take the other down.

BP-03

What rides the Wi-Fi

GameView cloud one console, every store Display schedule Tapestry artwork DIRECTV® channel Ad placement + coupon code What actually played Check-in + box health Coupon scans, per store Occupancy ≈ people StreamBridge™ at every screen
Down — control & artwork Up — measurement

Artwork is distributed, not streamed: each box holds its own tapestry and plays it locally, so a slow night on the venue's Wi‑Fi shows up as a late update, never as a stutter on the wall.

Measured audience

Top dollar needs a number
somebody can check.

Every place-based network sells "potential viewers" — capacity times a foot-traffic model, bought from a panel that has never been inside your stores. It is the reason chain screen inventory is priced like a guess. An Armada store counts the room instead: a small appliance on the store network measures how many people are actually in front of the screens, every hour, in every location.

BP-04

Where the count comes from

one appliance per store
THE STORE FLOOR Data Master · calibrated radius Counts. Nothing else. identifiers hashed on the box, salt rotates daily GameView cloud hour by hour, screen by screen, kept in-room devices ÷ 1.8 ≈ people
Measured coverage Screen Calibrated range

The appliance already lives on the store network for control and diagnostics. Counting is a server-side toggle per box — nothing is installed in the store to turn a location into a measured one.

📶

Counted, not modelled

The appliance listens passively for the Wi-Fi radios people already carry and counts the unique ones close enough to be in the room — not everything the antenna can hear from the parking lot.

🔒

Nobody is identified

Device identifiers are hashed on the box with a salt that rotates daily and is never written down or sent anywhere. Only per-window counts leave the store. No cameras, no faces, no app, nothing to opt into.

🎯

Calibrated per store

One phone advertises itself under several rotating identities; those are merged before anything is counted. Then in-room devices are divided by a devices-per-person figure you tune per venue, and the store's overnight equipment is learned and reported separately rather than sold as customers.

📈

Reportable

Hour by hour, a day-by-hour pattern for every store, peaks, and the whole history kept — in each store's own local time. It is the same measurement the buy report quotes and the same one your own floor reports use.

This is what a rate card is worth arguing about. A buyer pricing your estate against the rest of the place-based market is comparing your number to a modelled one. Measured hours, per store, with a method you can describe in a sentence, is the difference between defending a rate and discounting to close.
And it is believable because it refuses to fill gaps. A store without measurement reports not measured — never 0, never the chain average quietly standing in for it. An estate that admits which stores it cannot speak for is the only kind whose totals survive being checked.
Enterprise ad buys

One advertiser. One budget.
Three hundred stores.

A national brand does not want three hundred campaigns. They want a buy — a budget spread across the estate, creative they control, and an answer at the end. So a buy sits above campaigns the same way the chain sits above stores.

Buy — “Coca-Cola Summer 2026”

$1,000,000

The commercial agreement. One advertiser, one budget, one report.

Flight → a store group

40% · 25% · 35%

A share of the budget aimed at a group of stores, over a date range and a daypart.

Placement — store, screen, variant

written once

The unit that gets measured. It carries what was promised — showings, seconds, value, the frozen creative variant, and that store's own coupon code.

The loop is the point. A 15-second spot inside a 60-second rotation shows a quarter as often as the same spot on a screen running only that ad. Booking the two as equal over-promises by 4×, so the rotation length is an explicit number on every flight — not an assumption buried in a rate card.
gameviewmanager.com/account_manager
Chain
Ad Buys
Locations
Schedule
Reports

Coca-Cola Summer 2026

$1,000,000 · 3 flights · 10 stores · 20 screens

BuysPlan & Creative DeliveryA/BCoupons
104%
of baseline
18,240
Showings
17,905
Airings
Bay Pines · Screen 1
Baseline 1,840 · Actual 1,912 · OTS 21,900
On pace
Cherry Creek · Screen 2
Baseline 1,840 · Actual 1,466 · OTS 14,200
Behind
Kapolei · Screen 1
Baseline 1,840 · Actual 1,801 · OTS not measured
No audience

Measured through Aug 1 · 1 of 20 screens has reported nothing

Delivery is rolled up nightly, and every report says the date it is measured through.

📺

“How many times was the ad on screen?”

Two numbers, because they answer different things. Airings is measured directly — the number of times the creative actually came up on a screen. Showings is derived from on-screen seconds and the rotation length. A run already playing at midnight is a continuation, not a fresh airing, so one long evening is never counted twice.

🎟️

“Which stores drove the coupon scans?”

Every store gets its own coupon code and its own short link, per creative. Scan a QR in Bay Pines and the scan says Bay Pines. If a buy ships one shared image with one code baked into it, the report says so and reports at the creative level — rather than printing a per-store split of numbers that were never attributable.

🔀

“Which creative won?”

Stores are split between variants deterministically and the assignment is frozen, so editing weights mid-flight can never reshuffle stores that are already running. The headline is scans per 1,000 showings, never raw scans — and below the significance threshold the answer is “too close to call”, not a winner.

📐

“Baseline vs actual?”

The baseline is pro-rated to the days that have elapsed. Measuring week one against a three-month promise and calling it “8% delivered” is true and useless. Preflight also reports what the buy will land on before a dollar of it is placed — stores with no screens, flights booking zero days, budget left unallocated.

Reporting

Numbers that mean what they say.

Chain reporting fails quietly. A store that stopped reporting looks like a store that ran zero. A rollup that is two days behind looks current. An average across the estate absorbs both. Every number here carries the thing that would otherwise be left out.

Null is not zero. A store with no audience measurement reports not measured, never 0. Adding zeros for ninety unmeasured stores understates a national buy while looking exactly like a measurement.
Measured through. Delivery is a nightly rollup, so every report states the date it runs to and counts the screens that reported nothing at all — a report that silently stops at yesterday is how an advertiser gets told a campaign under-delivered when the job was simply behind.
TermWhat it countsSource
Airings The number of times the creative came up on a screen — a transition into the ad, inside the reporting window. Measured
Showings On-screen seconds divided by the rotation length. What a media planner means by “times it ran”. Derived
OTS Opportunities to see — showings × the store's measured audience × its attention factor. Null where the store has no audience measurement. Derived
Coupon scans Scans of that store's own code, for that creative. Reported per 1,000 showings so a busy store doesn't win the A/B on traffic alone. Measured

One vocabulary, deliberately. The word impressions is not used anywhere in a buy report, because a venue's own campaign report already uses it for person-hours of screen time — and a chain roll-up that prints a different quantity under the same heading is a number nobody can reconcile.

One console. Every store. One report.

Let's map your estate.

Bring a store list and we'll come back with the blueprint, the screen count and what the estate is worth as an ad buy. Four screens or four hundred, the wiring is the same in every one.

info@gameview.tv  ·  727-223-6494  ·  gameview.tv