> ## Documentation Index
> Fetch the complete documentation index at: https://docs.brew.new/llms.txt
> Use this file to discover all available pages before exploring further.

# Review Your Email Analytics Every Week

> A weekly routine in Brew: read Insights, check bounce and complaint rates, scan automations and sends, and read unsubscribe reasons.

Problems in email build up quietly. A trigger stops firing, a domain's bounce rate creeps up, or one send drives a wave of unsubscribes. A short weekly pass catches them while they're still small.

Run these steps in order, once a week.

<Info>
  **Before you start.** You need at least one send in the last week. Turn on [automatic checks](/analytics/insights#turn-on-automatic-checks) in Brew Insights, so the findings are current when you open the page. Any cadence works for a weekly review.
</Info>

## 1. Start With Brew Insights

Open **Brew Insights** from its card on **Home**. The top of the page compares the **Last 7 days** with the week before. It covers delivered, unique opens, unique clicks, and unsubscribes.

An arrow appears only when a change is statistically real. A number that shows as steady moved within normal noise, so don't chase it.

Then read the findings under **Open**, most severe first, and deal with **Critical** and **Warning** before anything else. Act on each one with its button, snooze it for later, or dismiss it once it's handled.

[Read a Finding](/analytics/insights#read-a-finding) explains what each part means.

If the latest run failed, the findings may be out of date. Click **Run now** before you read on.

## 2. Check Bounce and Complaint Rates

Brew sets two limits for every send: a bounce rate under 2% and a spam complaint rate under 0.08%. [What You Can Send](/get-started/what-you-can-send#what-brew-monitors) explains both.

Open **Events** in analytics and pick the **7d** window. The tiles count delivered, bounced, and unsubscribed events for the week. Work out the bounce rate with the formula in [Key Metrics](/analytics/key-metrics-and-terms).

Insights already flags a send whose bounce rate is high enough for mailbox providers to act on.

Complaints have no tile on **Events**. Ask Brew in chat for each domain's complaint rate, or read it with [`get_domain_health`](#run-the-review-from-an-agent).

Then open **Domains** and check each domain you send from. Its deliverability score shows how it moved since the last check, with a list of what to fix.

**Run check** costs credits. Run it after a change to the domain or a drop in the score, not every week.

## 3. Scan Your Automations

In analytics, switch the list to **Automation**. Each row shows a 14-day trend and its last 14 days of sent, opened, and clicked.

* **Awaiting activity** in place of a trend means a live automation had no recent matches. Check that its trigger source is still sending events.
* **A falling trend** on a flow that usually runs steady is worth opening.

Open any automation that looks off. Its **Email steps** list every email in the flow with its own numbers. That shows the step where people stop opening ([Automation Detail](/analytics/reading-analytics#automation-detail)).

## 4. Look at Last Week's Sends

Switch the list to **Audience** to see one-off sends and manual-audience runs. Compare each send's opened and clicked numbers with your usual results.

Open the weakest one. The row shows its subject line and audience. The detail page adds the sender and preview text, next to the email itself.

That's usually enough to see what to change next time. Insights also raises a finding when an email does better or worse than usual.

## 5. Read the Unsubscribes

Open **Domains**, pick a marketing domain, then **View list** on its **Unsubscribes** card. **Activity** under the list shows:

* unsubscribes in the last 7 days, next to the 30-day and 90-day counts
* how people left: one-click, the confirm page, or unattributed
* the **Top reasons** people picked on the unsubscribe page

A jump after one send usually points at that send's content or timing. One-click opt-outs never give a reason, so a reason count lower than the total is normal. See [Activity](/brand/unsubscribe#activity).

## 6. Pick One Change for Next Week

Choose one thing to change: a finding to fix, a subject line to test, or a flow step to rewrite. Many findings can hand the job to Brew with their button.

One change at a time keeps next week's numbers readable. If you change three things, you can't tell which one moved the result.

## Run the Review From an Agent

Ask Brew in chat for the same review:

> "Give me last week's email review: the Insights 7-day numbers, open findings, bounce and complaint rates per domain, and any automation awaiting activity."

Over [MCP](/api-reference/mcp/tools), the review maps to these reads:

| Step | MCP | API |
| - | - | - |
| Insights and the 7-day numbers | `list_insights` | `GET /v1/insights` |
| Totals and sends | `get_email_analytics` with `report.kind` `overview` or `sends` | `GET /v1/analytics/overview`, `GET /v1/sends` |
| Automation numbers | `list_automations` with `analytics: {}` | `GET /v1/analytics/automations` |
| Domain health, including bounce and complaint rates | `get_domain_health` | `GET /v1/domains/{domainId}/health` |

The API's default windows differ from the app's. Pass `from` and `to` for the exact week you're reviewing. [Reading Analytics](/analytics/reading-analytics) has the details.

## 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:

<Tabs>
  <Tab title="Self-Service Tools">
    <CardGroup cols="2">
      <Card title="Search Documentation" icon="magnifying-glass" color="#c44925">
        Type in the "Ask any question" search bar at the top left to instantly find relevant documentation pages.
      </Card>

      <Card title="ChatGPT/Claude Integration" icon="robot" color="#c44925">
        Click "Open in ChatGPT" at the top right of any page to explore it further with ChatGPT or Claude.
      </Card>
    </CardGroup>
  </Tab>

  <Tab title="Talk to Our Team">
    <CardGroup cols="2">
      <Card title="Schedule a Call" icon="calendar" color="#c44925" href="https://calendar.google.com/calendar/u/0/appointments/schedules/AcZssZ1iYoRUG1J792XQpbuQLjSRRDupr7MwraFK-HQRCtTYdBmrQi8nZu2qXfzKQigb8gbKJK3KN3-R">
        Book time with our founders for personalized guidance on strategy, best practices, or complex implementation questions.
      </Card>

      <Card title="Call Us Directly" icon="phone" color="#c44925">
        Need immediate assistance? Reach us at **+1-(332)-203-2145** for urgent issues or time-sensitive questions.
      </Card>

      <Card title="Slack Channel" icon="slack" color="#c44925">
        Our preferred support channel. You'll receive an invite after signup for direct founder support and fast responses.
      </Card>

      <Card title="Email Support" icon="envelope" color="#c44925" href="mailto:support@brew.new">
        Contact us at **[support@brew.new](mailto:support@brew.new)** for detailed inquiries or if you prefer not to use Slack.
      </Card>
    </CardGroup>
  </Tab>
</Tabs>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.