Mobile Location Data
PiinPoint’s Location Intelligence platform provides up-to-date mobile location data, helping you learn more about your customers, competition, properties, and community’s movement behaviour.
PiinPoint has partnered with SafeGraph, a leading provider of anonymized mobile location data, to draw insights from 45 million mobile devices each month across North America.
Tired of municipalities with outdated or unavailable traffic studies? PiinPoint combines mobile location data with machine learning to provide accurate, consistent, and always up-to-date traffic counts for all major road segments across North America.
My Location Average
My Location Average
Mobile Location Data provides detailed visitor insights, giving you a snapshot of who your customers are, how often they visit a location, and how their behaviour changes over time. PiinPoint provides insights into visitors:
Draw your own custom geofence around nearly any area to get more granular visitor insights. Whether it be a building footprint, a local park, or a city block, geofencing areas allows you to narrow in on visits to that area.
60% TOTAL VISITORS
It doesn’t matter if you have access to customer data now or not, mobile location data allows you to better understand a property’s trade area, where your customers are coming from, and what kind of capture rates you have in each market.
Where does the Mobile Location Data data come from?
How do you protect the privacy of our customers?
We take privacy seriously at PiinPoint. We have partnered with SafeGraph, a leading provider of anonymized mobile location data. The data is collected from smartphone users who have given the app developers consent to gather location data. Data is de-identified, aggregated to a Dissemination Area (DA), ensuring that home or work locations are not shown. Geofenced areas must have a minimum of 15 people within its borders to be visualized.
How often is the data updated?
Data is delivered to PiinPoint daily, and is updated into PiinPoint on a monthly basis to account for lagging observation delivery (typically 1-5 days). Mobile location data from PiinPoint captures historical data up to 2 years old, and into the present day.
Most municipalities do not update AADT for all road segments each year. With PiinPoint’s mobile data, we are able to deliver the newest snapshot of AADT counts for any given road segment. This relieves our users from having to worry that traffic patterns haven’t changed since the latest version of AADT was created for any given area.
What is your data coverage?
PiinPoint’s Mobile Traffic data is available for all of North America. PiinPoint geofencing and Visitor Reports are available across Canada.
How does PiinPoint ensure accuracy?
PiinPoint has conducted extensive accuracy testing in order to be confident in our mobile data predictions. Using a supervised machine learning model, our accuracy measurements are currently at 81.62% for AADT predictions.
How is PiinPoint’s Mobile Data different from Annual Average Daily Traffic (AADT)?
PiinPoint’s Mobile Traffic data is not so different from AADT studies, except that it is based on a consistent set of observations (anonymized mobile devices), as opposed to a variety of collection methodologies and display options. PiinPoint’s Mobile Traffic is always displayed by road segment, as opposed to point-based locations.
How do you Calculate Visits?
Visits are calculated based on devices intersecting a geofence within a requested time frame. Any single intersection is staged as a potential visit. For each, PiinPoint assesses other factors of the device at the time frame including its GPS accuracy and velocity, in order to disqualify visits that cannot be confidently placed in the geofence.
How do you Calculate Traffic Volumes?
Traffic volumes capture all intersecting devices along a queried road segment. Similar to visits, intersecting devices are staged as a potential vehicle or pedestrian and undergo qualification tests to identify the type of traveller. Qualified devices are counted and summarized as a result of the traffic volume request.