BlackPrint · Guides · Data layers
Mobility data in Mexico
The layer that turns a static map into behavior: how many people pass a point, at what hour, which days and where they come from. Measured with an own panel of more than 60 million devices per month in Mexico — always aggregated and anonymous.
Updated September 4, 2026 · BlackPrint Team
The essentials, in 20 seconds
- Own panel of 60M+ devices per month in Mexico, always aggregated and anonymous
- Four dimensions: volume, hourly rhythm, origin and dwell — by polygon or by point
- The rule that makes it auditable: device ≠ person ≠ buyer, declared in writing
01 · What it is OWN PANEL · MEXICO
Not how many people are there. How many pass by, and when.
Demographics count who lives there. Mobility counts who passes through — which, for a business that lives on flow, are different things and sometimes opposite ones.
What the layer contains
| Variable | What it holds | Resolution |
|---|---|---|
| Volume | Devices observed inside a polygon or in front of a point | Daily and hourly |
| Hourly rhythm | Distribution across the day and the week | Hour bands · 7 days |
| Origin | Where visitors come from (aggregated origin zone) | Block / neighborhood |
| Dwell | How long they stay and how often they return | Per visit |
02 · What it is for REAL DECISIONS
Five decisions that are made blind without mobility.
Each with a published guide and measured numbers, so the method can be audited before buying.
Questions it answers
| The question | Who asks it | How the layer answers |
|---|---|---|
| How many people pass this corner? | Retail, restaurants, franchises | Volume and hourly rhythm of the candidate polygon |
| Where do my customers come from? | Multi-unit chains | Real origin — not a drawn radius |
| Does the new store steal from mine? | Expansion | Shared visitors between the two points — from 91.7% to 0.7% |
| How many people enter the competitor's mall? | Real estate and retail | Volume of a third-party polygon, no permission needed |
| How do I schedule staff? | Operations | Rhythm by day and hour — the real peak hour |
03 · Where it comes from SOURCES AND LIMITS
Where it comes from, and what it cannot tell you.
No territorial data is perfect. These are this layer's limits, stated before you discover them.
Sources, refresh and what it cannot say
| Point | How it works here |
|---|---|
| Source | Anonymous, aggregated mobile-device signals; own panel with national coverage |
| Refresh | Continuous; typical analysis windows are 30 days |
| Limit 1 — the denominator | Device ≠ person ≠ buyer. Some people carry two devices and many pass without entering. Expansion factors are declared in writing |
| Limit 2 — sample size | In very low-density areas the panel thins and week-over-week readings get noisy |
| Limit 3 — not identity | The layer says who nobody is. It is aggregated by design; there is no personal data to hand over |
04 · How you receive it 3 WAYS
Platform, data delivery or API.
Same layer; what changes is how you consume it. The right route depends on whether you will look at it, join it with your own data, or feed it to a model.
Which route fits
| Route | When | What you get |
|---|---|---|
| In the platform | You want to see it on the map and decide with it | The layer switched on over your area, with the others on top |
| Data delivery | You will join it with your own information in your tools | Geospatial files by area or nationwide, with a data dictionary |
| API | You will feed it to a model or your product | Query by parcel, polygon or coordinate |
Sobre tu territorio
Este análisis es del municipio. El tuyo es de tu esquina.
Si tienes una decisión enfrente —dónde abrir, a quién rentarle, contra cuánta competencia llegas— la medimos con los datos de tu zona exacta, no con promedios municipales.