The 2024 U.S. reporting snapshot
The figures below come from the FTC’s Consumer Sentinel Network Data Book and March 2025 release. They describe reports received in 2024.
Reported fraud losses, rounded by the FTC.
Reported losses under the FTC’s imposter-scam category.
Using those rounded amounts, imposter scams accounted for roughly 24% of reported fraud dollars. The denominator is reported fraud losses. The ratio does not estimate the share of scams that involved a stolen photo, synthetic media, or any specific platform.
What the dataset measures
Sentinel aggregates submissions to the FTC and participating organizations. People and businesses who do not report are missing from the snapshot. The FTC’s roughly 6.5 million reports also include identity theft and other consumer issues. Use category-specific counts and comparable collection windows when drawing comparisons.
For an editorial case or industry comparison, record the agency, category definition, geography, reporting window, and unit. Keep complaints, reported losses, and verified incidents as distinct measures. Aggregate sources cannot establish whether a particular account committed fraud.
From data to action
How to read a fraud table
Start with the unit. A count of reports answers a different question from reported dollars lost. A category can have many complaints with modest amounts, while a smaller category can account for more dollars. Check whether the denominator is all reports, fraud reports, or only reports that include a dollar loss.
Look at the data note before comparing two years. A change in reporting coverage, classification, or how people reach the reporting system may affect the totals. If an agency adds categories or revisions, explain whether the older figures were recalculated. Use the same scope and time window before interpreting a change. FTC’s 2024 Data Book and notes.
What an incident reviewer can use
Aggregate fraud figures show why reporting matters. They cannot tell you whether one account or photo is involved. Preserve the public URL and the claim that was made. When a payment was requested, retain the payment channel and transaction reference privately. Avoid adding faces or personal details that do not establish the reported behavior.
For a business briefing, track reported URLs, takedowns confirmed by the host, and customer reports about payment requests as distinct measures. Define what counts as a repeat incident before aggregating. Keep complaint totals separate from observed losses or recovered funds. This makes a follow-up report useful even when the original link is no longer available.

