What Google tells senders to configure
Google’s Gmail sender guidelines call for all senders to personal Gmail accounts to use SPF or DKIM authentication. For bulk senders, the page specifies SPF and DKIM, DMARC, and alignment requirements, alongside other sender practices.
These are Google’s stated conditions for its mail ecosystem, not a universal promise of inbox placement. The page also advises senders to keep spam rates low. Authentication is therefore necessary operational groundwork, while reputation and recipient experience remain important and partly outside a marketer’s control.
Audit the real sending architecture
A company may send from a marketing platform, a CRM, a support tool, and a transactional service. List each source and determine which domain it uses before editing records; an SPF record that omits a legitimate sender can create a different problem from an unauthenticated stream.
Coordinate DNS changes with the domain owner and technical team. After implementation, inspect message headers from each system and confirm that the expected authentication results appear. Preserve a record of approved senders so future vendor onboarding does not quietly bypass the configuration.
Make deliverability a lifecycle concern
Authentication does not compensate for confusing consent, stale lists, or messages people did not ask to receive. Review acquisition forms, segment logic, suppression, complaints, and campaign cadence alongside the technical checks.
For Email & SMS Marketing, the practical response to Google’s guidance is a maintained sender inventory and launch preflight, not a claim that one record guarantees delivery. Keep channel permissions distinct, investigate signals by source, and use the official requirements as one part of a responsible sending program.
From perspective to practice.
See how this subject connects to the work we do.
Explore Email & SMS Marketing ↗