For tourism boards and destinations

The Scavvi
Engine

Family exploration trails branded as your city, and an analytics console that shows you exactly how families moved through it. Every visit verified on the ground, not modelled from a panel.

Families are a third of leisure travel and the hardest group to measure. They are invisible in your data and fragile on the ground.

Kids get bored, so visits get cut short. Everyone crowds the same three landmarks while the quiet gems stay quiet. And when you report on it afterwards, the honest answer is that nobody knows which families went where, in what order, or whether they enjoyed any of it. The Engine was built to answer exactly that.

The loop

Explore. Stamp.
Spend. Share.

Four moves, one game. Each one is something a paper trail or a printed passport starts but cannot finish, because paper cannot tell you who walked it.

πŸ—ΊοΈ

Explore

Trails route families past the hotspots and into the lanes you want walked, then on to the next neighbourhood or the next city.

πŸ“Έ

Stamp

Every stop is a GPS and photo verified find. A stamp that proves somebody actually stood there, rather than a device passing within 200 metres.

Partner module
🎟️

Spend

Optional partner module: perks at merchant stops, unlocked by arriving. The journey that leads to the till, built on purpose.

πŸ’›

Share

Finds share as branded cards carrying your destination, not ours. Earned reach on every post, built into the mechanic.

What it is

Three parts,
one engine.

🏷️
Solution

White-label, powered by Scavvi

Geofenced family trails around your landmarks, museums and events, branded as yours. The engine is already shipped and running, so a city launch is a re-skin and content, not a new build.

🧭
Engine

Dispersal by design

The trail decides the route. Put a stop somewhere quiet and families walk there, because the game asks them to. Crowding at the hotspot becomes a design choice, not a fact of life.

πŸ“Š
Insight

The console

A live dashboard of how families actually moved: verified stop visits, movement heatmaps, routes, time of day, origin markets, group make-up and satisfaction. Exportable to CSV or a board-ready report.

The data

Verified,
not guessed.

Every find is captured the moment a family stands at the stop, takes a photo, and the AI confirms it is the right thing in the right place. Here is exactly what that gives you, and what it does not. We would rather you knew both before you started.

MetricScavviDetail
Footfall at a specific stopVerifiedA photo taken at the location, confirmed by AI, with GPS. Not a model, not a sample.
Route and order of visitVerifiedEvery find is timestamped, so the actual sequence between stops is known.
Dwell and pace between stopsVerifiedTime between consecutive finds on the same trail.
Family group sizeVerifiedNumber of players in a hunt. Telco panels cannot separate a family from four adults.
Source marketSelf-declaredHome country given in-app, plus device language. Optional, so coverage is partial.
Family compositionSelf-declaredAge band of the children exploring. Optional and aggregated only.
SatisfactionDirectOne-tap rating at the end of a trail, while the experience is still happening.
Visitor spendNot capturedScavvi does not see transactions. Card-spend partners remain the right source.
Total city footfallNot capturedScavvi measures families playing a trail, not everyone in the city. Complementary to your panel data, not a replacement.

Scavvi sits alongside the data you already buy. Telco panels give you volume, card partners give you spend, surveys give you sentiment weeks later. The Engine gives you verified family movement and how they felt about it, on the day.

How many families is this based on?

It is the first question worth asking any vendor, so we answer it before you ask. Every figure in the console carries the sample it is drawn from, and any metric below our published minimum is suppressed rather than shown as a trend. A pilot is an instrument being built: you are buying a dataset that does not exist yet, and we will tell you plainly when it is big enough to act on.

Partner moduleBuilt per partner

The gap between
engagement and the till

Where a destination works with retail partners, a sponsor, or a payment brand, stops can carry perks that unlock by arriving. That turns the trail into a measurable route to a merchant door.

It also produces a number nobody currently holds: who photographed a place and did not spend there. The journey is ours to observe; the transaction stays entirely with you and your payment partner. We never see or touch a card.

This module is scoped per partner rather than switched on, and it is not part of the standard console. Ask about it if you have a retail or payment partner in the mix.

Access

You get the data,
not just a dashboard.

A chart you cannot export is a screenshot. The point of a pilot is that your team ends up holding a dataset it did not have before, in a shape it can join to everything it already owns. Four ways in, and the data belongs to your board in all of them.

Live
πŸ–₯️

The live console

A browser dashboard, per city, with named access for your team. Heatmaps, routes, stop tables, time patterns and satisfaction, updating as families play.

Live
πŸ“„

Board-ready report

The season in a document you can put in front of a committee without rebuilding it in PowerPoint first. Printed or PDF, with the sample sizes stated on every figure.

Live
⬇️

CSV export

Every table in the console, downloadable. Take it into Excel, your BI stack or your existing visitor-data warehouse and cut it however your analysts prefer.

Scoped per partner
πŸ”Œ

Data feed for joining

Where you want it flowing into systems you already run, an aggregated feed can be scoped per partner. This is how the journey data gets joined to spend, ticketing or campaign data that we never see and never want.

We observe the journey. You join it to everything else. Scavvi is deliberately not trying to become your single source of truth. It measures the one thing your other sources cannot see, and hands it over in a form that makes them more useful.

The insights

What you learn
on Monday morning.

Did the dispersal work?

See how many families reached the quiet stop you wanted lifted, and what share of the trail they completed after it.

When do families actually explore?

Time-of-day and day-of-week heatmaps, so staffing, opening hours and partner offers line up with reality.

Which markets are bringing families?

Self-declared home country and app language, so you know whether the German campaign brought German families.

Where do families give up?

Completion and drop-off by stop. A stop everyone abandons is telling you something about that street.

Did they enjoy it?

A one-tap rating at the end of the trail, captured while they are still in the city rather than in a survey six weeks later.

What is worth funding again?

Season-on-season comparison per trail and per stop, exportable as a board-ready report for the funding conversation.

How a pilot works

One season.
One trail. Real numbers.

01
β˜•

Fifteen minutes

You tell us the landmarks you want walked and the corners you want lifted. We tell you honestly whether Scavvi helps.

02
✍️

Scope and price

A written scope with a fixed price, the stops agreed, and the success measures set before a line of it is built.

03
πŸš€

Live in weeks

Your trail goes live in the app in eight languages, co-branded, with QR codes for your welcome desks and hotel partners.

04
πŸ“ˆ

Your dashboard

A live console from day one, plus a board-ready report at the end of the season with the numbers you can take to funding.

Methodology and privacy

Built for a children's app first

Scavvi is used by children, so the privacy bar was set by that before it was ever set by a client. Everything a board sees is aggregated and anonymised, with a k-anonymity floor: if a cut of the data is small enough that it could point at a specific family, it is suppressed rather than shown. There is no individual-level reporting, no child-level reporting, and no way to ask the console about a person.

Photos exist to verify that a find is genuine. They are not sold, not shared with boards, and not used to profile anyone. Origin and family-composition signals are optional, self-declared and only ever reported as totals.

The data your city's trails generate belongs to your board. We are happy to work to your data residency requirements and to put all of this in writing before a pilot starts.

Who builds this

Scavvi started as an eleven-year-old's idea. Harper wanted a scavenger hunt that did not need a parent to organise it, and her dad built it. That is still how it works: she decides what is fun, he makes it run. The same trails families play on holiday are the ones that power city pilots.

Read the story β†’

Questions boards ask

What does a pilot cost?

Pilots are paid and scoped per city, based on the number of trails and the season length. The first conversation is fifteen minutes and free, and you get a written scope with a fixed price before anything is committed.

Who builds the trails?

We do, working from your priorities. You tell us the landmarks you want walked, the quiet corners you want lifted and the events you want tied in. You approve every stop and every clue before it goes live.

What languages does it run in?

Eight today: English, French, German, Spanish, Italian, Portuguese, Dutch and Japanese. Every trail is available in all of them, so a Japanese family and a German family play the same trail in their own language.

Who owns the data?

You do. The visitor data generated by your city's trails belongs to your board, and you receive it as a live dashboard, CSV export and a board-ready report.

How does this work with children's data?

Everything reported to a board is aggregated and anonymised. There is no individual-level or child-level reporting, ever. Photos are used to verify a find and are not sold, shared or used to profile anyone.

We already buy footfall data. Why this?

Because footfall panels tell you devices moved through an area. They cannot tell you a family of four arrived at a specific statue, in what order they walked, whether they actually stopped, and whether they enjoyed it. Scavvi answers the family-segment questions your existing data cannot reach.

Start with fifteen minutes

Tell us the corners of your city you wish more families reached. We will tell you straight whether the Engine is the right tool for it.

Book a pilot conversation β†’

Or email hello@scavvi.com Β· See where trails are live