See who bought from a broadcast

The funnel is a mirror, not a live number

GET /broadcasts/stats mirrors the connected platform's own mass-message statistics page rather than computing sent/opened/replied/bought independently — it's a snapshot the engine captured, not a real-time count. Four honest states cover why the screen might look empty:

A blank funnel therefore isn't automatically "broken" — check the state before assuming a data problem.

Pulling the buyer list for one send

The one action here that actually reaches out is GET /broadcasts/stats/{mm_id}/buyers — a narrow, read-only request for who bought a specific broadcast, gated three ways: the feature flag, the broadcast belonging to this workspace (checked before any request goes out — an id that isn't yours is a plain 404, never a live lookup), and a rate limit of one request per hour per broadcast.

The call is asynchronous by design — the engine fetches this at a human pace, and a request that waited synchronously wouldn't survive a restart or a dropped connection. The response's state tells you where things stand:

• requested — queued, the engine hasn't fetched it yet;
• ok — a buyer list is ready, with shown out of the connected platform's own total count;
• failed — the last attempt didn't land; wait out the hourly cooldown before it's retried.

Once a list is ready, it keeps refreshing in the background on the same hourly cadence — you don't lose what's already been fetched while a newer pull is in flight.

What's next

• Send a broadcast campaign — where the campaign this funnel describes came from.