Audit email deliverability before Q4 traffic compounds

More Q4 traffic does not repair a weak email system. It exposes it faster.

For a brand-owned audience gathered with valid permission, deliverability is an infrastructure and compliance job before it is a copywriting job. A campaign can have relevant creative and still fail because one sending source lacks authentication, a suppression list does not propagate, or an agency sends under a domain nobody monitors.

Audit the whole sending system before seasonal volume compounds those defects.

Inventory every path into the inbox

Start with systems, not campaigns.

List every organizational domain and subdomain used in the visible From address, envelope sender, links, and tracking. Add sending IPs, email service providers, CRM automations, support tools, ecommerce notifications, loyalty systems, review platforms, and agencies. Record owner, message class, typical and peak volume, audience source, authentication status, and suppression source of truth.

Separate transactional mail from marketing or subscribed mail even when one provider sends both. Distinct streams may require different controls and reputations, but a recipient’s opt-out and the legal character of the message still need accurate treatment.

Look for forgotten senders: an old launch tool, a contractor’s platform, a support workflow, or a root domain used for tests. The least-managed source can affect the brand’s reputation and compliance position.

Prove authentication and alignment

Google’s sender guidelines require all senders to personal Gmail accounts to use SPF or DKIM, maintain valid forward and reverse DNS, use TLS, format messages according to Internet message standards, and keep reported spam rates below its stated threshold.

For senders above roughly 5,000 messages per day to personal Gmail accounts, Google adds SPF and DKIM, DMARC, From-domain alignment, and one-click unsubscribe requirements for marketing and subscribed messages. Classify sender status using actual aggregate volume across the same primary domain; splitting traffic across subdomains is not a reliable way to avoid the bulk-sender classification.

Test authentication from delivered messages and DNS, not from a vendor settings screen alone. Confirm which system is authorized by SPF, which domain signs with DKIM, whether DMARC evaluates correctly, and whether the visible From domain aligns as required. Document selectors, record owners, reporting destinations, and change control.

Synchronize consent and suppression

An unsubscribe that succeeds in one application but fails in another is not a completed control.

Map the recipient key and status flow across the ESP, CRM, ecommerce platform, customer support, data warehouse, loyalty system, and agency exports. Test a recipient through every entry point. Confirm that an opt-out reaches the source of truth, downstream sends stop, reimports do not reactivate the address, and transactional exceptions cannot be used to carry promotional content improperly.

Google’s bulk-sender rules and U.S. law are separate gates. The Federal Trade Commission says CAN-SPAM covers commercial email, including business-to-business messages. It requires accurate routing information and subject lines, a valid physical postal address, a clear opt-out, and honoring the request within 10 business days. A company and the vendor sending on its behalf can both have responsibility.

Use the stricter applicable platform, legal, and internal deadline; do not wait ten days where a provider requires faster handling.

Gate list and message quality

Authentication does not make an unwanted message wanted.

Document how every segment entered the brand-owned list, what the recipient was told, and which message class the permission supports. Exclude purchased, scraped, unverifiable, or improperly transferred addresses. Do not build an off-Amazon marketing list from Amazon customer contact data.

Review the From identity, reply path, subject, content, destination links, postal address, preference options, and unsubscribe experience before release. Match sending cadence and content to the recipient’s reasonable expectation. A technically compliant footer does not offset deceptive identity or a stale audience.

Seed tests should cover major mailbox providers and mobile rendering, but they do not substitute for production authentication and complaint data.

Ramp Q4 volume with stop gates

Large, sudden volume can hide which source or segment caused deterioration.

Release in bounded batches, beginning with recent and demonstrably engaged recipients. Monitor delivery errors, deferrals, authentication failures, blocks, unsubscribes, and complaint signals by domain, source, message class, campaign, and segment. Google’s Postmaster Tools can help eligible senders observe spam and delivery indicators for Gmail traffic.

Google requires reported spam rates to remain below 0.3% and recommends staying below 0.1%. Treat the lower level as an operating warning, not as permission to continue until the maximum is crossed. Define who can pause a source, how suppression and complaint data are reconciled, and what evidence is required before resuming.

Do not mask a failing stream by averaging it with healthier transactional traffic.

The Operator Read

Q4 email performance begins with identity, permission, and control plumbing.

Inventory every sender, prove SPF, DKIM, DMARC, DNS, and alignment against the requirements that apply, synchronize suppression across systems, and gate volume with provider and complaint signals. Keep CAN-SPAM duties visible even when an agency or platform executes the send.

The objective is not maximum mail volume. It is a brand-owned communication channel that can prove who sent each message, why the recipient received it, and how quickly the system stops when consent or quality fails.