Send History & transactional analytics

Every email your code sends via the Brixus365 Dev API shows up at Connect → Transactional. The Send History page lists each one with recipient, subject, template, status, opens, and clicks. Click any row to open the Audit Trail drawer with the full event timeline and the actual URLs the recipient clicked. For the bird’s-eye view, open Analytics — six stat cards, three charts, and a per-template performance table over the last 30 days.

---

Open the Send History page

1. Sign in to app.brixus365.com.
2. Click your account menu (top-right) → Connect, then Transactional in the sidebar.
3. The page header reads Send History with the subtitle “View all transactional emails sent via the API.” Top-right shortcut: View Analytics.

Empty state. Before your first API send, the table shows: No sends found. Transactional emails sent via the API will appear here. The first row appears the moment your first POST /v1/emails call succeeds.

Prerequisite. If you haven’t verified a sending domain yet, the page shows a Domain verification required banner with a Set up domain CTA. See Verify your sending domain.

---

Find a specific send

The Send History table has 7 columns. The status filter at the top lets you narrow the list to Pending / Sent / Delivered / Failed / Bounced / Complained — useful when triaging issues.

Column reference:

Column	What it shows
Recipient	The email address you sent to.
Subject	The subject line as rendered.
Template	The name of the template used. Inline-HTML sends (sent without a stored template) show a small badge.
Status	Pending / Sent / Delivered / Failed / Bounced / Complained — with a coloured dot and label.
Sent At	Local timestamp of the send.
Engagement	Whether the recipient opened or clicked, with timestamps for each.
Metrics	Open count and click count, useful for repeat opens or multi-click engagement.

Pagination: 20 rows per page, page-based controls at the bottom.

---

The audit-trail drawer

Click any row in the Send History table to open the Audit Trail drawer. It shows a vertical timeline of every recorded event for that single message:

The events:

• Sent — the moment Brixus365’s mail infrastructure handed the email off for delivery. Always present.
• Delivered — the receiving mailbox accepted the email. Shown if the message status is Delivered, or if there’s a later open or click event (which implies the message was delivered).
• Opened — the recipient opened the email. Shown with the timestamp of the first open. If the recipient opened more than once, the entry reads “Opened (N times)”.
• Clicked — the recipient clicked at least one link. Shown with the timestamp of the first click.

Below the timeline, the drawer lists the specific URLs the recipient clicked — useful for confirming which CTA worked.

The drawer is read-only. There’s no resend action today; if you need to resend, fire another POST /v1/emails.

---

Aggregate view: Transact Analytics

For the bird’s-eye view, head to Connect → Analytics (or click the View Analytics shortcut in the Send History header). The default view is Transact Analytics, a 30-day rolling window over your Dev API sends.

Three charts under the stat cards:

• Send Volume — daily transactional email volume across the 30-day window.
• Delivery Funnel — progression Sent → Delivered → Opened → Clicked.
• Hourly Send Pattern — when (UTC) your code typically fires sends.

Per-template performance table below the charts: each template’s Sent / Delivered / Failed / Open Rate / Click Rate over the same 30 days. Click any row to drill into the per-template detail page.

---

Per-template drill-down

Clicking a template row in Transact Analytics opens its detail page. Four stat cards — Sent, Delivery, Open, Click — over the same 30 days, plus a daily breakdown table with one row per day (Date / Sent / Delivered / Failed / Opened / Clicked).

Useful for:

• spotting a regression on the day you shipped a template change,
• eyeballing whether a recent password-reset template is converting clicks the way you expect,
• comparing weekday vs weekend volume for the same template.

---

What “Bounced” and “Complained” actually mean

These two statuses matter most for sender reputation — worth a beat of explanation:

• Bounced — the receiving mailbox rejected the email. Usually because the address doesn’t exist (a hard bounce) or because it temporarily refused (a soft bounce: full mailbox, server overloaded, etc.). Brixus365 automatically suppresses hard-bouncing addresses from future sends.
• Complained — the recipient’s mailbox provider reported the email as spam (the recipient hit Report spam or the provider’s anti-spam system flagged it). Brixus365 automatically suppresses complaining addresses from future sends — sending to someone who already reported you damages your sender reputation.

Practical thresholds (industry standard, mirrored in the stat-card warning highlights):

Metric	Worth investigating	Reputation at risk
Bounce rate	Over 3%	Over 6%
Complaint rate	Over 0.1%	Over 0.3%

If you cross the worth investigating threshold, check your email-collection flow for typos and stale addresses, and audit recent sends for unexpected content or frequency. Crossing reputation at risk means mailbox providers may already be filtering your mail to spam.

---

What’s coming

• Custom date ranges. The 30-day window on Transact Analytics and the per-template detail page is fixed today. A date-range picker is on the roadmap.
• Unified send feed. Today this page covers Dev API sends specifically. A future cross-surface feed combining Spark campaigns + Workflows + Dev API in one place is on the roadmap.
• Resend from row. Today the audit drawer is read-only. A Resend action is being scoped.

---

What’s next

You want to…	Go to
Send your first transactional email from code	Quickstart
Understand Connect as a whole	What is Connect
Verify a sending domain (prereq)	Verify your sending domain
Send a marketing campaign instead	Send your first email campaign