Birmingham, AL itemized gifts to DCCC

How Birmingham, AL meets DCCC on the FEC tape

$272,134 requires both keys at once: contributor city BIRMINGHAM with state AL, and recipient committee C00000935 disclosed as DCCC. LobbyVault keeps a Birmingham, AL city hub and a DCCC committee hub. Neither hub is this page. The city hub lists every committee that received itemized gifts storing this city string. The committee hub lists every city that gave to C00000935. This URL is only the intersection.

The packet does not name unique donors, contribution counts, or election cycles for this pair. $272,134 is a dollar aggregate. Treating it as a typical gift size or as a count of households is arithmetic the file does not support. BIRMINGHAM in Alabama is not Birmingham, Michigan. This URL is AL × C00000935 only. A sibling Birmingham, AL join to ALABAMA REPUBLICAN PARTY is a different committee ID and is not inside $272,134. Omaha also has a DCCC city-pac page; those dollars are omitted here.

The Birmingham, AL side of the DCCC join

Birmingham, AL's all-committee itemized book in this extract is $100,682,535. $272,134 is 0.27% of that book. A thin or moderate share is the usual result of comparing one committee with every other recipient on the city tape. The leftover $100,410,401 went to other committees under BIRMINGHAM, or sits outside this recipient filter.

The stored city sits in Alabama. Neighboring municipalities are not absorbed into BIRMINGHAM. Alabama campaign-finance pages include other cities. All FEC ties lists other city-committee pages. None of them converts $272,134 into spending by Birmingham, AL candidates or into independent expenditures by DCCC.

DCCC (C00000935) as the recipient key

C00000935 is disclosed as DCCC. This page does not list independent expenditures the committee made, operating expenditures it paid, or earmark destinations beyond the labeled recipient. $272,134 is itemized individual receipts storing city BIRMINGHAM and committee C00000935. Other cities giving to DCCC appear on the committee hub. Adding them here would break the city filter.

Quote the committee with its FEC ID so a similarly named filing is not swapped in. DCCC on another ID is a different page. This URL is Birmingham, AL × C00000935, not Alabama × C00000935 and not every spelling of BIRMINGHAM. If a live overlay at the committee path disagrees with $272,134, the overlay and FEC.gov control.

Share of the Birmingham, AL book

0.27% of $100,682,535 is $272,134 to DCCC (C00000935). That percentage describes overlap of two FEC groupings, not a finding that residents of Birmingham, AL as a group preferred this committee. Most of the $100,682,535 city book went to other committees. Even when 0.27% is a visible slice, the slice is still only the C00000935 filter.

The leftover $100,410,401 under the BIRMINGHAM city string went to other committees. The Birmingham, AL hub holds that remainder. The DCCC page holds receipts whose city field did not store BIRMINGHAM. Do not stack this cell with another city's gifts to C00000935; each join is its own filter.

What the Birmingham, AL × DCCC dollars omit

Unitemized federal gifts sit outside $272,134. Alabama state-office filings sit outside it. Independent expenditures are a different FEC file; the source note on this packet says these aggregates are not independent expenditures. City labels are filer-entered. PAC or joint-fundraising addresses that stored this city string follow the same rule as household streets.

Do not read $272,134 as proof that Birmingham, AL funded DCCC as a municipal act, or that the committee spent the money in Alabama. The join is two fields. Correlation is not causation. FEC individual contributions are not USAspending awards. This packet has no obligation dollars and no award counts. Do not add $272,134 to federal spending in Alabama.

How to cite the Birmingham, AL × DCCC join

Internal links go to Birmingham, AL, DCCC, Alabama campaign finance, and All FEC ties. Use those four doors. The city page holds the $100,682,535 book and the committees that received the leftover $100,410,401. The committee page holds C00000935 receipts from every city. All FEC ties collects neighboring pairs without mixing independent expenditures into this cell.

Researchers citing the join should keep both nouns in the sentence: Birmingham, AL and DCCC (C00000935). Dropping either noun turns this page into a restatement of a hub it is not. $272,134 is the only overlap this extract published. A later amendment wave can move a dollar without this file rewriting itself. Treat the live LobbyVault hub as newer than this packet snapshot. Cite $272,134, $100,682,535, 0.27%, leftover $100,410,401, and C00000935.

Questions

How much did Birmingham, AL donors give DCCC?

Itemized FEC individual contributions storing city BIRMINGHAM and recipient DCCC (C00000935) total $272,134 in this extract. That is the join, not Birmingham, AL's all-committee book of $100,682,535. These figures are not independent expenditures. Original reports remain on FEC.gov.

Does the Birmingham, AL total include every spelling of the city name?

No. BIRMINGHAM is the exact stored city string with state AL. Other spellings, abbreviations, and neighboring places are other keys and are omitted from $272,134. LobbyVault does not recode the field into a Census place. Use the Birmingham, AL hub for the all-committee book of $100,682,535.

What share of Birmingham, AL itemized money went to DCCC?

$272,134 is 0.27% of the $100,682,535 Birmingham, AL city book. The leftover $100,410,401 went to other committees under the same city string. Quote both dollars and the committee ID C00000935. Do not upgrade 0.27% into a ranking of civic preference.

Are the Birmingham, AL DCCC figures from FEC.gov?

Yes. The numbers are FEC.gov itemized contribution aggregates indexed on LobbyVault: $272,134 for the Birmingham, AL × C00000935 join and $100,682,535 for the city string. If a later extract or the committee overlay disagrees with this snapshot, the Commission's filing controls.