Is your CSV ready?
Paste your CSV header row to check it against the standard revenue-events template — before you upload anything. Header only: no file, no fan data, nothing stored.
No account connection, no scraping, no auto-send.
The nine required columns
Your standard revenue-events CSV needs all nine of these column headers:
- creator_alias
- Pseudonymous label for the creator the event belongs to.
- fan_alias
- Pseudonymous label for the fan — never real names or contact details.
- event_type
- One of the supported event types listed below.
- amount
- Event amount in your currency; use 0 for non-monetary status changes.
- occurred_at
- Date or datetime the event happened, in ISO format (e.g. 2026-06-01).
- lifecycle_status
- The fan's lifecycle state at the time, such as active or expired.
- campaign_ref
- Optional campaign reference for the event; may be left blank.
- content_ref
- Optional content reference; hashed on import and may be left blank.
- event_status
- Status of the event itself, such as delivered, refunded, or active.
Supported event types: subscription, paid_content, tip, message, refund, chargeback, status_change.
Check my fields
Paste the first line of your CSV — the column headers, separated by commas. We never ask for real fan data.