datasets real and made-up data to practise on
Datasets
Data for the Playground, Database Lab and Performance Lab. Pick one and open its files.
Real complaints people sent the U.S. CFPB in 2024 about credit reports, debt collection and banks.
600 complaints1 tableJan 2024 – Dec 2024
what to watch for
Tricky rows
- ZIP codes partly masked for privacy (e.g. "891XX")56 rows
- Complaints with no sub-issue6 rows
- Several tags in one text field ("Older American, Servicemember")1 rows
- Company did not respond in time (timely = "No")1 rows
files
Open a file to see what one row means, its columns and a preview. Open in Playground starts a new file there with code that loads it.
complaints600 rows · 15 columns · CSV
One complaint, as the CFPB published it. Most are about credit reports, as in the full database.
In your code: data/complaints.csv
- complaint_id
CFPB complaint ID
- date_received
When the CFPB received it (date and time as text, UTC)
- product
Financial product
- sub_product
More specific product
- issue
What went wrong
- sub_issue
More specific issue
- company
Company the complaint is about
- state
Consumer’s state
- zip_code
Consumer’s ZIP code; partly masked for small areas
- tags
Older American and/or Servicemember
- submitted_via
Web, Phone, Referral, …
- date_sent_to_company
When the CFPB sent it to the company (date and time as text, UTC)
- company_response
How the company closed it
- company_public_response
Company’s optional public statement
- timely
Yes if the company responded within 15 days
data/complaints.jsonl600 records · JSON Lines
One complaint, as the CFPB published it. Most are about credit reports, as in the full database.
In your code: data/complaints.jsonl
data/api/complaints-2024-01-15.json600 records · JSON
One complaint, as the CFPB published it. Most are about credit reports, as in the full database.
In your code: data/api/complaints-2024-01-15.json