Deliverability
How campaign email is sent, and what's tracked around delivery.
Campaign email sends through Brevo from a single, fixed sender address configured for your Threadliner instance — there's currently no per-workspace custom sending domain or SPF/DKIM/DMARC setup in the product. If you need a dedicated sending domain, that's a hosting-level configuration question, not something you set up from within Threadliner today.
What's tracked automatically
- Link tracking: every link in a
buttonortextblock gets UTM parameters (utm_source=newsletter,utm_medium=email,utm_campaign=<campaign-slug>) appended automatically, and is routed through a click-tracking redirect. See Campaign analytics. - Send failures: a failed delivery marks that recipient
FAILEDand counts toward the campaign's Failed stat, without blocking the rest of the send.
There's no unsubscribe link automatically added to campaign content. The
Subscriber model has a per-subscriber unsubscribe token designed for this, but the
current send pipeline (renderCampaignHtml) doesn't inject it into the email body or
as a header, and there's no per-recipient merge-field system a campaign author could
use to add one manually either — block content is the same for every recipient. If
you're sending real marketing email, this is worth confirming with whoever owns
compliance before you rely on Threadliner's campaigns for anything CAN-SPAM/GDPR
needs to cover — right now, unsubscribing only happens via the Unsubscribe button
in the dashboard's list view, not from the email itself.
General best practices
Beyond what's tracked above, ordinary email deliverability practice still applies:
keep your list clean (Threadliner already stops sending to UNSUBSCRIBED, BOUNCED,
and COMPLAINED subscribers automatically), avoid spammy subject lines, and prefer
double opt-in lists (see Lists and double opt-in)
over imported/purchased lists.
Last updated on