Audience Hygiene

Audience hygiene is the practice of keeping your list valid, relevant, and engaged. For day-to-day contact management like handling bounces and suppression lists, see Manage contacts.

​

How Brew Protects Your Sending Reputation

Brew tracks bounce rate and spam complaint rate on every send. A domain’s health read (get_domain_health, or GET /v1/domains/{domainId}/health) reports both from a sample of sends and flags a high rate. Brew Insights flags a send whose bounce rate is high enough for mailbox providers to act on. What You Can Send states the thresholds. They protect everyone on the platform: a single sender with poor list quality can affect shared sending infrastructure. The best way to keep bounces from happening at all is to validate your contacts before you send. Each address comes back valid, risky, or invalid, and the verdict is saved on the contact. That page covers every way to run the check, from one click on an audience to the API.

​

Build a Quality List from the Start

The foundation of a healthy audience is how contacts get on it in the first place. Be clear on your sign-up forms. Tell people what they’re signing up for and how often you’ll email them. Transparency reduces unsubscribes and attracts contacts who want to hear from you. Use CAPTCHA on sign-up forms. Bot submissions inflate your list with invalid addresses that hurt deliverability. Three solid options:

• Google reCAPTCHA: multiple protection levels from invisible verification to interactive challenges, with excellent bot detection. Simple integration with most website platforms.
• hCaptcha: privacy-focused alternative with enterprise-grade security, adjustable difficulty settings, and strong accessibility options.
• Friendly Captcha: runs verification in the background without puzzles. Designed for strong privacy protection and compliance with global regulations.

Never purchase lists. Brew only allows permission-based email. Purchased lists contain people who never opted in to hear from you specifically. They lead to high bounce rates, spam complaints, and account suspension. See What you can send with Brew for the full policy.

​

Monitor Engagement over Time

Regularly check your key metrics in Analytics:

• Open rate
• Click rate
• Bounce rate
• Spam complaint rate
• Unsubscribe rate

A significant drop from your baseline means something needs attention: your content, your sending frequency, or your contact quality.

​

Segment by Engagement

Targeting engaged segments for regular sends protects your sending reputation and improves performance. Create Audiences lists the standard tiers, from highly engaged down to inactive. Audiences in Brew are dynamic. As contacts engage or go quiet, they move in and out of segments automatically. You don’t need to rebuild them. A time window like “in the last 30 days” is the exception. Engagement lives in your event history, not on the contact, so a saved filter can’t express it. Build those cohorts from events instead, as described in Engagement snapshots. To build an inactive segment:

1. Ask your agent for the cohort, for example:
   Create an audience of contacts who haven't opened or clicked
   an email in the last 90 days.
   
2. The agent builds an engagement snapshot with create_audience_from_events. It uses cohort.exclude, so the audience holds everyone in your base audience who did not open or click in that window.
3. Wait until the build is ready before you send to it.
4. Name it with the date, like “Inactive 90 days: 2026-10-14”. A snapshot is frozen, so build a fresh one each time.

Build each tier the same way. Use your highly engaged segment as the primary audience for your regular sends.

​

Re-engage Inactive Contacts

Contacts who’ve gone quiet are worth one well-aimed attempt before you stop sending to them. As an Email. Send a one-off Email to your inactive segment:

1. Go to Emails in the sidebar and open a new chat.
2. Select your inactive audience segment.
3. Use a prompt like:
   Create a re-engagement email with a subject line about missing
   the recipient, acknowledging their inactivity, reminding them
   of our value, and including a clear CTA to stay subscribed.
   
4. Review and refine the output, then send.

As an Automation. Build a 2 to 3 step re-engagement flow and run it for an engagement snapshot of inactive contacts. Brew has no scheduled trigger, so build a fresh snapshot and run it again each cycle. See the Lifecycle emails for SaaS and B2B recipe for prompts and a step-by-step walkthrough. After the re-engagement attempt, handle contacts based on how they responded:

• Re-engaged: move them back into your active sending audience
• Still inactive: exclude them from regular sends
• No response after final email: exclude them from every send, but keep the contact

Continuing to send to chronically inactive contacts hurts your metrics and your sending reputation.

​

Set a Sunset Policy

Decide upfront what inactive means for your business and what happens when a contact crosses that threshold. A simple policy:

1. No engagement in 90 days. Enter re-engagement flow.
2. No engagement after re-engagement flow. Exclude from regular sends.
3. No engagement in 6 months. Exclude from every send.

Don’t delete inactive contacts to clean the list. Exclude them with a filter instead. Deleting a contact removes its profile and activity. Brew keeps its unsubscribe and bounce restrictions, so re-adding the address doesn’t make it mailable. See Manage Contacts for what a delete removes.

​

Recurring Hygiene Tasks

A few things worth doing on a regular cadence:

• Before a big send: validate the audience you’re about to send to, and pull anything that comes back invalid.
• Monthly: check bounce rate and spam complaint rate trends. Flag anything moving toward the thresholds.
• Quarterly: run a re-engagement campaign for contacts inactive 90 or more days.
• Every 6 months: review your active sending audience and prune contacts who haven’t engaged in over 6 months.

​

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: