Separate delivery, acceptance and engagement

A message accepted by a receiving server is not proof it reached the inbox, and an open is not proof the recipient read it. Build a measurement ladder: attempted sends, accepted messages, hard and soft bounces, complaints, unsubscribes, clicks, meaningful conversions and replies. Keep definitions consistent across sending providers.

Use a dashboard that distinguishes campaign-level issues from persistent sender-domain health. A sudden rejection spike after a new list import suggests a different cause than a gradual increase in complaints from long-standing subscribers. Investigate the pattern before changing creative or send frequency.

Classify bounces before taking action

Hard bounces generally indicate permanent delivery failures such as an invalid address; suppress these promptly according to provider guidance. Soft bounces often reflect temporary problems such as a full mailbox, server issue or throttling. Apply a documented retry policy rather than repeatedly hammering the same address.

Inspect SMTP response codes and provider reason categories instead of relying only on a headline bounce rate. Some failures relate to authentication, domain reputation or recipient policy rather than bad addresses. Record the affected domain, campaign, error class and first occurrence to find systemic problems.

Treat complaints as an urgent quality signal

Spam complaints indicate that recipients perceived the message as unwanted, confusing or inappropriate. Review acquisition source, consent record, promised content, frequency and unsubscribe experience. Suppress complainants promptly and avoid resending to them through a different list or tool.

Google's sender guidance recommends keeping user-reported spam rates below 0.1 percent and avoiding 0.3 percent or higher. Those are Gmail Postmaster Tools measures, not necessarily the same denominator as your email provider's complaint-rate dashboard. Do not present the two as interchangeable metrics.

Build a consent and suppression system

Maintain a single authoritative suppression policy across newsletter, promotional automation and CRM sends. Record unsubscribe, complaint, hard-bounce and other ineligible states, with timestamps and source. Ensure a contact excluded from one campaign is not accidentally reintroduced by a sync or a newly uploaded audience.

Distinguish transactional messages from marketing where law and platform rules require different treatment, but do not use transactional classification as a loophole to send promotions. For consent-based marketing, preserve the original permission context and make opting out straightforward. Test the unsubscribe flow regularly.

Audit authentication and reputation

Confirm SPF, DKIM and DMARC configuration for the actual sending domains, and check that the visible From identity aligns appropriately. Review provider dashboards, Gmail Postmaster Tools when eligible and delivery error patterns. Authentication is a necessary foundation, not a guarantee that recipients will want the email.

Large senders to personal Gmail accounts face additional requirements, including aligned authentication and one-click unsubscribe for relevant marketing messages. Keep a change log for domain migrations, sending-platform switches and major volume increases because these can coincide with changes in delivery outcomes.

Example: a list import creates a spike

A business imports an old event-contact spreadsheet and sees more bounces and complaints. The right first response is to pause the affected segment, verify the lawful permission basis, inspect address age and source, and reconcile suppressions. Increasing send frequency to compensate for low engagement would worsen the underlying problem.

After cleanup, resume cautiously with clearly expected content and monitor complaint and rejection trends. Do not assume a single successful campaign means the list is healthy. Compare performance by acquisition source and age, and set thresholds for manual review when quality changes.

Operating cadence and decision rules

Review hard bounces, complaints and critical rejection codes after every send; inspect engagement and segment health weekly; audit consent, suppression syncing and authentication on a scheduled basis. Assign clear ownership between marketing, CRM and technical operations. Write down the trigger for pausing a campaign or isolating a problematic segment.

Report downstream outcomes alongside list health so the team does not optimize for superficial opens or list size. Pair this guide with SPF/DKIM/DMARC setup, re-engagement sunset policy and consent QA. A smaller permission-based list that reliably reaches interested people is more useful than a larger list with avoidable complaints.