The Steps Involved

Every project like every business and brand is diffrerent, here are some steps we find common between deployments in your industry.

Get Started

Airport AR pilot: decide and prepare

Pick one mechanic and a single terminal path for the MVP. Secure security approvals, confirm POS or voucher wiring, run Wi‑Fi/DAS soak tests, and publish consent copy and visible policy links.

Lock scope with the Navigator
Pick gates and time windows for A/B tests
Confirm POS mapping and loyalty joins
Approve privacy and signage copy

Configure and train: POS mapping, FIDS/queue APIs, kiosk/MDM lock‑down

Integrate with POS or issue time‑bound vouchers. Wire FIDS and queue‑time APIs. Lock kiosks/tablets with MDM. Train staff on scripts and exception handling.

• Pre‑cache assets and enable offline mode • Landmark prompts for wayfinding accuracy • One‑tap redemption with pickup routing • Staff scripts for help and crowd safety

Run the pilot: A/B by gates or time slices with POS‑verified attribution

• Monitor queue advisories and adjust dwell prompts • Watch heatmaps and redeploy signage • Large type UI and smooth camera moves • Incident log and on‑call rota in place

Step 4: Test, Record, Improve In Live Service

• Zero Sev‑1 incidents as a hard gate • POS and loyalty attribution verified • Scale by gates then terminals

Frequently Asked Questions

Will AR distract passengers or slow them down?

Design with conservative time estimates, large‑type UI, landmark prompts. Provide an identical non‑AR path for rewards and step‑free routing.

How do we handle security and privacy?

No biometrics, coarse geo, fast deletion. Visible policy links and role‑based access. Secure approvals with audit logs and signed builds.

What if the network is unreliable?

Pre‑cache assets, edge CDN, offline core flows. Run Wi‑Fi/DAS soak tests before launch and monitor during live days.

Can we attribute spend to the program?

Yes. Use unique codes, voucher mapping, POS reconciliation, and loyalty joins as a second signal. Report by terminal and gate.

How do we disperse crowds at a delay gate?

Trigger short quests and quiet‑zone prompts via DOOH or app pushes, routing to nearby amenities.

What to track from day one

Use session_id, hashed pax_id (opt‑in), flight_no, terminal/gate, geo_cell, poi_id, offer_id, order_id. Track wayfinding start/complete, queue views, try‑on start/place, offer view/click, voucher issue/redeem, pre‑order start/complete, lounge upgrade steps, and crashes.

• Real‑time ops view for stability • CDP/CRM for marketing • POS/loyalty for redemptions • Warehouse for per‑cap and flow

Tech stack: POS, vouchers, FIDS, queue APIs, SPARC signage sync

Use in‑app SDK for airport/airline apps with WebAR fallback. Back end connects to POS/vouchers, loyalty/CRM, FIDS and queue‑time APIs, and a CMS. Optional SPARC syncs live signage. Network segmentation, signed builds, and audit logs satisfy IT/security.

• Tag Manager/Analytics or CDP for events • Coarse geo cells, no biometrics • Retention limits and visible policy links • MDM for owned devices

Example MVP

Scope a single path from security to a gate with 4–6 points of interest and 1–2 concession offers. Add one duty free try‑on scene and a sponsor frame. Use offline cache, brightness controls, strobe‑safe content.

• Large‑type UI and one‑hand mode • Non‑AR path with identical rewards • Quiet‑mode content near sensitive areas

Download journey blueprint || /resources/ops-checklists#journey

Choose your format

Compare Technologies

AR Wayfinding

Arrows to check‑in, security, amenities, gates, with live queue advisories.

Concession Promos & Pre‑Order

Hyper‑local offers with click‑and‑collect and pickup routing.

Duty Free Virtual Try‑On

Sunglasses, watches, cosmetics and more with reserve or pay‑now.

Gate Delay Engagement

Short quests or quiet‑zone prompts to disperse crowds.

Lounge Upgrades

Show value, upgrade if eligible.

Airport outcomes: spend up, stress down, clean attribution

AR wayfinding plus synchronized offer moments meet passengers where they are. Camera‑up arrows reduce uncertainty; hyper‑local offers and duty free try‑on convert interest into orders and loyalty joins. Results attribute by terminal/gate for commercial proof.

Shared context across DOOH, jumbotrons, and mobile
One‑tap pre‑order or voucher with pickup routing
Queue advisories to smooth dwell and dispersal

Lift per‑cap revenue and verified opt‑ins
Reduce misdirects and disperse dwell
Attribute results by terminal, gate, and offer

Airports And Duty Free Playbook

Non‑aero revenue must rise, complaints must fall, and security can’t be compromised.

You need clean attribution for concessions and sponsors, smoother flows to gates, and opt‑ins you can act on.

This page shows one focused, auditable program to hit all three.

See More Insights Into Immersive In Airports

Airport KPIs: per‑cap revenue, redemption, pre‑order, queue time

Commercial:
per‑cap +3–7%, offer
redemption 8–15%,
pre‑order 5–10%,
verified opt‑ins.

Passenger:
wayfinding completion ≥70%, queue time
−10–20% on targeted routes,
NPS/CSAT +10 points.

Ops:
crash‑free ≥98%,

ROI snapshot

Estimate monthly users from pax volumes and take‑rate. Compare baseline vs XR conversion (offer→redeem, view→pre‑order, loyalty join). Multiply by AOV and add sponsor fees. Apply an attribution factor, then compute per‑cap uplift as a second lens.

Inputs sheet for assumptions
Three‑year ROI and payback
Validate with tagged codes and POS mapping

Pilot Design Example

Design A/B tests by gates or dayparts and hold flight mix constant. Target 20–40k sessions for directional reads. Verify attribution through codes or POS mapping; require zero Sev‑1 incidents to exit.

• Gate exit when KPIs are green • Scale to all gates in terminal • Add a second mechanic (e.g., lounge upgrades)

Safety, Privacy & Compliance in Airports and Terminals

Passenger-facing immersive activations in airports must be rights-safe, compliant with aviation security rules, and accessible. No biometric collection, no personal identifiers, no tracking beyond coarse geo or QR scans. All activations must run offline if needed, with non-AR equivalents available. Projection mapping and LED solutions for terminals and waiting areas must meet fire, safety, and passenger flow codes, with brightness and refresh rates tuned to avoid health risks. Installations must not block egress or sightlines. LBE activations (pop-up AR booths, immersive lounges, projection-mapped experiences) require signage with plain-language notices, opt-in/out, sponsor attribution, and audit logs. Accessibility defaults include subtitles, high-contrast UI, one-hand mode, strobe-safe settings, brightness controls, and seated-friendly experiences.

• No biometrics or face recognition • Coarse geo/QR scans only • Offline fallback mode • Plain-language consent and signage • Projection/LED installs meet aviation safety codes (brightness, egress) • LBE activations supervised with audit logs • Accessibility defaults (captions, high-contrast, strobe-safe, one-hand, seated)

Risks & mitigations: security, network variability, wayfinding accuracy, POS complexity

Address security/privacy with approvals, signage, and data minimisation. Handle network variability via pre‑cache, edge CDN, and offline animations. Improve wayfinding accuracy with geo cells and landmark prompts. Reduce POS complexity with voucher fallbacks.