ZDOS provides clear insights into passengers flying into competitor airports and visiting your airport market. Learn more here!
Setting the Airport Boundary
The Boundary is the area we set up to represent your “market”. Your boundary should cover the area where you hope a passenger would choose to fly into your airport rather than a competitor when visiting.
For example, Tampa’s Boundary would encompass the greater Tampa area, out to about halfway to Orlando.
Observations
Devices are observed in a competitor airport (in the airsides, parking lots, and rental car areas).
Devices are then observed in your airport “Boundary”.
Inbound Leakage Count
When a device is observed in the competing airport and then observed in your boundary within the same calendar month, it’s counted as one inbound leakage.
Inbound leakage counts are accumulated over the month to give the totals you see in the insight. The data will show, say, 400 devices seen at the competing airport AND in the boundary in January, 350 in February, 500 in March, etc.
If a device is observed several times in that competing airport over a day, the extra observations will be discarded and only one observation is recorded for the day.
Multiple Day Visits
Someone could fly into the competing airport on Monday (and be observed at that airport) and then visit your boundary on five subsequent days, while someone else may only visit the boundary one day. We remove the extra days so each of these instances would count as only one inbound leakage.
If a device is observed again during the month in the competing airport and the boundary, a second inbound leakage would be counted.
Observed at Both Airports
If a device is observed in both the competing airport and the partner airport, the observation is removed from the count. This assumes that the device connected at the competing airport and flew into/out of your airport.
Inbound/Outbound
Inbound leakage is only recorded for devices that are dubbed “Inbound”—devices that live more than 150 miles from the observation. So Inbound Leakage is not recorded for locals.
DMAs, But Not Cities
We surface origin market DMAs for the Inbound Leakage counts. We do not surface cities.
Summarization
Zartico’s observations are SUMMARIZED monthly. You will not be able to see insights by week, or by day.