Audience → Campaigns lists every email blast. Create a draft, write content with the AI-assisted editor, send or schedule to active subscribers, then review stats.
Campaign list
Audience → Campaigns shows all campaigns with status:
Recipients table — filter all / opened / clicked / ignored
Unsubscribe reasons — aggregate counts only
Resend options — remaining subscribers who never received, or follow-up to non-openers
Preview email shows the rendered message and headers.
Campaign actions
From the list menu:
Edit — drafts and reschedulable campaigns only
Send / Reschedule
Stats — sent campaigns
Duplicate — copy as new draft
Delete — remove draft or history entry
Cancel Schedule to return a campaign to draft for editing.
Credits and limits
Each recipient counts against monthly email credits shown on Audience Overview. Test sends and welcome emails also consume credits unless your plan says otherwise.
Agents and API
AI agents and CI scripts can list campaigns, draft and revise copy, and read analytics via /api/v1/campaigns and aveiro_newsletter_* MCP tools — when the token includes newsletter:read and newsletter:write.
Send, schedule, and test sends stay dashboard-only. There is no API scope that grants send.
The media picker stores the canonical/api/media/… path in campaign HTML — the same unsigned reference pages use. That keeps drafts editable and avoids persisting expiring credentials in the database.
Opening a draft in the campaign editor signs media in the stored HTML on read — both the rendered body and the base64 block marker the editor reloads from — so image blocks keep rendering after grants expire; saves strip grants back to the canonical /api/media/… path in both places. Rows that already stored expired grants in the marker heal on the next open.
In-app preview renders that HTML in an iframe on Aveiro's origin. Image blocks are plain `` tags, so the browser sends your session cookies and the delivery route authorizes members who already have org access.
Test send, welcome email, and production send rewrite every media reference to an absolute URL with a share grant at send time. Recipients (and Gmail/Outlook image proxies) fetch with no session, often days or months later — share grants are built for that.
Deleting a file revokes its share grants; already-delivered mail keeps whatever URLs were in that send.
When delivery runs in the background, Send pace controls how fast messages leave:
Pace
Approximate rate
When to use
No data availableThere are no items to display
In the Send dialog, pick a pace above the duration estimate — the estimate uses your choice, so a slow warm-up on a big list is visible before you confirm.
A cold From domain opens with a slower pre-selection: Aveiro reads that domain's send volume over the last 90 days and suggests slow under 500 sends, steady under 5,000, and standard above. The dialog explains why; one click overrides it. A pace already saved on the campaign always wins, and once you touch the picker the suggestion never overwrites your choice.
Choosing anything other than standard queues the send in the background at any audience size — the inline shortcut is skipped so throttling is never hidden state. Non-opener follow-ups inherit the source campaign's pace.
Sending readiness
You need a verified sender domain or configured email provider before send succeeds. The editor shows a banner if setup is missing.
Once sent or scheduled, content is locked — duplicate the campaign to iterate.
Publish to site
From the campaigns list, open the row ⋯ menu on any sent campaign and choose Publish to site to convert the email into a native MDX page on a site. Campaigns tied to one site publish there in one click. Org-wide sends (audience across all sites, with no campaign site) open a host-site picker on first publish — choose which site should own the archive page. If your organization has only one site, it is preselected. After a page exists, Republish to site reuses that host site without asking again.
You cannot move an archive to a different site silently — publishing to another site while a page already exists returns an error. Remove from site first if you need to host it elsewhere.
Aveiro creates a newsletters collection folder (if missing), sorted newest-first, and files the page there — with a per-segment subfolder when the campaign targeted a segment. Segments narrow who received the send; they do not choose the host site.
The conversion is lossy by design so the page inherits your site theme:
Email spacers, per-block spacing, alignment, and brand styles are dropped
Multi-column layouts flatten left-to-right into a single column
Visual-editor campaigns convert cleanly; HTML-only campaigns (from agents or API) are parsed into headings, text, images, buttons, and dividers before conversion
Buttons and images become editable MDX (``, markdown images)
Page metadata carries the campaign subject, preview text, sent date, the segment name as a tag, and the first email image as cover art.
Republish to site overwrites the same linked page — touch it up in the site editor between republishes if you want. Remove unpublishes and deletes the generated page.
Publishing goes live when your plan and site publish gates allow; otherwise Aveiro saves a draft you can publish from the site editor.
Dashboard-only — agents cannot publish newsletters to the site via /api/v1.
Use a Collection block on an index page to list archived newsletters like any other folder content.
