ActBlue CSV Export Columns Explained for Finance Teams

Complete field-by-field guide to ActBlue CSV export columns including donation IDs, amounts, donor info, and metadata for campaign finance teams.

ActBlue CSV exports contain every contribution record your campaign or organization has received through the platform. These files arrive with 30+ columns, some clearly labeled, others cryptic. For finance directors juggling compliance deadlines and donor outreach, understanding what each column contains—and which ones you actually need—saves hours of confusion and prevents costly data errors.

This guide decodes every standard ActBlue CSV column in plain language. You'll learn which fields matter for FEC filing, which ones help identify major donors, and how to spot data quality issues before they become compliance headaches.

What columns appear in a standard ActBlue CSV export?

ActBlue CSV exports follow a consistent structure across all accounts, though the number of populated columns varies based on your contribution history and payment methods. Every export includes core transaction data (contribution ID, amount, date), donor identification fields (name, email, address), and payment processing metadata (status, payment type, transaction ID).

The Report Builder tool, introduced by ActBlue to give campaigns more control over their data exports, maintains this same column structure while allowing you to filter by date range, contribution type, or specific forms. Regardless of how you generate the export, the underlying field definitions remain consistent.

ActBlue's Report Builder provides a flexible way to export contribution data with consistent column formatting across all export files

ActBlue (actblue.com)

Every export uses UTF-8 encoding and includes a header row with column names. Most columns contain text values, though amount fields use decimal numbers and dates follow YYYY-MM-DD format. Empty cells appear as blank rather than "NULL" or other placeholder text.

How are donor information columns structured?

The donor identification section contains nine to twelve columns depending on whether you've collected phone numbers and mobile opt-in status. First Name and Last Name appear as separate columns, not combined. Email appears exactly as the donor entered it—watch for typos and formatting inconsistencies that complicate deduplication later.

Address fields split across five columns: Address Line 1, Address Line 2, City, State, and ZIP. Address Line 2 remains blank for most contributions. State uses two-letter postal codes. ZIP contains five-digit codes for US addresses, though international contributions may show different formats.

Phone appears in various formats—some donors use parentheses and hyphens, others enter digits only. ActBlue doesn't enforce a standard format here, so you'll need to normalize phone numbers before importing to most CRM systems. For detailed cleaning workflows, see our comprehensive ActBlue data cleaning guide.

The Mobile Opt-In column shows "Yes" or blank, indicating whether the donor consented to text message outreach. This field appeared in exports starting in 2022, so older data won't have it.

What do the contribution details columns tell you?

Amount shows the contribution value in dollars, formatted as a decimal (25.00, not $25). This is the net amount after ActBlue's processing fees, which appear separately in the Fees column. Receipt ID provides a unique identifier for each transaction—you'll use this when cross-referencing with bank deposits or resolving donor inquiries.

Contribution Date uses YYYY-MM-DD HH:MM:SS format in Eastern Time, regardless of where the donor is located. This matters when determining which reporting period a contribution falls into for FEC filing.

The Recurring column contains "Recurring" for recurring contributions or "One-time" for single donations. Recurring Total shows the full committed amount for recurring pledges (blank for one-time gifts). To understand how these values interact with refunds and cancellations, read our guide on how refund columns work in ActBlue exports.

Fundraising Page indicates which ActBlue form the donor used. If you run multiple campaigns or test different landing pages, this column helps attribute contribution sources. However, it only shows the final form—if a donor clicked through multiple pages, you'll only see where they completed the transaction.

What payment processing columns should you monitor?

Payment Method shows the funding source: "Credit Card," "ACH/Bank Transfer," or occasionally "PayPal" for older transactions. Card Type provides additional detail for credit cards—"Visa," "Mastercard," "American Express," or "Discover." These columns help identify patterns if certain payment types have higher refund rates.

Transaction ID is ActBlue's internal processing identifier. You won't need this for routine work, but support teams may ask for it when investigating failed transactions or processing errors.

Status indicates whether the contribution processed successfully. Most rows show "Completed," meaning funds cleared and arrived in your account. "Failed" indicates the payment didn't go through—these rows have amount values but didn't generate revenue. "Refunded" marks contributions that processed but were later returned to the donor. See donation type field values for how refund status interacts with recurring contribution tracking.

How do employer and occupation fields work?

Employer and Occupation columns contain donor-entered text, not standardized categories. ActBlue doesn't validate these fields against any database, so expect inconsistent formatting: "Teacher" vs. "teacher" vs. "Elementary School Teacher" all appear as separate values in your data.

These fields are optional at checkout unless you've configured your form to require them. Many donors skip them, leaving blank cells. For contributions under $200, this usually doesn't affect FEC compliance. For itemized contributions, you'll need to gather this information through follow-up emails if it's missing.

Political committees must collect and report employer and occupation information for individual contributors whose aggregate contributions exceed $200 in an election cycle

Federal Election Commission (fec.gov)

What compliance and refund data do the exports include?

The Refund Amount column shows dollars returned to the donor, blank if no refund occurred. Refund Date indicates when you processed the return. These columns work together—you'll have a Refund Amount without a corresponding original contribution row if that contribution happened before your export date range.

Compliance Flags appears in some export versions but remains blank for most campaigns. ActBlue uses this internally to mark contributions requiring additional review, but the specific codes aren't documented publicly. If you see values here, contact ActBlue support for clarification.

Line Number is a sequential counter ActBlue adds during export generation. It doesn't connect to anything meaningful—ignore it unless you're troubleshooting export formatting issues.

What problems appear most often in ActBlue CSV files?

Missing email addresses affect 2-5% of contributions, typically from donors who unchecked the "send me updates" box. These contributions are valid, but you can't add those donors to email lists without additional outreach.

Encoding issues appear when you open CSVs in Excel without specifying UTF-8. Special characters in donor names (accents, apostrophes, em dashes) display as garbage symbols. This doesn't corrupt the underlying data—re-import using UTF-8 encoding and the characters render correctly.

Blank employer/occupation fields become compliance issues only for itemized contributions. Run a filter to identify donors whose total contributions exceed $200 but have missing employment data, then prioritize those for follow-up.

Date format confusion happens when Excel auto-converts dates to different formats based on your regional settings. Always verify the Contribution Date column displays correctly before performing date-based calculations or filters.

Kit Workflows handles these inconsistencies letting you quickly and easily normalize data with saved workflows. Start your 14-day free trial to see how pre-built workflows clean your ActBlue data in minutes instead of hours.

Step-by-Step: How to identify and interpret each column in a standard ActBlue CSV export file

Download the export from ActBlue. Log into your ActBlue account, navigate to Reports, and generate a CSV export for your desired date range using the Report Builder tool.

Open the file in a spreadsheet application. Use Google Sheets or specify UTF-8 encoding in Excel to prevent character rendering issues with donor names containing special characters.

Locate the header row. The first row contains column names—these labels identify what data each column contains and remain consistent across all ActBlue exports.

Identify the Receipt ID column. This unique transaction identifier appears in every export and serves as your primary key when joining data across multiple exports or matching contributions to bank deposits.

Review donor identification columns. First Name, Last Name, Email, Address Line 1, City, State, and ZIP contain the core donor contact information you'll use for outreach and FEC itemization.

Examine contribution detail fields. Amount, Contribution Date, Recurring status, and Fundraising Page tell you what the donor gave, when they gave it, whether it's a one-time or recurring commitment, and which form they used.

Check payment processing columns. Payment Method, Status, and Transaction ID indicate how the donor paid and whether the transaction completed successfully or requires follow-up.

Verify compliance-related fields. Employer, Occupation, Refund Amount, and Refund Date contain data you'll need for FEC reporting and contribution reconciliation.

How should you organize and use ActBlue export data?

Download exports weekly during active fundraising periods and monthly otherwise. Regular exports make it easier to track recurring contribution performance and identify processing issues before they affect multiple billing cycles.

Store raw CSV files with date-stamped filenames (actblue_export_2026-03-20.csv) in a dedicated folder. Never overwrite original exports—you'll want to compare data across periods and reprocess if cleaning workflows change.

Import into a database or CRM rather than managing data in spreadsheets. Spreadsheets work for quick analysis of small datasets, but searching, deduplicating, and generating compliance reports across thousands of contributions requires proper database tools.

Create separate views for one-time vs. recurring contributions. These segments have different retention patterns and require different outreach strategies. The Recurring column makes this segmentation straightforward.

Automate donor deduplication using email as your primary matching key, then last name + ZIP as a secondary match. Don't rely on exact name matches—donors enter nicknames, legal names, and spouse names inconsistently.

Document your cleaning process. When you standardize occupation categories or normalize phone numbers, record the transformation rules you applied. FEC audits may require you to explain how raw ActBlue data became your filed contribution records.