Email marketing overview

FilesHub email marketing sends campaign email for a project: lists of people, imported with a recorded reason to write to them, and drip sequences that change course based on what each person did. It runs on the same platform that already sends the project's transactional email, from separate marketing mailboxes, so a campaign can never affect password-reset mail.

What it does

Part	What you get
Lists and contacts	Named lists per project. Each contact keeps its source, the reason it fits, tags and a consent basis.
Three ways in, one pipeline	CSV upload (with a column-mapping step), pasting comma- or line-separated addresses (Name <email> works), or one contact at a time. Every row is checked the same way and lands in exactly one counter.
Consent and suppression	Every contact records why you may write (opt_in, legitimate_interest, existing_relationship). An unsubscribe stops all marketing from that project for good, across every list.
One-click unsubscribe	Every email carries the RFC 8058 List-Unsubscribe headers Gmail and Yahoo require, and a visible unsubscribe link.
Double opt-in	A public sign-up form confirms by email first; a link scanner cannot confirm for the person.
Sequences	Emails in tracks (A → B → C), spaced by hours or days, where each step can require "not clicked yet", "signed up", "not activated yet"… and otherwise skip, end, or move the person to another track.
Tracking and events	Link clicks (scanner clicks filtered out) and events your product reports (signed_up, activated) steer the sequence immediately.
Designed in FilesHub	A branded layout — your name, colour and logo, the footer, postal address and unsubscribe line — wraps each email's content.

What it does not do

• It never sends to scraped or bought lists: a row without a consent basis is refused.
• It shows measured numbers only — sent, failed, unique clicks, unsubscribes, bounces, complaints. There is no delivery rate, and opens (off by default) are labelled unreliable because privacy proxies open every email.
• No A/B tests, drag-and-drop builder or SMS.

How sending works

A scheduled job runs every minute and sends the steps that are due, inside the project's sending window and under its daily cap. Each email leaves from one of the project's marketing mailboxes (least-used first) and never from a transactional one. New mailboxes start at a low daily limit and are raised by hand as the numbers stay healthy. A project pauses itself automatically when hard bounces pass its threshold or a spam complaint arrives, until an admin clears the pause.

Access

Caller	Credential	Gate
Your product's backend	fh_live_ key	can_manage_email_marketing on the key (off by default). Server-side only: a request with a browser Origin is refused.
Your public sign-up form	an origin-restricted fh_live_ key	the same flag; the only marketing endpoint a browser may call
An agent or CLI	fh_pat_ token	the token's can_manage_email_marketing scope; other projects answer 404

Next: the API reference and the product integration recipe.