Export Broadcast Results as CSV

Every broadcast can be exported as a CSV with one row per recipient, showing status, any Meta error code, send and reply timestamps, retry count and the reason for that status, streamed directly so a campaign of any size exports reliably. This article covers what is in the file, how to get it, and what it does not include.

Before you start

• You need the "View broadcasts" permission, which most roles already have since it is a read action rather than a send or create action.
• The export downloads directly from your browser as a .csv file; no separate export job or waiting period is needed.
• Decide what you actually need the data for; the export is the raw per-recipient record, not a summary report, so pair it with the campaign detail page's stat tiles for a quick top-line view.

Steps

1. Open the campaign's detail page. From Broadcasts, click into any campaign, whether it is still sending or already finished.

2. Click Export CSV in the action bar. It is always available, regardless of the campaign's current status.

3. Let the file download. Your browser saves a .csv file named after the campaign; the download starts immediately as the server streams the data.

4. Open it in a spreadsheet tool. Excel, Google Sheets or any CSV-compatible tool works. Sort or filter by the Status column to isolate delivered, failed, or suppressed recipients, or by Error code to group failures by their specific cause.

5. Re-export later if you need an updated snapshot. Running Export CSV again on the same campaign, at a later time, produces a fresh file reflecting whatever the recipients' statuses are at that moment, useful for a campaign still collecting delivery and read receipts.

What you will see

The downloaded file has one header row followed by one row per recipient, in the order VGraple CRM's internal recipient IDs were created. Every recipient the campaign ever queued appears, including suppressed, cancelled and pending rows, not only the ones that were successfully sent, so the file is a complete record of the campaign's audience, not just its successes.

What is actually in the file?

Revenue and click data are deliberately not part of this file. Both are visible elsewhere, revenue as a stat tile on the campaign detail page and in the multi-campaign Compare view, clicks as a stat tile and a filterable tab on the recipient table, but neither is currently exported as a CSV column. If you need revenue or click data alongside the delivery record for offline analysis, cross-reference the campaign detail page's figures with this export manually for now.

How does the export handle a very large campaign without failing?

An earlier, simpler approach to this kind of export loads every recipient row, every associated contact, and every related delivery message for the whole campaign into memory before writing anything, which on a 50,000-recipient campaign can mean hundreds of megabytes held in the same process serving the rest of the application, a real risk of the export itself slowing down or crashing unrelated requests. VGraple CRM's export instead streams the response: it pages through recipients 1,000 at a time using a keyset cursor (ordering by recipient ID rather than an offset, which stays fast no matter how deep into a large campaign it gets), writing each page's rows to the response as soon as they are fetched, and moving to the next page only once the previous one has been sent. Memory usage stays flat regardless of whether the campaign has 50 recipients or 50,000, and the download begins immediately rather than after a long wait while the whole file assembles server-side.

Settings and options

How does the export's Status column relate to what you see in the app?

The export deliberately mirrors the same resolution logic the recipient table and the funnel use, rather than dumping the raw database column value. A recipient whose row is still literally marked "sent" but whose linked delivery message has since moved to "delivered" or "read" via webhook is shown in the export with that more current status, not the stale original one, since that would otherwise disagree with what the exact same recipient shows inside the app at the same moment. This consistency matters when you are reconciling an exported file against what you see live in VGraple CRM, whether for a client report or an internal audit, since the two should never tell a different story about the same campaign.

Troubleshooting

Why does the export include suppressed and pending rows, not just successful sends?

A file that only listed successful sends would answer "who did we reach" but hide "who did we intend to reach and why did some of them not get the message," which is usually the more useful question when auditing a campaign afterward. Because every recipient VGraple CRM ever queued for the campaign appears in the export, including suppressed rows with their specific reason and pending rows for a campaign still in progress, the file works as a complete audit trail on its own, without needing to cross-reference the recipient table in the app to understand the full picture. Filtering by Status in your spreadsheet tool after the fact gets you the same views the in-app filter tabs offer, just offline and exportable to whatever reporting tool your business already uses.

Related reading

Cross-reference an export with recipient statuses explained for exactly what each status column value means, and see tracking link clicks and seeing revenue per broadcast for where that data lives instead.