A Pin Report is a point in polygon report that can be used to track visitation patterns within locations.
Table of Contents
👋 Do you have questions about anything on this page or in our help center? Contact our Support team!
Overview
A pin report provides the same information as the zero point report, but with the addition of the exact lat-long the of device when seen while in the polygon. This becomes useful for analyzing traffic patterns of larger areas like shopping malls, high streets, or neighborhoods. The format of this report is:
| Polygon ID | Near ID | Latitude of Visit | Longitude of Visit | Unix Timestamp of Visit |
Like all our reports that include timestamps, an option exists to convert the output of the report to contain the timestamp of point-in-polygon visits to be “friendly” dates, as well as a choice to convert to local time.
FAQs
What is the difference between a Pin Report and a Zero Point Report?
The Zero Point report is a subset of information in the Pin Report. The pin report (so-named because you can easily make visitation pin maps of your study location) provides for each visitor, their Near Anonymized ID, the timestamp of their visit, the name of the location they visited (as passed into the API) and the latitude and longitude of the observation point. The pin report is useful for larger study areas, like malls or stadiums or neighborhoods, where the exact location point of the observation is useful.
The Zero Point report (so-named because it's the zero-point in time of the analysis) concentrates on the TIME of the visit, not the specific lat-long point inside the location. For a small footprint store like a restaurant, the actual lat-long of the observation point is not relevant for most analyses, and merely adds extra size to the file.
The amount of rows within each file will be the same, ceteris paribus.