Authenticate every sending domain
Configure the SPF and DKIM records shown under Marketing Automation > Settings > Email, then publish a DMARC record for the From domain. Verify the domain before sending production traffic. Google requires SPF or DKIM for all senders and SPF, DKIM, and DMARC for bulk senders. Keep the From domain aligned with SPF or DKIM. See Google’s current email sender guidelines.Send expected email
- Send marketing email only to recipients who opted in.
- Do not use purchased, rented, or scraped lists.
- Keep volume increases gradual and avoid abrupt spikes.
- Suppress hard bounces, complaints, and unsubscribed recipients immediately.
- Keep transactional and promotional traffic logically separate.
Make unsubscribe easy
Include{{global.unsubscribe}} visibly in every marketing template. Masivo
also sends RFC 8058 List-Unsubscribe and List-Unsubscribe-Post headers, so
supporting inboxes can perform a one-click unsubscribe without opening the
message.
Transactional account emails are not given marketing unsubscribe headers.
Monitor Postmaster and Masivo together
Masivo analytics reports campaign delivery, bounce, complaint, open, and click events. Google Postmaster reports Gmail’s domain-level view. Connect it under Settings > Email, then use Analytics > Emails > Deliverability to review:- Compliance verdicts for SPF, DKIM, DMARC, DNS, TLS, spam, and unsubscribe
- User-reported spam rate
- Authentication and TLS success rates
- Delivery error types and reasons
- Feedback loop IDs
React to problems
- Rising spam: pause the affected segment and review consent and content.
- Authentication failure: correct DNS and From-domain alignment before resuming.
- Reputation-related rejects: reduce volume and remove low-engagement recipients.
- Temporary failures: avoid immediate high-volume retries.
- Unsubscribe failure: verify the visible link and one-click endpoint.