How the numbers are made, and where they come from
This page describes only what is true today. Finder reports run on written rules. Counts of people, households, jobs, and businesses come only from the public releases listed here, loaded into our database and checked first.
01How a finder report is made today
- Your description is read with a dictionary of words and patterns, to work out what kind of business you run and the words you use for your customers and what you sell.
- Your answers pick audience patterns from a library written for different kinds of businesses, and each pattern is scored against your answers.
- Your goal reweights those scores: which audience traits count most, which channels rise or fall, how the budget leans, which actions are eligible, and the order of the sections.
- Channels are ranked for each audience, and the budget is split across them from their scores and the range you gave.
- The report is compared with one built from the same answers and no goal, and the differences are listed in "What your goal changed".
- No AI model is involved. The rules are written by people.
- The same answers always give the same report.
- The report is built on the uraudience server from your answers, and saved there with them at its own address. Without an account, only the browser that made it can open it. With an account, you can open it on any device you sign in on.
- Shares and scores in a finder report come from these rules, not from counts of real people, and are labeled as estimates with a confidence mark.
02The label on every figure
Every number about people, households, businesses, or money carries one of four labels. The mark next to it differs by shape, not color, so it reads in grayscale, and a mark is never shown without its words.
- Census count
- A number read straight from a loaded Census Bureau release, shown with its margin of error. It is used only when every filter comes from one published table. A number from the Bureau of Labor Statistics carries the label BLS count instead.
- Combined estimate
- Two or more published numbers combined, which makes the result an estimate even though each part is real. Always shown as a range.
- Model estimate
- An estimate that rests on one of our own assumptions, such as how many people in a group cook at home. Always shown as a range, never a single number.
- From your inputs
- Something you told us, such as your budget. It carries no confidence ticks, because it is yours.
The confidence scale
Five ticks from low to high. The marker shows how much to lean on a figure. This one sits at three.
How ticks are set for a Census count
- Five ticks: the margin of error is small, at most 5 percent of the number, measured as the coefficient of variation.
- Four ticks: at most 12 percent.
- Three ticks: at most 20 percent.
- Two ticks: at most 40 percent.
- One tick: more than 40 percent.
These cutoffs are uraudience's own rules, not a Census Bureau standard. Estimates lose ticks for every join and assumption they rest on.
03Public sources loaded today
These are the releases the uraudience database holds right now. The list is read from the database, so it changes when a release is loaded or retired. In the audience builder, people and household counts use the American Community Survey, the Gazetteer, and the relationship files; job titles use BLS Occupational Employment and Wage Statistics and O*NET; skills use O*NET; and business counts use County Business Patterns and ZIP Code Business Patterns. None of these downloads needs an API key.
| Release | Vintage | Released | Loaded | What it covers |
|---|---|---|---|---|
| American Community Survey 5-year estimatesU.S. Census BureauRead the release notice: American Community Survey 5-year estimates | 2020 to 2024 | January 29, 2026 | September 11, 2026 | People and households by sex, age, education, language spoken at home, the time people leave for work, household income, occupation, and industry, for the nation, each state, cities and towns (Census places), and ZIP code areas (ZCTAs) |
| County Business Patterns and ZIP Code Business PatternsU.S. Census BureauRead the release notice: County Business Patterns and ZIP Code Business Patterns | 2023 | June 26, 2025 | September 11, 2026 | Business locations by industry and number of employees, for each state and county, and by ZIP code |
| Census Gazetteer ZIP Code Tabulation Areas fileU.S. Census BureauRead the release notice: Census Gazetteer ZIP Code Tabulation Areas file | 2024 | August 30, 2024 | September 11, 2026 | The center point of each ZIP code area, for searches within a radius |
| Occupational Employment and Wage StatisticsU.S. Bureau of Labor StatisticsRead the release notice: Occupational Employment and Wage Statistics | May 2025 | May 15, 2026 | September 11, 2026 | How many people work in each occupation, for the nation and each state |
| O*NET 31.0 DatabaseU.S. Department of Labor, Employment and Training AdministrationRead the release notice: O*NET 31.0 Database | 31.0 | August 25, 2026 | September 11, 2026 | Job titles, and the skills and software used in each occupation, for searching by job |
| 2020 ZIP Code Tabulation Area relationship filesU.S. Census BureauRead the release notice: 2020 ZIP Code Tabulation Area relationship files | 2020 | December 9, 2021 | September 11, 2026 | Which cities and towns each ZIP code area overlaps, and how much of its land falls in each |
When the American Community Survey release was loaded, its state totals matched the national total exactly, 50 sampled figures matched the Census Bureau’s data API, and three more were checked by hand against data.census.gov.
04The tables behind a count
People and household counts come from the American Community Survey 5-year Summary File, stored for the nation, each state, every Census place, and every ZIP code area, with the margin of error for each figure. Business counts come from County Business Patterns for states and counties, and ZIP Code Business Patterns for ZIP codes. At the ZIP code level the Census Bureau withholds many counts by business size, so that no single business can be picked out.
| Table | What it covers | What it counts | Group |
|---|---|---|---|
| B01001 | Sex by age | people 18 and over | People and households |
| B15001 | Sex by age by educational attainment | people 18 and over | People and households |
| B19001 | Household income | households | People and households |
| B19037 | Age of householder by household income | households | People and households |
| B16007 | Age by language spoken at home | people 18 and over | People and households |
| B08302 | Time leaving home to go to work | workers 16 and over who commute | People and households |
| C24010 | Sex by occupation | employed people 16 and over | Work |
| C24030 | Sex by industry | employed people 16 and over | Work |
| C24050 | Industry by occupation | employed people 16 and over | Work |
| CBP and ZBP | County Business Patterns and ZIP Code Business Patterns | business locations (establishments, not companies) | Businesses |
05The assumptions we state
Every estimate rests on one or more of these, and a figure’s details list the ones it uses, in these words.
- Where two filters come from different Census tables, we assume they are unrelated inside each small area, then add the areas up. Real people are not always that independent, so the result is shown as a range.
- For whole states or the nation, we assume the filters are unrelated across the whole area. That loses local patterns, so confidence drops one tick.
- Household income is published for households, not people. We apply each area's household income mix to its adults.
- The Census publishes this table in broad age bands, so your age range was widened to the nearest published bands.
- Counted by ZIP Code Tabulation Area (ZCTA), the Census Bureau's version of a ZIP code area. Most ZIP codes have one. PO box and single-building ZIP codes do not.
- A ZIP code area is included when its Census center point (the internal point) falls inside the radius.
- The margin of error for a sum of Census cells is estimated as the square root of the sum of the squared cell margins, the approximation the Census Bureau's ACS handbook describes.
- Some Census cells in this area are controlled estimates: the Census Bureau fixes them to its official population estimates and publishes no margin of error for them. They add nothing to the margin of error shown.
- Two tables count slightly different groups of people, for example employed people 16 and over and adults 18 and over, so combining them is approximate.
- Interest and behavior rates are uraudience estimates, not measurements, and are deliberately wide.
- This interest rate comes from a published survey and is applied as if it were the same everywhere.
- A job title's share of its occupation group comes from BLS figures for the whole state, applied to smaller areas.
- BLS counts jobs where people work; the Census counts people where they live.
- People are counted through the occupations where O*NET rates the skill as important, not through their own skills.
- County Business Patterns counts business locations (establishments), not companies. A chain with forty stores counts forty times, and businesses with no employees are not included.
- A city is counted through the ZIP code areas that approximate it, so the edges do not match the city line exactly.
- Cost per thousand views is a uraudience benchmark range, not a quote. Ad platforms set prices by auction.
- Assumes each person sees your ad a set number of times a month, shown next to the estimate.
- Assumes only part of the Census audience can be reached on each platform. The share is a uraudience estimate.
- Finder audiences come from uraudience rules matched to your description. Their shares are estimates, not measurements.
- BLS publishes a relative standard error for each job count. The margin shown is 1.645 times the standard error, the same 90 percent level the Census Bureau uses, added across states and job titles as the square root of the sum of squares.
- ZIP Code Business Patterns does not publish every size class for every area. Where one is missing, the area’s published count for that industry is split across the missing size classes in the proportions its state publishes. That part is an estimate, shown as a range of half of it either way.
06Words we use carefully
- Sex
- The Census asks about sex, not gender identity, so the filter is called Sex. Ad platforms use their own gender settings.
- ZIP code areas (ZCTAs)
- ZIP Code Tabulation Areas, the Census Bureau’s version of ZIP code areas. Most ZIP codes have one. PO box and single-building ZIP codes do not.
- City
- A Census place: a city, town, village, or census-designated place, shown with the Census name, such as "Evanston city".
- Business locations
- Establishments, not companies. One company with three shops is three business locations.
- Center point
- The Census internal point of a ZIP code area. A radius includes an area when its center point is inside the radius.
07How your data is handled
As the site works today. The privacy policy says the same in more words. Every cookie the site sets is in this table, and there are no others.
| What | Where it lives | How long |
|---|---|---|
| Your finder answers | This browser only, in local storage under the name ua_find_draft. This is not a cookie. The answers are sent to uraudience only when you ask for your report. | Until you clear this site’s data in your browser |
| Your audience builder draft | This browser only, in local storage under the name ua_build_draft. This is not a cookie. Your filters are counted in your browser. The places, job titles, and skills you search for and pick are sent to uraudience to look up their public figures, and are not saved in the database. The draft also keeps the name you type to save it and, when you opened it from a report, which report segment it came from. When you save an audience, the audience (its name, filters, and size) is saved in your account, where you and the site owner can read it. | Until you clear this site’s data in your browser |
| Your report, with the answers it was built from | The uraudience database at Supabase, in Amazon Web Services’ us-east-1 region (Northern Virginia, United States). The site owner can read it, and the answers it was built from. | Until it is deleted. Deleting a report from the site is not built yet. |
| Report cookie (fn_claim) | This browser, when you make a report without an account. It holds the keys (claim tokens) of your last ten reports at most, so only this browser can open them. Scripts on the page cannot read it. | 30 days from the last report you made, or until you sign up or sign in from one of those reports, which moves them all into your account and removes the cookie |
| A report made without an account, after that | It stays in the database. Once the report cookie is gone you cannot open it from the site, but the site owner still can. Nothing deletes it automatically yet. | Until it is deleted by hand |
| Your account: email address, password, and trial status | Supabase’s sign-in service and the same database, in the same region. The password is stored only as a one-way hash, never as typed. | Until the account is deleted. Deleting an account from the site is not built yet. |
| Who can read your answers and your report | The site owner, who can read every saved report and the answers it was built from, including reports made without an account, on a private page only the owner can open and in the database itself. Nobody else can open your report from the site. | As long as the report is kept |
| A public example made from your report, only if you tick the box | A separate, frozen copy in the same database, made on the server, with the business name, the description, the service area, the ZIP code, the radius and any city, the website, social accounts, customer notes, and anything else you typed, including every place the report repeats those words blacked out. What stays visible is the business type, the audiences, the channels, the plans, and the numbers with their labels. The site owner checks the copy, decides whether to publish it in the example gallery, and can unpublish it at any time. | Until it is unpublished and removed, or until you untick the box on your report while signed in, which deletes it at once |
| Your tactics checklist: the status, owner, and due date you save for each tactic | The same database, under your account | Until the report it belongs to is deleted |
| Sign-in cookies (names that start with sb- and end in auth-token, sometimes split into parts ending in .0 and .1) | This browser, while you are signed in. Set by Supabase’s sign-in library. Scripts on the page can read them. | Until you sign out. The browser keeps them for at most 400 days, renewed as you use the site. |
| Sign-in check cookies (names that start with sb- and end in code-verifier) | This browser, when you sign up or ask for a password reset. Each holds a random one-time value that lets Supabase check the sign-up or the reset link. None holds your password. | Until you sign out, or until the reset link is used. The browser keeps them for at most 400 days. |
| Abuse limits | The server’s memory, never the database: reports made per IP address without an account (20 an hour) or per account (60 an hour), refused promo codes per account (5 an hour), and data lookups per IP address (120 a minute). | At most an hour, and gone when the server restarts |
| Analytics, advertising, and tracking cookies | None. The site sets none, and loads no analytics or advertising scripts. | Not applicable |
| The contact form | Not connected, so nothing typed into it is sent or saved | Not applicable |
| Request logs | Vercel, the host, records requests as part of serving the site, such as your IP address, your browser, and the pages you ask for | Kept by Vercel under its own policy |
Getting your data removed
There is no way to delete a report or an account from the site yet. There is also no contact inbox yet, so there is no way to ask for removal from this site today. This page will say when there is. Clearing this site’s data in your browser removes your finder answers and the report cookie. That makes a report made without an account unreachable, but it does not delete it from the database.
08Export formats, and when we last checked them
A file for an ad platform ships only where that platform's own documentation confirms its format. Everything else goes on the platform's spec sheet, which lists the settings to enter by hand. Every format below was last checked against the linked page on September 11, 2026.
| Format | Ships as | What it holds | Checked |
|---|---|---|---|
| Google Ads Editor location file | A file | A two-column CSV (Campaign, Location) with one radius per row, written as distance, latitude, and longitude. Only for radius audiences: Google does not document the place-name format, so states, cities, and ZIP codes go on the spec sheet. | September 11, 2026 |
| Google Ads demographics | Spec sheet only | Age ranges, gender, and household income tiers, listed for you to choose in Google Ads. | September 11, 2026 |
| Meta targeting JSON | A file | Ages, gender, and the country or a radius, in the Marketing API basic targeting fields. Only for the whole country or a radius: other places need Meta location keys. | September 11, 2026 |
| Meta Ads Manager bulk import | Spec sheet only | Its template comes from inside Ads Manager, so its columns are not generated here. The spec sheet lists the settings. | September 11, 2026 |
| TikTok targeting | Spec sheet only | TikTok documents only some bulk import columns publicly; the full template is inside Ads Manager. The spec sheet lists ZIP codes, ages, gender, languages, and interests in words. | September 11, 2026 |
| Google Customer Match template | A file | Header-only CSV: Email, Phone, First Name, Last Name, Country, Zip. | September 11, 2026 |
| Meta customer list template | A file | Header-only CSV: email, phone, fn, ln, zip, ct, st, country, doby, gen, each a column header on Meta’s formatting page. | September 11, 2026 |
| TikTok customer file templates | A file | Two header-only CSV files, one headed Email and one headed Phone. | September 11, 2026 |
| Housing, employment, and credit rules | Spec sheet only | The warning on each spec sheet, from Google’s policy and Meta’s Special Ad Categories rules. | September 11, 2026 |
09Credits and licenses
Census data: U.S. Census Bureau, from the American Community Survey, County Business Patterns, ZIP Code Business Patterns, the Gazetteer files, and the relationship files. uraudience uses Census data but is not endorsed or certified by the Census Bureau.
Occupation counts: U.S. Bureau of Labor Statistics, Occupational Employment and Wage Statistics.
This page includes information from the O*NET 31.0 Database by the U.S. Department of Labor, Employment and Training Administration (USDOL/ETA). Used under the CC BY 4.0 license. uraudience has modified all or some of this information. USDOL/ETA has not approved, endorsed, or tested these modifications. O*NET® is a trademark of USDOL/ETA.