Metro id
Census Bureau identifier for the Metropolitan Statistical Area containing the individual's address. Known or imputed for 100.5 million addresses — 83.9% of the addresses Faraday knows.
At a glance
- Coverage today
- 83.9%
- Typical coverage
- 83.8%
- Addresses with a value
- 100.5M
- Share in largest category
- 6.3%
- Most values come
- from the address
- Latest collection
- Jan 1, 2020
How the categories split
How values are spread across the records that have one. Use it to check that the attribute tells records apart: when one value holds nearly everyone, it will not separate audiences much. Categories are ranked by share, largest first. “All other values” groups the smallest into one bar.
Share by category
Share of addresses in each category. 99+ categories, of which the 20 largest are shown, with 6.3% in the largest.
Every category
99+ categoriesThe chart above draws the 20 largest. Search here for one it does not. This list holds the 100 most common; rarer values are not named.
- 356206.3%6,316,207 addresses
- 310803.7%3,725,098 addresses
- 169803.2%3,200,731 addresses
- 191002.6%2,640,603 addresses
- 264202.3%2,298,484 addresses
- 331002.2%2,210,428 addresses
- 379802.2%2,198,315 addresses
- 479002.1%2,148,906 addresses
- 120602.1%2,112,005 addresses
- 144601.8%1,782,713 addresses
- 198201.7%1,742,641 addresses
- 380601.6%1,649,207 addresses
- 418601.5%1,472,844 addresses
- 334601.3%1,346,557 addresses
- 426601.3%1,344,957 addresses
- 453001.3%1,319,487 addresses
- 401401.3%1,260,875 addresses
- 197401.1%1,149,301 addresses
- 411801.1%1,093,401 addresses
- 167401.1%1,063,778 addresses
- 125801.0%1,028,119 addresses
- 367401.0%1,011,358 addresses
- 417401.0%993,183 addresses
- 383000.9%941,594 addresses
- 417000.9%895,237 addresses
- 389000.9%884,639 addresses
- 171400.9%882,610 addresses
- 174600.9%874,034 addresses
- 181400.8%843,574 addresses
- 298200.8%830,436 addresses
- 124200.8%825,838 addresses
- 281400.8%799,965 addresses
- 269000.8%795,149 addresses
- 349800.8%766,258 addresses
- 409000.7%750,475 addresses
- 272600.7%664,744 addresses
- 472600.6%646,480 addresses
- 393000.6%624,447 addresses
- 333400.6%616,247 addresses
- 395800.6%571,459 addresses
Coverage
How widely Faraday has this attribute, and how precise its values are. How many of your own records get a value also depends on how many of them Faraday matches. The state map shows where coverage is thin. Coverage over time shows whether it is growing or shrinking.
Coverage by state
Percentage of addresses in each state with a value.
Coverage over time
Share of addresses holding a value at each monthly snapshot. A value carries forward for one year.
How we arrive at a value
Whether a value was observed on the person themselves, carried from their address, or estimated from the people around them.
- On the person — 0%
- Not used for this attribute — no value is inherited this way.
- From address — 100%
- Carried from what we know about the household at their address.
- From geography — 0%
- Not used for this attribute — no value is inherited this way.
Coverage, in context
Where 83.9% sits on the catalog’s own coverage range.
Higher coverage than 80% of address-level attributes in the catalog
Freshness
Whether the values reflect today. A long gap since the latest collection means they may lag behind what is true now.
Collections
How recently this was collected, and how often a new collection arrives. Each bar is one collection, sized by how many addresses it carried. Gaps are real — collection is periodic, not continuous.
Contribution ledger
1 ingestion1 authority contributed since Jan 2020.
| Observed | Ingested | Count | ID |
|---|---|---|---|
| 119,048,853 | e84435bf-fdae-464b-ad1b-45a5aca06bc2 |
Related attributes
Attributes whose descriptions are closest to this one.
Neighbors found Oct 2026.
Use it in the API
Send an email, phone, or address. Get Metro id back in real time.
- Add
metro_idto a project. - Send an email, phone, or address to the project's append endpoint. The response carries Metro id for the matched person.
curl -X POST 'https://api.pro.faraday.ai/v1/projects/YOUR_PROJECT_ID/append' \
-H 'Authorization: Bearer YOUR_API_KEY' \
-H 'Content-Type: application/json' \
-d '{
"email": "jane.doe@example.com"
}'→ {"attributes":{"metro_id":"35620"}}Technical details
null in any row means the label does not apply, or is not recorded, for this attribute.
- API name
- The field to request through the API, and the key it comes back under in a payload.
- metro_
id - Category
- The catalog group the attribute is filed under.
- fig/geography
- Type · unit
- The kind of value and, where it has one, its unit of measure. Counts on this page are in addresses, whatever the unit.
- Text
- Statistical type
- How the values are meant to be read: a measured amount, one of a ranked set, one of an unordered set, or several from an unordered set. The chart's form comes from the published values; for categories without a rank prefix, this label decides whether they are listed in rank order or by size.
- categorical
- Allowed values
- The full list of values, when the attribute has a fixed set.
- null
- Derivations
- How the value is produced, each with its definition.
- Unspecified
- How values combine
- How the values from the attribute's sources become the one value delivered.
- Read from a single source field.
- Directionality
- For ordered values, what a higher value means.
- null
- Deprecation
- True when the attribute is being retired; choose another for new work.
- false