Micro id
Identifies the 5-digit Micropolitan Statistical Area code for the surrounding postcode, or NULL if the postcode is not in a micropolitan area. Known or imputed for 5,466 postcodes — 16.0% of the postcodes Faraday knows.
At a glance
- Coverage today
- 16.0%
- Typical coverage
- 16.0%
- Postcodes with a value
- 5.5K
- Share in largest category
- 2.0%
- Most values come
- from the area
- When latest collection arrived
- Sep 16, 2026
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 postcodes in each category. 99+ categories, of which the 20 largest are shown, with 2.0% 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.
- 301002.0%108 postcodes
- 368370.8%44 postcodes
- 390600.8%41 postcodes
- 458600.7%39 postcodes
- 363000.7%37 postcodes
- 268600.6%35 postcodes
- 141400.6%31 postcodes
- 217000.5%30 postcodes
- 309400.5%28 postcodes
- 459000.5%27 postcodes
- 181800.5%27 postcodes
- 274600.5%26 postcodes
- 185000.5%26 postcodes
- 364600.5%26 postcodes
- 123000.5%25 postcodes
- 146600.5%25 postcodes
- 407000.5%25 postcodes
- 319400.5%25 postcodes
- 384600.4%24 postcodes
- 283000.4%24 postcodes
- 395000.4%23 postcodes
- 461800.4%21 postcodes
- 259000.4%21 postcodes
- 172200.3%19 postcodes
- 131800.3%19 postcodes
- 402600.3%19 postcodes
- 414000.3%18 postcodes
- 407800.3%18 postcodes
- 329400.3%18 postcodes
- 327400.3%18 postcodes
- 103000.3%17 postcodes
- 182600.3%17 postcodes
- 371400.3%17 postcodes
- 449800.3%17 postcodes
- 497800.3%16 postcodes
- 367000.3%16 postcodes
- 117800.3%15 postcodes
- 354200.3%15 postcodes
- 339800.3%15 postcodes
- 192600.3%15 postcodes
Category shares over time
The 5 largest categories, each followed across 4 collections. Estimated from a 1% sample of postcodes.
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 postcodes in each state with a value.
Coverage over time
Share of postcodes 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 — 0%
- Not used for this attribute — no value is inherited this way.
- From geography — 100%
- Estimated from other people in their postcode or region.
Coverage, in context
Where 16.0% sits on the catalog’s own coverage range.
Higher coverage than 1% of postcode-level attributes in the catalog
Freshness
Whether the values reflect today. A long gap since the latest collection arrival 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 postcodes it carried. Gaps are real — collection is periodic, not continuous.
Change between collections
How much values move between collections. Income or life events should move; heavy change in something steady can mean noisy data.
of postcodes changed value between the two most recent collections.
Contribution ledger
4 ingestions1 authority contributed since Dec 2021.
| Observed | Ingested | Count | ID |
|---|---|---|---|
| 41,117 | e2d21660-1ea6-430a-8bf9-33673e10fdd6 | ||
| 41,045 | 263a35d2-5801-4741-b944-e98bac372850 | ||
| 41,045 | 2a630c8a-310d-4609-85f0-6b111e297fd3 | ||
| 41,045 | bd04e3fc-186d-491b-8619-c4aa7f2f47a9 |
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 Micro id back in real time.
- Add
micro_idto a project. - Send an email, phone, or address to the project's append endpoint. The response carries Micro 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":{"micro_id":"30100"}}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.
- micro_
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 postcodes, 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.
- nominal
- 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.
- null
- 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