Newsletter

Write, send and grow your list
Import CSV + New edition
Confirmed readers
—
will receive the next edition
Last edition opens
—
no edition sent yet
Last edition clicks
—
 
Next scheduled
—
nothing scheduled
Editions
Status Subject When Sent to Opens Clicks
Loading…
Editions go to confirmed readers only, through your mail servers. Everyone on the do-not-send list is skipped, including readers who unsubscribed here.
Confirmed
—
receive your editions
Pending
—
waiting to confirm
Unsubscribed
—
never mailed again
Net, 30 days
—
 
Growth, last 90 days
Confirmed Unsubscribed
Recent sign-ups
Email Source When
Loading…
Top sources
From the most recent sign-ups.
Loading…
Next steps
Drop the <ff-newsletter> snippet on your site, or POST to the subscribe URL directly.
Subscribers
Email Source Status Subscribed  
Loading…
—
Import readers
Upload the CSV export from your current tool. Status and original signup date are kept; addresses that would bounce or that left before are skipped, and every skip is listed. Nothing is imported until you confirm.
Past imports
FileFromWhenImportedSkipped
No imports yet
Signup behavior
How new subscribers are captured and which language their emails use.
Sender name
The display name on subscriber emails.
Sender email
Your own address, sent through your mail providers - must be one of their configured senders. Blank = FlowPrime's newsletter address.
Email language
Applies to confirmation/welcome emails and the hosted confirm/unsubscribe pages.
Postal address
Printed in the footer of every edition. Anti-spam laws require it, and the pre-send review checks for it.
Consent & compliance
Rendered by the embed widget (v1.3+) next to a checkbox and stored on each subscriber as consent evidence.
Consent text
Terms URL
Privacy policy URL
Heads up: saving a consent text (or requiring consent) makes the widget on your live site start rendering the checkbox as soon as visitors load the page - no site deploy needed.
Subscribe URL
POST JSON { email, source?, consent?, fields?, hp?, ts } with Authorization: Bearer <license-jwt>. Calls are accepted only from origins on the license's domain allowlist (wildcards like *.example.com supported; localhost is exempt for dev). The <ff-newsletter> widget handles the JWT for you and sends { email, ts, consent? }; source, hp and fields are for your own forms and server-side integrations.
fields is an optional object of up to 10 string values, e.g. { "name": "...", "company": "..." } (keys a-z 0-9 _, values up to 200 chars). They show up as extra columns in the subscriber tables and in the CSV export. For an address that is already subscribed, browser-submitted fields are applied only after the subscriber confirms them from their inbox.
…
Manage authorized domains per license in Licenses & Domains. Server-to-server callers can use X-Api-Key with the platform key instead of a JWT.
Embed on your site
Drop this snippet into any page to start collecting subscribers.
…
Replace your-api-key with a license key for the newsletter product. Issue keys to your authorized domains in Licenses & Domains.
Dev-only embed (no license check) 
…
Built-in anti-spam: honeypot hp field (silent drop on bots) · 3-second submit-time check (silent drop) · 10-request/hour-per-IP rate limit (returns 429) · idempotent on duplicate emails.