Brew’s analytics are split into three tabs — Campaigns, Automations, and Events — each scoped to your active brand. Open analytics from the sidebar.
Use the time range selector in the top right to filter by any window. Analytics default to your local timezone; switch to UTC or another timezone using the timezone control next to the date range.
Campaigns
Automations
Events
The Campaigns tab shows performance for one-off email sends — newsletters, announcements, promotions. Each row is one campaign send.| Column | What it means |
|---|
| Sent | Emails accepted for delivery |
| Delivered | Emails that reached the inbox |
| Opens | Unique recipients who opened |
| Clicks | Unique recipients who clicked a link |
| Bounces | Emails that couldn’t be delivered |
| Unsubscribes | Recipients who opted out |
The Automations tab shows performance for triggered flows — welcome sequences, onboarding drips, re-engagement flows. Each row is one automation, with a breakdown by node below it.Flow-level stats
| Column | What it means |
|---|
| Runs | Contacts who entered the flow when the trigger fired |
| Sent | Total emails sent across all steps in the flow |
| Delivered | Emails that reached the inbox |
| Opens | Unique opens across all emails in the flow |
| Clicks | Unique clicks across all emails in the flow |
| Bounces | Emails that couldn’t be delivered |
| Succeeded | Contacts who completed every step in the flow |
| Failed | Contacts whose run stopped due to an error |
Runs and Succeeded will usually look mismatched, and that’s normal. A contact enters a flow the moment the trigger fires, but they don’t complete it until every step — including all Wait nodes — has finished. A 3-email flow with 2-day waits takes nearly a week to complete. If you launched recently, most runs will still be in progress.
Failed means something stopped the contact mid-flow — a hard bounce, a missing payload field, or a filter that couldn’t evaluate. Click into a failed run to see the specific error.
Per-node breakdown
Expand any automation to see stats per node. Each Send Email node has its own Sent, Delivered, Opens, and Clicks columns — so you can see exactly where engagement drops off across the sequence, not just the aggregate.Wait nodes show how many contacts are currently paused there. Filter and Split nodes show how contacts were routed. The Events tab is a unified real-time log of every email event across all campaigns and automations — a single stream regardless of how the email was sent. Use it to investigate: confirm a specific contact received an email, debug a delivery issue, or audit exactly what happened during a send.Filters
Narrow the log using any combination of:| Filter | What it does |
|---|
| Event type | Show only Delivered, only Clicked, only Bounced, etc. |
| Email | Filter to one specific campaign or automation email |
| Audience | Filter to a specific contact list or segment |
| Automation | Filter to all events from one automation, across every step |
| Trigger event | Filter to emails fired by a specific trigger |
Columns
| Column | What it means |
|---|
| Time | When the event occurred |
| Event | The event type (Sent, Delivered, Opened, Clicked, etc.) |
| Audience | The contact who triggered the event |
| Activity | The email or automation step that generated it |
You can ask Brew directly from chat. “Which campaign had the highest CTR last month?” / “Show me everyone who clicked but didn’t open in the welcome flow.” Brew has access to your analytics data and can return summaries, comparisons, or contact-level details.
Where the numbers come from
Every metric on the dashboard is derived from sends and their events.
- A send is one delivery of a design. A campaign records a single send for the whole audience; an automation records one send per recipient. Both kinds share the same dashboard.
- Each send accumulates events as it moves through the pipeline (sent → delivered → opened → clicked, plus bounces, complaints, and unsubscribes). Every event is attached to the send that produced it, so a recipient’s open always traces back to the exact send and design they received.
- Rolled-up totals (delivered, opened, clicked) are computed per send from those events, then aggregated across the window you’re viewing.
This is why campaign and automation performance line up in one view: they’re the same underlying records, just tagged by which surface created them.
Filters and time ranges
The top-right time range selector adjusts the window:
- 1h. Last hour (good for monitoring an in-progress send)
- 24h. Last day
- 7d. Last week
- 30d. Last month (default)
- 1y. Last year
Filter further by:
- Recipient email. Search a specific contact to see all their events
- Email. Filter to one campaign, automation, or transactional email
- Event type. Toggle which event types appear on the chart
Reporting timezone
By default, analytics are shown in your browser’s local timezone. Use the timezone control in the top-right to switch to UTC or any other timezone, useful when coordinating reports across regions or comparing to other systems.
The activity chart
The chart shows event volume over time. Each event type has its own colored line. Click a label below the chart to show or hide an event type.
Drag on the chart to zoom into a time range. Scroll to zoom in and out.
Event details
Click any event in the table below the chart for full details:
- Recipient email
- Event timestamp
- Email subject line
- Email client and operating system (when available)
- Geographic location (when available)
Geographic data
The map shows where recipients are opening and clicking emails. Helpful for:
- Understanding audience distribution
- Optimizing send times for different regions
- Spotting unexpected engagement patterns
Asking Brew for analysis
You can also ask Brew directly: open chat and prompt it about your analytics. “Which campaigns had the highest CTR last quarter?” / “Compare opens between my Pro and Free audiences over the last 90 days.” Brew has access to your analytics data and can return summaries, comparisons, or specific contact-level details.
