TEASEDocs
ProductsClubHow-to

Build a reusable fan segment for broadcasts

Save a live audience filter once — "whales, active 30 days" — and reuse it across multiple campaigns instead of re-typing it.

Saved segments ("Lists") live under /api/admin/broadcasts/segments rather than a general /fans/segments — deliberately, so they sit behind the same 1:1 broadcasts capability as the rest of the broadcast screen instead of a looser fan-browsing right. Up to 100 live segments per workspace.

Filters are live, not a snapshot

A segment is a saved filter definition, not a frozen list of fan ids — its membership is recomputed every time it's read. You can filter on subscription status and type, auto-renew, spend (a floor, a ceiling, or a rolling "$X+ in N days" window), purchase count, recency of last purchase or silence, refund count, and acquisition source or country.

POST /broadcasts/segments/preview gives you a live match count as you tune the filter, before you save anything.

Saving and naming

Save with POST /broadcasts/segments. The panel derives a plain-language description from the filter (e.g. "subscription: active · spent ≥ $50 · countries: US, GB") so the list of saved segments reads as what each one actually does, not just a name you have to remember the meaning of.

A segment in use can't be deleted out from under a campaign

Deleting a segment that a draft, scheduled, running, or paused campaign still targets is refused with the names of the campaigns blocking it — change their audience first. This is a soft delete either way: an in-flight undo elsewhere in the account can still see the row.

Syncing a segment to a native OnlyFans list

If your workspace has enabled writing to OnlyFans Collections, GET /broadcasts/segments/{id}/sync-plan is a read-only dry run: "would add +N, would remove −M" against the platform's own list, with zero calls out. The actual write happens separately and only when you trigger it — this endpoint never changes anything on its own.

What's next

On this page