Foot Traffic Data API - Visits, Trade Area, Demographics

visit-metrics

Charged once for each place summarised over a date window: the extrapolated visits and unique visitors for the whole population, the panel visits and panel visitors the provider actually observed and modelled from, the visit length segment the figures were calculated on, the nearby activity radius where one was used, the place name, type and category, and a flag saying whether a distance filter has made the panel and extrapolated counts describe different populations. Entities the provider holds no data for over the window are not charged.

visit-bin

Charged once for each bin of a trend or breakdown: a date bin from a daily, weekly or monthly trend with its extrapolated visits and the panel visits behind them; a day of the week or an hour of the day with its estimated foot traffic and, on the hourly report, whether the place was open in that bin; a dwell time band with the average and median dwell in minutes; or a loyalty band with the visitors and visits in it, each as a count and as a percentage, alongside the average and median visits per visitor. Empty reports are not charged.

trade-area

Charged once for each trade area drawn: the full GeoJSON MultiPolygon of where the visitors actually came from, the number of separate polygons in it, the method used, the traffic volume threshold the shape encloses, the maximum home distance or drive time applied, the block group allocation method, and the visit length segment behind it. Entities the provider will not release a trade area for are not charged.

demographic-attribute

Charged once for each demographic attribute of a trade area: its full path through the provider's own structure, its leaf name and its numeric value, alongside the data set it came from and the date window. Covers census demographics and, where the plan includes them, population statistics, consumer landscape, market outlook, spending patterns, workplace, persona segments and follow graph. Data sets the account cannot see are refused rather than charged.

journey-destination

Charged once for each other chain or place the visitors to a location also frequent: its entity identifier, name and type, its group category, category and sub-category, the share of visitors it accounts for, the visitor and visit counts behind that share, and for a place the distance in miles from the subject. Locations with no journey data are not charged.

ranking-record

Charged once for each ranking row: an overview row carries the place's rank in one geography - nationwide, its state, its DMA, its CBSA or a local radius - with the size of the field it was ranked against and the visits behind it, plus the scope, the metric and the parent chain. A ranking index row carries one neighbouring venue with its name, address, rank and visits alongside the subject's own rank and the total ranked. Rankings the provider refuses for a flagged or unverified entity are returned with the reason and are not charged.

retail-sales

Charged once for each retail sales metric returned for a place: the metric name, the value, and the value type saying whether the number is currency, a count or an index, over the requested window, or one time bin of a sales trend. Entities with no sales coverage are not charged.

block-group

Charged once for each census block group that sent visitors to a place in a time bin: the block group identifier, the bin date, the visits attributed to it and its share of the total. This is the row that turns a trade area polygon into a list of neighbourhoods. Places with no block group coverage are not charged.