Skip to content

Docs: Campaign Builder guide, sending type and unsubscribe consolidation, October roadmap - #38

Merged
MarkNLD merged 12 commits into
mainfrom
docs-campaign-builder
Oct 20, 2026
Merged

MarkNLD merged 12 commits into
mainfrom
docs-campaign-builder

Conversation

@MarkNLD

@MarkNLD MarkNLD commented Oct 20, 2026

Copy link
Copy Markdown
Collaborator

Campaign Builder guide

New sidebar group Campaign Builder, after "Sending with the API":

Page Covers
campaigns/index What it is, the five steps, separate marketing infrastructure, where things are in the dashboard
campaigns/contacts-and-lists CSV import rules, custom fields, contact status vs list status, unsubscribe/remove/delete, advanced search and Save as new list
campaigns/templates Template catalog (start campaigns and new templates from it), Simple vs Advanced editor, importing MJML/HTML
campaigns/create Sender, lists, subject and preview, personalization with defaults, the unsubscribe link
campaigns/test-and-send Test sends and their limits, the issues list, schedule/unschedule, the list and content review, statuses, daily limit
campaigns/reports The numbers and how rates are counted, per-list deliverability, bounce reasons, export and webhooks
campaigns/api-and-automation Typical automations, API scopes, CLI command groups, MCP Marketer preset

Moved into the group with redirects: deliverability/marketing-limit → campaigns/marketing-limit, deliverability/unsubscribe → campaigns/unsubscribe. All internal links updated.

Sending type made clearer

  • /domains: new Sending Type section with a table, and the rule in one place: Campaign Builder campaigns always use the marketing infrastructure and need no setting; marketing mail sent through the API or SMTP must come from a marketing domain.
  • /deliverability: one paragraph with the same rule under "Which sending type should my domain use".
  • Homepage card "Marketing Domains" now points at /domains#sending-type.

Also

  • Facts: test send limit (5 addresses, 50 per day) and import limits (100 MB CSV, 1,000 contacts per API request).
  • Glossary: campaign, campaign template, contact, list, sending type, daily marketing limit, review.

Checks

  • scripts/docs_lint.py rules pass (descriptions 120–160, titles unique, navigation complete).
  • mint broken-links: no broken links.
  • Please confirm two dashboard details I could not verify from the API: that custom fields are managed from the Contacts page (overview table), and that the campaign page shows a preview that steps through real contacts (create page, Personalization).

Later commits on this branch

  • One home per topic: /domains#sending-type for the setting, campaigns/unsubscribe for API/SMTP unsubscribe rules including building your own endpoint; /deliverability keeps short pointers; no circular links.
  • Guide checked against the October changelog: text_unchecked, sends refused on the spot, catch-all addresses in list checks, Email Address CSV column and Mailchimp files, Save as new list from plain and advanced search, Send Campaign on a list page, View email button. "Simple Editor" and "Advanced Editor" casing throughout.
  • Roadmap, October update: Recently shipped gets MCP server, Transactional Templates, SMTP on port 465 and zero-day retention for sub accounts (7); Active is one infrastructure card; Planned (34) follows the internal Fibery roadmap order, with the permissions cards merged, Whitelabel DNS for Pro, the Email Address Validation API endpoint, a Retry delivery card, and Whitelabel dashboard on your own domain added.

MarkNLD and others added 11 commits October 20, 2026 12:21
…mains

- New group Campaign Builder: overview, contacts and lists, templates and
  editors, creating a campaign, test/review/send, reports, API/CLI/MCP
- Move marketing-limit and unsubscribe pages into the group, with redirects
- /domains: Sending Type section; Campaign Builder needs no sending type,
  marketing mail through API/SMTP needs a marketing domain
- Homepage cards, facts (test send and import limits), glossary terms
- /domains#sending-type is the reference for the setting; /deliverability keeps the why and links there
- campaigns/unsubscribe owns the API/SMTP rules incl. building your own endpoint; /deliverability one-click section is a three-case pointer
- campaigns/create#the-unsubscribe-link stays campaign-only and points to the API/SMTP page
- No circular links between the three
- MCP page: a campaign only goes out after your consent
- Issues: text_unchecked; sends refused on the spot; catch-all and unreachable addresses in list checks
- CSV import: Email Address column and Mailchimp files; Save as new list copies in the background; Send Campaign on a list page sends to the whole list
- Reports: View email button
- Recently shipped: MCP server, Transactional Templates, SMTP on port 465 (now 6)
- Active: internal infrastructure improvements; zero-day retention for sub accounts moved to Planned
- Planned: whitelabel dashboard on own domain, recipient pages in the recipient's language, dashboard in more languages (now 37)
- Campaign Builder card: Simple Editor / Advanced Editor, included in every plan
Test sends (3 in the dashboard, placeholder text), the list check (sampled,
only for new or changed lists, pause above 4%), review outcomes, dashboard
button names, contact and list actions that exist only in the API, CSV
import and export, custom field keys, template catalog actions, HTML
upload, and the sending type through Update Domain.
Docs: Campaign Builder guide checked against the product code
@MarkNLD
MarkNLD merged commit 6795d23 into main Oct 20, 2026
2 checks passed
@MarkNLD
MarkNLD deleted the docs-campaign-builder branch October 20, 2026 14:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants