City
Name of the city or municipality in the individual's mailing address. Known or imputed for 117.1 million addresses — 97.7% of the addresses Faraday knows.
At a glance
- Coverage today
- 97.7%
- Typical coverage
- 97.6%
- Addresses with a value
- 117.1M
- Share in largest category
- 0.8%
- 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.
Share by category
Share of addresses in each category.
No single value is common: at least 99 distinct values, the largest holds 0.8% of addresses with a value, and the 20 largest together hold 9.5%.
Show the 20 most common
Every category
99+ categoriesThe 20 most common are listed above. Search here for any other. This list holds the 100 most common; rarer values are not named.
- Houston0.8%951,502 addresses
- Chicago0.7%849,172 addresses
- Brooklyn0.7%780,642 addresses
- Los Angeles0.6%661,118 addresses
- New York0.6%644,289 addresses
- Miami0.5%623,290 addresses
- San Antonio0.5%621,562 addresses
- Las Vegas0.5%589,114 addresses
- Philadelphia0.5%565,327 addresses
- Dallas0.4%485,237 addresses
- Columbus0.4%484,614 addresses
- Denver0.4%467,421 addresses
- Phoenix0.4%458,746 addresses
- Jacksonville0.4%454,805 addresses
- San Diego0.4%418,336 addresses
- Austin0.4%411,066 addresses
- Portland0.3%405,767 addresses
- Charlotte0.3%403,299 addresses
- Cleveland0.3%401,859 addresses
- Minneapolis0.3%401,781 addresses
- Atlanta0.3%382,936 addresses
- Bronx0.3%376,380 addresses
- Orlando0.3%375,715 addresses
- Saint Louis0.3%360,561 addresses
- Indianapolis0.3%359,922 addresses
- Seattle0.3%358,493 addresses
- Washington0.3%358,307 addresses
- Cincinnati0.3%345,688 addresses
- Springfield0.3%342,889 addresses
- Fort Lauderdale0.3%337,961 addresses
- Louisville0.3%335,398 addresses
- Fort Worth0.3%327,470 addresses
- Tucson0.3%323,787 addresses
- Tampa0.3%308,018 addresses
- Richmond0.3%305,618 addresses
- Milwaukee0.3%300,543 addresses
- San Francisco0.3%298,844 addresses
- Rochester0.3%298,195 addresses
- Saint Paul0.3%294,160 addresses
- Pittsburgh0.2%280,323 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 97.7% sits on the catalog’s own coverage range.
Higher coverage than 84% 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
2 ingestions1 authority contributed since Jan 2020.
| Observed | Ingested | Count | ID |
|---|---|---|---|
| 119,048,853 | e84435bf-fdae-464b-ad1b-45a5aca06bc2 | ||
| 119,016,289 | dd311395-716d-40ea-98f2-81aeadd883f8 |
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 City back in real time.
- Add
cityto a project. - Send an email, phone, or address to the project's append endpoint. The response carries City 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":{"city":"Houston"}}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.
- city
- 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