Skip to content

chore(KNO-13495): Add broadcast email best practices #1472

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
rachael-t wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(KNO-13495): Add broadcast email best practices #1472

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions content/concepts/broadcasts.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -131,6 +131,10 @@ Broadcasts respect all [user preferences](/concepts/preferences) that are config

Knock also supports [commercial unsubscribe](/preferences/commercial-unsubscribe) preferences that will automatically add a 1-click unsubscribe header and link to your email messages, to respect CAN-SPAM compliance.

## Best practices

If you plan to send broadcasts regularly or at high volume, we recommend configuring a dedicated email channel for marketing sends that is separate from your transactional email channel, and ideally using a separate sending domain or subdomain. Marketing and transactional email have different engagement and complaint patterns, and isolating them protects the deliverability and sender reputation of your transactional email if a broadcast generates higher-than-expected unsubscribes or spam complaints.

## Frequently asked questions

<AccordionGroup>
Expand Down
Loading