Email Design, Deliverability, and Compliance
Email Design, Deliverability, and Compliance
This domain tests the technical and legal envelope around a send: rendering, authentication, sender reputation, consent, and unsubscribe requirements.
Core rules and concepts
- Design for clients: responsive layout, roughly 600px max width, alt text on images, strong contrast, bulletproof buttons, and a visible unsubscribe plus physical address in the footer. Test images-off and mobile rendering.
- Authenticate: SPF, DKIM, and DMARC align your domain and reduce spoofing risk. A dedicated IP can protect reputation but must be warmed gradually; a shared IP leverages the provider's reputation but gives less control.
- Protect reputation: send consistent volumes, suppress hard bounces, monitor spam complaints, avoid spam traps, and never buy or scrape lists.
- Comply by jurisdiction: CAN-SPAM requires honest headers, a physical address, and a working opt-out; GDPR requires a lawful basis and honors data-subject rights; CASL generally requires express consent. Use HubSpot subscription types and preference pages, and keep transactional mail separate from marketing.
- Distinguish transactional from marketing; do not route a promotion through a transactional template to bypass consent.
Worked example
A company enables a new dedicated IP. Instead of blasting all 60,000 contacts, it sends to the 5,000 most engaged contacts first, then 10,000, then 15,000 over several days, watching bounces and complaints. The gradual ramp builds reputation. A sudden full-list send from an unwarmed IP is a classic route to throttling and spam-folder placement.
Traps
Missing physical address; hiding unsubscribe; image-only email; ignoring hard bounces; buying lists; treating all email as transactional; and launching a new IP at full volume.