Brew Insights

Brew Insights checks your email for you and lists what it finds, most severe first. Each finding shows the numbers behind it, how Brew detected it, and what would resolve it. Many come with a button that fixes the problem or hands it to Brew. Insights covers deliverability problems, emails that did better or worse than usual, and timing, audience, and automation opportunities. It is scoped to your active brand.

​

Open Insights

Click a Brew Insights card on Home, or go to brew.new/insights. The page, What Brew noticed, has three parts:

• Last 7 days. Delivered, unique opens, unique clicks, and unsubscribes for the last 7 days against the 7 before.
• The counts. How many findings Need attention and how many are Opportunities.
• The findings. The list itself, with Open and All tabs.

Until the first analysis finishes, the page says it is waiting for one and the counts read zero.

​

Reading the Last 7 Days

The 7-day window ends at the start of today, so a day still in progress never skews it. An arrow up or down appears only when the change is statistically real. Small moves show as steady. With too few deliveries to compare rates, Brew shows the counts only. If engagement tracking is off, opens show as unknown.

​

Turn On Automatic Checks

Automatic checks are off by default, so Brew analyzes your account only when you ask. Turn them on to keep the page current. Next check shows when the next automatic run is due. Run now starts one right away.

​

Read a Finding

Each finding has a headline, a severity, and the numbers it was computed on. Those numbers are frozen when the finding runs, so they stay the same even as new data arrives. Quote them as they are.

​

Severity

The list is ranked by severity, then by score within each level:

1. Critical
2. Warning
3. Opportunity
4. Info

For example, a send whose bounce rate is high enough for mailbox providers to act on shows as Critical.

​

What Else a Finding Shows

• Evidence. The facts behind it, with links where Brew has them.
• How it was detected. What Brew looks for, how it measures it, and what it compares against, such as your own history or a fixed limit.
• What resolves it. The condition that closes it, such as a later send of the same email staying under the limit.
• Confidence. High, medium, or low.
• Type. What happened, a change that passed a statistical test, or a recommended next step.
• History. When Brew first and last saw it, and how often it has closed and come back.

​

Act on a Finding

Many findings carry a button. It does one of two things:

• Opens the page that fixes it. For example, a bounce finding can open that email’s analytics.
• Hands the job to Brew. Brew’s assistant starts on a request for you: review your domain health, validate contacts, create or repeat an email, or review a recommendation.

Snooze a finding you plan to deal with later, or dismiss one you’ve handled or don’t need. A snoozed finding comes back to Open when its snooze ends.

​

Open and All

Open lists active findings, including snoozes that have ended. All adds findings that are resolved, cleared, dismissed, or stale, and snoozes still in effect. A finding moves to Resolved on its own once the condition that raised it goes away.

​

Deep Analysis, Reports, and Suggestions

Click Run deep analysis to have Brew’s analysis agent review your account. It publishes an intelligence report: a set of observations about performance, audience, trends, risks, content, and setup, each with its likely impact. A report can propose suggestions: concrete next steps for an audience, an email, an automation, deliverability, or your schedule. Launching one asks Brew to do exactly what the suggestion describes. Suggestions you launch are marked as launched. Brew keeps an account memory across runs, so each analysis builds on what it learned before. Open it from the settings with View account memory.

​

How Current the Findings Are

Brew keeps up to 200 findings in view, and each run records how current its data is. If the latest run failed, the findings may be out of date until the next one succeeds. Run one by hand with Run now or Run deep analysis.

​

From an Agent or Code

Agents and code read the same findings. Over MCP, list_insights lists them as the page ranks them, and get_insight reads one in full. list_insights can also return the weekly numbers, the latest report, its suggestions, and the account memory. From code, GET /v1/insights and GET /v1/insights/{insightId} do the same. Both reads are free. Read Brew Insights covers the API in full.

​

Related

• Reading Analytics for the numbers behind each send
• Key Metrics for what each rate means
• Domains for your domain’s deliverability score
• Audience Hygiene for keeping bounce and complaint rates down

​

Need Help?

Our team is ready to support you at every step of your journey with Brew. Choose the option that works best for you: