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.
