Contents
- Why does every report start with arrivals?
- Who never appears in the hotel count?
- Which sources does a destination already hold?
- Why does the number arrive after the decision?
- What do businesses get back when they share their numbers?
- Can a park gate say something about tourism?
- What does an observatory add that a dashboard does not?
- A monthly page that someone actually reads
Destination data should tell a place who comes, when they come, where they go once they are there, what they spend and what all of that does to residents. Arrivals answer only the first of those questions, and only in part. Beyond arrivals, the measures that matter most are the spread of visits across months and districts, the visitors who never check into a hotel, spending that stays with local businesses, repeat visits, and how residents use their own city while visitors are in it.
Most destinations already sit on far more of this information than they use. The hard part is rarely collecting more. It is knowing who holds what, getting it to the people who decide in time, and reading it with the place in mind rather than the campaign.
Why does every report start with arrivals?
Because arrivals produce themselves. Every guest who checks into registered accommodation leaves a record, those records add up automatically, and the result can be compared across years without anyone designing a survey. It is cheap, steady and easy to explain in a meeting, which is more than can be said for most other numbers.
The weakness lies in what the figure actually counts. It counts check-ins, not people, so a visitor who moves between three hotels appears three times while a family staying with relatives does not appear at all. It says nothing about where those guests spent their day, whether they enjoyed it, or whether the old quarter was unbearable at noon. A report built only on arrivals describes the front door of the hotel.
I don’t want to dismiss the number. It is a good thermometer, and a long series of arrivals data is something almost every destination has. But a thermometer cannot tell you why the patient is warm.
Who never appears in the hotel count?
More people than most plans assume. The statistical definitions UN Tourism uses draw a basic line between a tourist, or overnight visitor, whose trip includes an overnight stay, and a same-day visitor, whose trip does not. In many cities and coastal districts the same-day visitors are the larger group, arriving by coach, car, cruise ship or ferry and leaving before dark, and they are almost invisible in accommodation statistics.
They are not the only gap. Visitors staying with friends and family, people in short-term rentals that are not fully registered, delegates who sleep in the next city, residents of the wider region who come in for a concert or a match: all of them use the streets, the parks and the buses, and all of them spend money. Event audiences are a good illustration. A festival can fill a city center for three days and barely move the hotel figures, because most of its audience drove in from an hour away.
Does that matter? It does when decisions follow the data. Pressure on a heritage site, a beach or a ferry line often comes from day visitors, and a destination that sees only overnight guests will aim its heritage tourism management at the wrong visitors.
Which sources does a destination already hold?
Usually more than anyone has listed. The difficulty is that they sit with different owners, in different formats, on different schedules. Laying them side by side is often the most useful first step a destination body can take, and it is destination management in its plainest form.
| Source | Who usually holds it | What it shows well | What it tends to miss |
|---|---|---|---|
| Accommodation registrations | Public statistics or local registers | Overnight guests, origin, length of stay | Day visitors, informal rentals, visiting friends and relatives |
| Hotel occupancy and rates | Hotels, often pooled by an association | Demand by week, price pressure, weekday and weekend patterns | Everything outside the hotel |
| Card spending data | Banks and payment networks, in aggregated form | Where and when visitors spend, by sector and district | Cash spending, the reasons behind spending |
| Mobile location data | Telecom operators, aggregated and anonymized | Presence and movement of people by hour and area, including day visitors | Purpose of the visit, satisfaction |
| Transport counts | Airports, bus stations, ferry and rail operators, car parks | Arrival peaks and modes of travel | Where people go after arrival |
| Tickets and registrations | Museums, sites, event organizers | Visits to specific places, event attendance and origin | The rest of the visitor’s day |
| Recreation use | Park managers, trail counters, sports and cultural facilities | How residents and visitors share public spaces | Who the users are, unless asked |
| Surveys | Destination bodies, universities, businesses | Motives, satisfaction, resident attitudes | Anything not asked, small samples |
No single row answers the main questions. Two or three rows read together usually do. Card spending next to hotel occupancy shows whether a busy week also put money into local shops. Mobile data next to ticket counts shows whether a crowded site is crowded by day visitors or by hotel guests, the first question visitor flow management has to answer. Recreation use next to occupancy shows whether residents stop using their own seafront in August.
Why does the number arrive after the decision?
Timing is the most underrated problem in destination data. Annual statistics are published long after the year they describe, and by then next season’s prices, programs and campaigns have already been set. A hotel revenue manager looks at bookings daily, a tour operator weekly, an event organizer from one edition to the next. A destination body that sees its own picture once a year is always reacting to a season that has already gone.
Destination data earns its cost only when it reaches the people who decide while they can still change something.
That changes what a good data system looks like. Completeness is not the point. It needs a few indicators that arrive monthly or even weekly during the season, from sources that can provide them quickly, with a short note on what moved and why. A rough figure in June beats a precise one the following spring, at least for decisions about the summer. The precise annual figures still matter for a long-term destination strategy and for comparison with other places, but they are a different tool for a different meeting.
The same goes for problems like seasonality in tourism. A destination trying to fill its quiet months needs to know quickly whether a new off-season event or package actually brought people in, and whether those people stayed one night or three, so that the next attempt can be adjusted before the next winter, not two winters later.
What do businesses get back when they share their numbers?
Most tourism partnerships built around data quietly fail on this question, and our industry carries much of the responsibility. Hotels, operators and event organizers are generous with numbers when they want something, a grant, a listing in a campaign, a better slot in the calendar, and cautious when they are simply asked to contribute. Some of that caution is reasonable, since nobody wants competitors reading their occupancy. Much of it is habit.
The arrangement that works is a fair exchange. A hotel shares its occupancy and average rate each month and receives the anonymized picture for its whole area, which it could never build alone and which is worth real money in pricing decisions. An event organizer shares attendance and origin data and gets back a view of how its audience moved through the city, which is useful when it next negotiates with venues or sponsors. When a DMO or a comparable organization acts as the trusted middle, aggregating, protecting and returning the data, cooperation tends to grow year by year.
Events deserve a special word. Organizers already track event KPIs for their own reports, but those figures rarely reach the destination in a usable form. A few shared questions in every post-event survey, asking where people stayed, how long and what else they did, would add a great deal to a city’s picture at almost no cost.
Can a park gate say something about tourism?
More than people expect. Trail counters, bookings at sports halls, attendance at libraries and cultural centers, beach occupancy counts and the use of public parks are usually collected for reasons unrelated to tourism. Read alongside visitor data, they show something arrivals never will: how residents are using their own streets, parks and beaches while visitors are there too.
If residents stop using a popular beach in the high season, or a park’s evening use drops when a nearby street fills with visitors, that is an early sign of strain, and it often appears well before complaints reach any meeting. Read this way, data becomes a practical tool for managing tourism carrying capacity rather than an abstract number. It also feeds straight into any honest look at quality of life tourism seen from the resident’s side. The figures are modest and local, but they are the kind that decide whether growth is still welcome.
Resident surveys complete the picture. Asked the same way each year, a handful of questions about how tourism affects daily life shows the direction residents’ attitudes toward tourism development take over time, and gives a destination a reason to act before those attitudes harden.
What does an observatory add that a dashboard does not?
Many destinations have bought dashboards in recent years. They look impressive, update automatically and are often opened by very few people after the launch. A dashboard shows numbers; it does not say which ones matter this month or what anyone should do about them.
UN Tourism’s International Network of Sustainable Tourism Observatories describes its members as observatories monitoring the economic, environmental and social impact of tourism at the destination level, and its mission as supporting destinations committed to regular monitoring for evidence-based decision making. The word that stands out to me is “regular”. An observatory, in this sense, is less a piece of software than a routine and a group of people: often a university or research team alongside the destination body and local businesses, meeting on a schedule, agreeing what the figures mean and putting that interpretation in front of decision makers.
That human layer is what most data projects skip. It is also what makes the numbers credible. A figure interpreted by a mixed group of public, private and academic partners is harder to dismiss than one produced by any of them alone, and it is more likely to feed a real debate about the visitor economy instead of a press release.
A monthly page that someone actually reads
For most destinations, the realistic starting point is not a new system. It is one page a month during the season, and one a quarter outside it, built from four or five sources the destination can already reach: hotel occupancy from the association, a spending or presence figure from an aggregated provider, visits to the main sites, use of the busiest public spaces, and a line from the latest resident or visitor survey. A short paragraph on what changed, written by someone who knows the place, turns that page into something people discuss.
Over time the page can grow, and the destination can join wider networks, compare itself with similar places and invest in better sources. But the habit comes first, because data that nobody reads on a schedule is just storage. When your own destination’s next figures arrive, who will be the first person to read them, and what will they be in a position to change that week?