Associated post office name

Text

Name of the USPS post office serving the individual's mailing address. Known or imputed for 119.5 million addresses — 99.6% of the addresses Faraday knows.

At a glance

Coverage today
99.6%
Typical coverage
98.5%
Addresses with a value
119.5M
Share in largest category
0.8%
Most values come
from the address
When latest collection arrived
Nov 11, 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.

Share by category

n = 119,474,652

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
HOUSTON
0.8%
CHICAGO
0.7%
BROOKLYN
0.7%
LOS ANGELES
0.6%
NEW YORK
0.6%
SAN ANTONIO
0.5%
MIAMI
0.5%
LAS VEGAS
0.5%
PHILADELPHIA
0.5%
DALLAS
0.4%
COLUMBUS
0.4%
DENVER
0.4%
PHOENIX
0.4%
JACKSONVILLE
0.4%
SAN DIEGO
0.4%
AUSTIN
0.4%
MINNEAPOLIS
0.3%
PORTLAND
0.3%
CHARLOTTE
0.3%
CLEVELAND
0.3%
Distinct categories
99+
Share in largest category
0.8%
Share in top 3 categories
2.2%

Every category

99+ categories

The 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%975,076 addresses
  • CHICAGO0.7%875,498 addresses
  • BROOKLYN0.7%799,966 addresses
  • LOS ANGELES0.6%676,911 addresses
  • NEW YORK0.6%661,029 addresses
  • SAN ANTONIO0.5%636,647 addresses
  • MIAMI0.5%632,708 addresses
  • LAS VEGAS0.5%599,564 addresses
  • PHILADELPHIA0.5%578,943 addresses
  • DALLAS0.4%498,987 addresses
  • COLUMBUS0.4%491,606 addresses
  • DENVER0.4%475,330 addresses
  • PHOENIX0.4%469,994 addresses
  • JACKSONVILLE0.4%463,170 addresses
  • SAN DIEGO0.4%427,724 addresses
  • AUSTIN0.4%424,492 addresses
  • MINNEAPOLIS0.3%415,637 addresses
  • PORTLAND0.3%413,890 addresses
  • CHARLOTTE0.3%410,856 addresses
  • CLEVELAND0.3%408,526 addresses
  • ATLANTA0.3%394,244 addresses
  • BRONX0.3%387,424 addresses
  • ORLANDO0.3%382,293 addresses
  • INDIANAPOLIS0.3%367,875 addresses
  • SEATTLE0.3%367,198 addresses
  • SAINT LOUIS0.3%366,812 addresses
  • WASHINGTON0.3%366,712 addresses
  • CINCINNATI0.3%350,056 addresses
  • SPRINGFIELD0.3%348,870 addresses
  • FT LAUDERDALE0.3%342,796 addresses
  • LOUISVILLE0.3%341,456 addresses
  • FORT WORTH0.3%335,080 addresses
  • TUCSON0.3%331,962 addresses
  • TAMPA0.3%312,938 addresses
  • RICHMOND0.3%312,484 addresses
  • MILWAUKEE0.3%305,802 addresses
  • SAN FRANCISCO0.3%303,522 addresses
  • ROCHESTER0.3%303,056 addresses
  • SAINT PAUL0.3%299,680 addresses
  • PITTSBURGH0.2%285,844 addresses

Category shares over time

0.8% (largest)

The 5 largest categories, each followed across 12 collections. Estimated from a 1% sample of addresses.

Nov 2024Apr 2025Oct 2025Dec 2025Mar 2026Jun 2026Aug 2026
HOUSTONBROOKLYNCHICAGOMIAMILAS VEGAS

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

99.6% today

Share of addresses holding a value at each monthly snapshot. A value carries forward for one year.

Jul 23Nov 24Mar 25Jul 25Dec 25Apr 26Nov 26

How we arrive at a value

Latest collection: 119,554,311 addresses

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 99.6% sits on the catalog’s own coverage range.

catalog min 0%max 100%

Higher coverage than 92% of address-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 addresses it carried. Gaps are real — collection is periodic, not continuous.

Nov 11, 2026
when latest collection arrived
Aug 1, 2026
data as of
3 days
since the latest collection arrival
every two months
median collection cadence
Nov 24Apr 25Oct 25Dec 25Mar 26Jun 26
Data as of

Change between collections

How much values move between collections. Income or life events should move; heavy change in something steady can mean noisy data.

0.0%

of addresses changed value between the two most recent collections — 140978.1× steadier than the catalog median of 23.5%.

Contribution ledger

15 ingestions

1 authority contributed since Jul 2023.

ObservedIngestedCountID
264,508,7797eb390da-8602-4a0d-870b-33a136ac6e0b
263,433,64974d6c94c-8e2b-48fe-a704-50c99ad3cdde
266,506,942c5492806-a892-460e-aba1-ee78ffb29c5b
264,096,9771181277b-b751-4a59-aae1-101fa3f55375
264,777,400af53c569-4fe2-4282-975b-4cbf5f85692d

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 Associated post office name back in real time.

  1. Add associated_post_office_name to a project.
  2. Send an email, phone, or address to the project's append endpoint. The response carries Associated post office name 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":{"associated_post_office_name":"HOUSTON"}}
Get it by APIAppend to a fileRead the API docs

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.
associated_post_office_name
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.
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.
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
API reference